DaisyUI
How DaisyUI found the one feature no other payment provider had: built-in revenue splits
“It was like a key feature that I was looking for. Creem has this and it works really well. I am really satisfied with it.”
Pouya Saadeghi
Creator of DaisyUI
About DaisyUI
DaisyUI is one of the most popular UI component libraries for Tailwind CSS, trusted by engineers at Meta, Amazon, Adobe, Google Cloud, and thousands of indie developers around the world. What started as a Tailwind CSS plugin has grown into a full design system — 65+ components, 500+ utility classes, and a thriving community. Behind the polished components is a lean team, and like many successful developer tools that monetize, DaisyUI offers collaborative products built by multiple contributors who share the work — and expect to share the profits.
The feature gap that made the switch inevitable
Some products are solo-built. DaisyUI has collaborative products — projects where two people put in the work and both deserve a share of what it earns. LemonSqueezy didn't have a native way to handle this. Revenue splits had to be managed manually, which means spreadsheets, transfers, and trust — none of which scale cleanly. Creem's built-in revenue split feature solved this natively. Pouya had spoken with Creem's CEO early on and received early access to try it. He did. It worked exactly as expected. That was enough.
Revenue splits: profit sharing without the plumbing
Creem's revenue split feature lets sellers automatically divide earnings from any product between multiple parties at the payment level — no manual transfers, no post-payout calculations, no third-party tools. For DaisyUI's collaborative products, this means two contributors can set their split once and Creem handles the rest on every transaction. It's the kind of infrastructure that sounds simple but is notoriously annoying to build yourself — and Creem ships it out of the box.
Lower fees and faster support as added wins
Beyond revenue splits, the economics were compelling. Creem's fees are lower than LemonSqueezy's — and at the margins where digital products operate, that difference compounds quickly. Customer support was another standout. Every time Pouya had a question, feedback, or an issue to raise, he heard back within a day. For a widely-used library with real users depending on it, that kind of responsiveness from a payments provider isn't a nice-to-have — it's essential.
Migration done in hours, on their own terms
Migrating a payment provider is never trivial. Pouya chose to migrate DaisyUI's products manually — not because the process forced him to, but because it was an opportunity to clean things up at the same time. The migration took a few hours and went smoothly. No surprises, no data loss, no disruptions to existing customers. Everything carried over cleanly, and the manual approach meant he had full visibility and control over exactly what moved.
Key takeaways
Ready to switch?
Join DaisyUI and thousands of other companies using Creem for smoother payments.
Start selling like DaisyUI