110 Million Installs a Week. The Funding Model Still Did Not Work.
Tailwind Labs is joining Shopify. The CSS framework stays MIT, but the paid products that funded it are closing to new customers. The last well-known example of fund-the-commons-by-selling-something-next-to-it just resolved into an acquisition, which means every option has now been tried.
On 9 September 2026, Adam Wathan announced that Tailwind Labs is joining Shopify.
The framework is fine. That is worth saying first, because the reflex is to assume otherwise:
Nothing changes with Tailwind CSS or any of our other open-source projects. Everything will always be MIT-licensed, and our team will continue to lead and maintain these projects for the community with the support of Shopify.
Take that at face value. There is no relicense here, no open-core bait and switch, no rug pull. By the standards of how these announcements usually go, this is the good version.
The interesting part is the other sentence.
The line that matters
All existing customers will of course maintain their access to products like Tailwind Plus and ui.sh, but we're closing sign ups for new customers to focus on Tailwind CSS at Shopify.
Tailwind Plus and ui.sh were the business. Premium component libraries sold alongside a free framework, funding a team to work on the free framework full time. No venture capital, no license games, no foundation with a donate button.
That was the model everyone pointed at. When the argument came round again about how open source should be funded, Tailwind was the counterexample people reached for. It worked. It was independent. Nobody had to be a charity or a hostage.
And the framework at the centre of it is not niche:
the framework is installed over 110 million times per week and is trusted by many of the world's biggest companies to style products like ChatGPT, X, Cloudflare, Reddit, and Shopify
One hundred and ten million weekly installs. Nine years. Used by the largest software products in the world. And the sustainable answer still ended in acquisition.
No price was disclosed. No revenue figure was disclosed. Read that absence however you like, but the shape of the outcome is not ambiguous.
Every option has now been tried
Line up the ways a widely-depended-on open source project can pay its maintainers. There are not many, and at this point each has a large public example with a known ending.
Relicense. Take something permissive and move it to a source-available license when a cloud provider monetises your work better than you do. HashiCorp, Redis and Elastic all did versions of this. It works commercially and it costs you the community, usually via a fork that keeps the old license and the old name's goodwill.
Foundation and donations. Neutral governance, corporate members, a donate button. Good for governance, chronically underfunded relative to how load-bearing the software is. This is the model that produced the long tail of critical infrastructure maintained by one exhausted person.
Venture capital. Take money against a future business model that the open source project is supposed to produce. Sometimes it works. Often the pressure to find that model is what forces option one.
Sell a premium product next to the free one. Tailwind. The one without an obvious catch.
And now: acquisition. Which is where option four went.
That is not a moral failure by anyone involved. Wathan's stated reason is plausible and sympathetic:
We're joining Shopify to give Tailwind a stable long-term home where it will be actively maintained for the millions of people who depend on it.
A nine-year-old project with 110 million weekly installs is a serious permanent obligation held by a small company. Wanting an institution behind it is reasonable. But the fact that the good outcome and the acquisition outcome are the same outcome is the thing to sit with.
The same week, the same company, the other direction
Here is the pairing that makes this more than a funding think piece, and almost nobody will put the two together.
In the same week, Shopify published Back to Native, announcing it is leaving React Native. That post includes the wind-down of the React Native libraries Shopify maintained: FlashList, at roughly 2 million downloads a week, is looking for a new steward; React Native Skia is sponsored to the end of 2026 and then forks away; Restyle is being archived.
So in one week, one company acquired the maintainers of one ecosystem's most-used styling layer and began exiting stewardship of another ecosystem's most-used list component.
Nothing improper about that. Both decisions are internally coherent and both were announced honestly. But put side by side they describe the actual mechanism with unusual clarity:
A library maintained by a company is maintained for exactly as long as that company's strategy requires it. Not out of malice. Out of arithmetic. The React Native libraries were sustained by a strategic commitment, and when the strategy changed, the commitment did.
Tailwind is now on the other side of that same arrangement. Today the support is real and the incentives point the right way, because Shopify uses Tailwind. The question the pairing raises is not whether Shopify will be a good steward. It is what the commons looks like when stewardship is a line item in somebody's strategy review.
What this actually changes for you
Very little this week, and that is the honest answer.
Tailwind CSS is MIT and it stays MIT. An MIT license cannot be revoked on code already published. The worst realistic case is not a rug pull, it is the slow kind: priorities shifting toward what Shopify needs and away from what you need.
If you were going to buy Tailwind Plus, that decision expired. Sign-ups are closed. Existing customers keep access.
If you depend on FlashList, Skia or Restyle, you have work. That is the concrete task from this week, and it comes from the other post, not this one.
And the broader signal is about dependency shape, not about Tailwind. The useful question for anything in your stack maintained by a single company: what happens to this if that company's strategy changes? For a lot of your dependencies the answer is fine, it is a genuine community project. For some of them the answer is that you are relying on a strategic commitment you were never party to.
The part worth saying plainly
There is a version of this post that treats the acquisition as a betrayal. That version is wrong and it is unfair to people who built something good and gave it away for nine years.
The better reading is sadder and more useful. A project can be enormously successful, genuinely well run, commercially creative, and independent, and still find that the durable answer is to be owned by someone larger.
If the model everybody cited as proof that open source could fund itself ends here, then the question is not what Tailwind should have done differently. It is whether the funding problem has a solution that survives success, or whether we have four ways to delay the same ending.
Sources. Tailwind Labs is joining Shopify, Adam Wathan, 9 September 2026, for every quote and figure above, and Back to Native, Shopify Engineering, 10 September 2026, for the library wind-downs. Related here: cross-platform was a labor-saving device.