Aceternity UI: 7 Free Components to Start, $80,000/Month Within 2 Months of the Paid Tier — a Two-Story Model

Note: dollar figures in this article are converted at roughly ¥150 per dollar for reference.

Server costs: $20/month (about ¥3,000). What he built in a weekend: 7 components. That free UI library eventually launched a paid tier and hit $80,000/month (about ¥12 million) within two months — this is the story of Aceternity UI, run by Manu Arora out of Jaipur, India.

The breakdown is $40,000 from the paid Aceternity UI Pro and $30,000 from custom development work, totaling $70,000, though the source states the month in question as $80,000 and the normal range as $60,000–$100,000. The figures are coarse-grained, and as we’ll cover below, the timeline doesn’t fully add up either. Even so, the case shows a clearly replicable skeleton: build distribution power for free first, then place the product on top of it later.

The disclosed numbers, and where they wobble

Let’s verify these numbers. The team size doesn’t match: the profile section lists “1 founder + 2 employees,” while the body text describes a “6-person team.” The expense math is strained too: feeding 6 people on roughly $5,000 in monthly expenses is hard to justify even accounting for Jaipur’s cost of labor. It’s likely that payroll isn’t included in that expense figure. Then there’s the timeline. The company is said to have been founded in March 2021, yet the body text also states “after running the free library for about 4 months, I built UI Pro” and “it’s been two months since [UI Pro’s] launch.” If March 2021 is the starting point, Pro would have launched within 2021 itself, leaving too large a gap before the recent $80,000 result. It’s most natural to read March 2021 as the founding date of Aceternity, the design studio, with the UI library itself launching considerably later, but the source alone can’t confirm this. Going forward, we’ll rely only on the relative figure of “two months since Pro’s launch” for timing.

He quit blogging and started giving away copy-paste code

The starting point was the attractive UI components Arora had been building for his own projects. He originally wrote a blog explaining how to build them.

Looking at his analytics, he realized readers weren’t reading the explanations. What people wanted was code they could paste in and have working immediately, not the tutorial. He dropped the blog and switched to a library of copy-paste components. This was the first decision.

The free library launched simultaneously on X and Product Hunt. Product Hunt brought in the initial users, but he states clearly that X was what drove sustained growth. A few months later, Fireship, a YouTube channel for developers, covered Aceternity UI. Exposure spiked, X followers reached 20,000, and word of mouth became the primary acquisition channel.

The one point where the tide turned

If you had to pinpoint the moment the trajectory changed, it wasn’t the day Fireship covered it, and it wasn’t Product Hunt’s launch day, but the sequencing itself: only after distribution power existed did he place a paid product on top of it.

Lined up before and after, it looks like this. During the free-library-only period, revenue was zero and expenses were just $20/month for Vercel. Once he had 20,000 followers and a word-of-mouth channel in place, he launched Aceternity UI Pro, and hit $40,000/month within two months. At the same time, custom development requests from people who’d seen the library generated another $30,000/month. The transition from zero to $70,000–$80,000 took two months, and the only new thing done in those two months was launching the paid tier.

Arora describes this as being able to “launch with almost zero friction.” Rather than building a product and then searching for customers, he placed the product afterward where customers were already gathered, a matter of sequencing.

Why this shape worked

For one thing, the free library functions as a demonstration device that costs nothing in advertising. UI components are a product category where quality is obvious the instant you see it. No explanation or comparison shopping is needed. A developer can paste it onto their own site and immediately confirm the effect. This near-zero verification cost is why word of mouth became the primary channel.

For another, the same asset generates two revenue streams simultaneously. Some developers who see the library buy the paid templates. Others ask to have something built for them. Structurally this resembles how an agency builds a portfolio of past work, except a freely distributed library reaches far further than a portfolio ever could, and every time it’s pasted onto someone’s site, exposure grows further.

And underneath both, Arora’s repeated principle of “giving value without expecting anything in return” is more than a mindset. It’s rooted in the nature of the inventory. Components cost almost nothing to replicate, so giving them away costs nothing to lose. Distribute a large volume of inventory that costs nothing to lose in order to capture awareness, then charge for what can’t be replicated, time, and more advanced templates, a two-story design.

His other line, “it’s better to write ugly code than to agonize over beautiful code no one uses”, is the flip side of the same philosophy. Publishing 7 components had more value than not publishing at all.

What didn’t work, and the limits

The blog he was writing didn’t work. This is less a failure than a withdrawal driven by measurement. A decision he couldn’t have made without analytics.

On reproducibility, the Fireship feature remains a major uncertain factor. Coverage on a developer-focused YouTube channel isn’t something you can buy, and since it explains part of the growth, following the same steps won’t guarantee the same curve. The 20,000 X followers also sit on top of more than seven years of accumulated content he’s put out while building products.

There are structural weaknesses too. The custom-dev revenue, which accounts for just under 40% of monthly revenue, scales with headcount, so the 6-person team is a direct ceiling on that revenue. The wide swing in the monthly revenue range ($60,000–$100,000) is naturally read as reflecting the volatility of custom-dev work. On top of that, the source discloses neither UI Pro’s price nor its billing structure, so it’s unclear how many sales make up that $40,000. Nor can we tell whether the “$100,000 MRR within a year” goal assumes a shift to subscriptions or is simply an extension of the current model.

How far can this be replicated?

What can be replicated is the sequence. Among the things you’re capable of building, choose something that costs nothing to replicate, whose quality is obvious at a glance, and that users can verify in an instant. Give it away completely to build a distribution channel, then place the paid version on top. This sequence itself requires neither capital nor connections.

The preconditions are clear too, though. The audience must be developers. Developers can evaluate technology themselves, pay for it themselves, and spontaneously share what they find good. Apply the same playbook to an audience with thin evaluation skills and weak sharing habits, and free distribution just ends up being a pure cost. Whether the advice “give it away for free” holds depends entirely on who you’re giving it to.

Related reading

• Carrd — a solo founder who started small around the periphery of web design and built up revenue without chasing scale
• Sidekiq — a classic case of monetizing long-term with a free open-source tier and a paid tier stacked on top