A team picks up an open-source library because it’s free, it’s good, and nobody has to file a procurement request to start using it. This is the correct decision. We’ve watched it play out dozens of times, and it’s the right call almost every time.
Then it’s month six. The library is wired into the product, the rollout is halfway done, and there’s a board deck due Thursday that depends on it rendering correctly. Something needs to change. The developer who introduced it has moved to another team, or another company. The GitHub issue you opened has three thumbs-up and no reply. And somewhere in the building, someone in procurement is asking a very reasonable question: *who is our vendor for this? *
The honest answer — “nobody, it’s open source” — is technically accurate and completely useless to the person who has to sign off on the release.
What Free Actually Answers
Open source answers one question cleanly: *can we use this? * Yes. Apache 2.0, no license fee, keep the attribution and you’re done. That part of Rare Styles isn’t changing, and it isn’t going to. The library stays free, because a design system that only the well-funded can adopt isn’t a design system, it’s a sales funnel.
But “can we use it” and “who’s accountable when it breaks at 11pm before a deadline” are different questions. The second one doesn’t have a free answer, and pretending it does is how internal rollouts quietly stall.
So we gave it one.
Rare Styles Enterprise Support is a one-time payment of $9,999. One payment, one project. You get an SLA, priority support through the adoption phase, direct answers from the people who built the thing, and — the part procurement actually cares about — a named party standing behind the implementation. It’s built for the team that has a deadline, a board, and someone who has to answer for whether this works.
If you’re using Rare Styles on a side project, a prototype, or anything without a delivery date attached — keep using it free. That’s still the whole point, and nothing about that changed today.
But if it’s load-bearing, if there’s a rollout with a date and a board behind it, the supported tier exists for exactly that situation. One name, one SLA, one number to call.
Details and the rest of the support options are on the Rare Styles pricing page.