Even as more developers than ever use Tailwind CSS, the company behind it is shrinking fast… and AI is to blame.
Tailwind Labs, the company behind the widely used Tailwind CSS framework, has cut about 75% of its engineering team, a move that has sent shockwaves through the developer community.
The layoffs come at a difficult moment: Tailwind CSS is more popular than ever, yet the business that maintains it is struggling to stay afloat.
Founder and CEO Adam Wathan confirmed the job cuts publicly, linking the decision directly to the growing influence of AI tools in software development.
“75% of the people on our engineering team lost their jobs here yesterday because of the brutal impact AI has had on our business,” Wathan wrote in a GitHub comment.
Tailwind CSS is an open-source, utility-first framework used to design websites and apps quickly. While the framework itself is free, Tailwind Labs makes money by selling paid products like UI components and insider programs.
That model depended heavily on one thing: developers visiting Tailwind’s documentation. According to Wathan, that funnel is breaking.
“Traffic to our docs is down about 40% from early 2023 despite Tailwind being more popular than ever,” he wrote. “The docs are the only way people find out about our commercial products, and without customers we can’t afford to maintain the framework.”
AI coding tools now generate Tailwind code directly, meaning many developers never visit the website at all. As a result, Tailwind’s revenue has fallen by nearly 80%, even while usage keeps climbing.
A small company, a big cut
While “75% layoffs” sounds massive, Tailwind Labs is a small company. In a podcast shared on X, Wathan explained that the company had four engineers before the cuts. Now, there is just one.
“If absolutely nothing changed, then in about six months we would no longer be able to meet payroll obligations,” Wathan said in the podcast, describing the financial forecasts he ran over the holidays.
He added that making the decision earlier allowed the company to provide more generous severance packages.
The GitHub thread that sparked a firestorm
The situation became public after Wathan declined a pull request that proposed making Tailwind’s documentation easier for large language models to consume.
Explaining the decision, he wrote: “Making it easier for LLMs to read our docs just means less traffic to our docs, which means fewer people learning about our paid products and the business being even less sustainable.”
The comment went viral, drawing intense debate about whether open-source projects can survive when AI systems replace human visits to documentation pages.
Community reaction and industry support
The layoffs sparked an outpouring of support from across the tech industry and renewed concern about open-source sustainability.
Vercel CEO Guillermo Rauch announced his company would step in as a sponsor:
“Vercel will be officially sponsoring http://tailwindcss.com. That’s a given.” Rauch wrote on X. “We as a community and industry owe @adamwathan and team a lot. Tailwind is foundational web infrastructure at this point (it fixed CSS 😉). I’ve also reached out to Adam to explore how we can make this a longer-term commitment.”
Google also joined in. Logan Kilpatrick, lead product manager for Google AI Studio, posted on X: “I am happy to share that we (the @GoogleAIStudio team) are now a sponsor of the @tailwindcss project!”
Wathan later responded with gratitude, writing: “Overwhelmed by the support over the last 24 hours… Thanks so much to everyone with words of encouragement, the new sponsors we’ve brought on… I’m extremely touched ❤️.”
For now, Tailwind CSS will continue to run, maintained by a skeleton crew. But its crisis is a warning sign for every open-source project that relies on community engagement and website traffic to survive. The tools that build the web are entering a new, uncertain era, and the business models of yesterday may already be obsolete.
Looking to pivot your career? Check out 10 AI Jobs You Can Land Without a Computer Science Degree for practical roles that don’t require a CS degree.