Reviews paint Creem as a cost‑effective, responsive MoR with smooth setup, fast payouts, and a clean UI. Users highlight low fees, strong support, and less hassle than Stripe or incumbents, though one tester flags duplicate product creation and pay‑as‑you‑go pricing quirks in the API. Maker feedback adds weight: makers of
the gist of praise rapid iteration and responsiveness, while makers of
Pod call it an easy Lemon Squeezy alternative. Overall, Creem stands out for speed, pricing, and attentive team execution.
This is interesting. Building the product is one thing, but figuring out payments, taxes, billing, and everything around actually selling it can get surprisingly messy. I like that Creem is trying to take that part off the founder’s plate. Looking forward to see how people are going to use the usage-based billing in real products.
Best wishes @sudoferraz and team :)
Creem
@sudoferraz @whatshivamdo Thanks for the kind words! Usage-based billing is something we're really excited about too - it unlocks pricing models that actually grow with your customers instead of forcing them into rigid tiers.
Are you running usage-based pricing in anything you're building, or exploring it for the first time?
@sudoferraz @paul_creem TBH, I haven't seen much products with usage based billing. So, consider it first time only.
But definitely an AI-native builder myself, I'm seeing myself there exploring it now with Creem :)
Creem
@sudoferraz @whatshivamdoThat's great to hear! Usage-based is a natural fit for AI products since your costs scale with usage anyway. With Creem you can set up custom meters and let the billing match exactly how your users consume the product - no overcharging on quiet months, no leaving money on the table on big ones.
What are you building? Would love to help you figure out the right metering setup!
Dial
Usage-based billing plus global tax handling in one platform is the hard combo to get right - most "merchant of record" tools I've looked at handle VAT/sales tax fine for flat subscriptions but get messy once you add metered/usage pricing on top, since the tax event and the billing event happen at different times. Does Creem calculate tax at time of usage accrual or at invoice time, and does that change per jurisdiction
Creem
@galdayan Tax is calculated when money moves, not when usage accrues. With prepaid credits that's the top-up (auto-refill included), on the gross, using the customer's location and VAT status from checkout. Consuming credits is not a tax event, so billing and tax are the same event everywhere; only the rate changes by jurisdiction. As merchant of record, filing is ours. Are you on prepaid credits or metered at period end?
Dial
@joosep_creem Not a customer yet, just evaluating options for our own usage-based pricing - but that answer actually settles the question I was circling. Collapsing billing and tax into the same event at top-up removes the whole "which jurisdiction rate applies to unconsumed credits" problem that trips up a lot of DIY tax setups. Makes sense why merchant-of-record is worth the cut for anyone doing metered pricing globally.
Creem
@galdayan Exactly that. The other half nobody expects: refunds. Refund a top-up and the tax has to be reversed in the jurisdiction it was collected in, which is where DIY setups break. That's ours too. When Dial gets to it, prepaid credits or metered at period end?
I’ve been using Creem for the past few days and honestly, I love it. The whole setup and payment flow feels incredibly simple and smooth, which is exactly what I want when launching a new product. Really impressed with how easy everything is so far. Hope Creem keeps growing — you guys are building something great!
Creem
Hi Vesa! Thank you, that genuinely made our day! 🙏🏼 Simple and smooth is exactly what we are going for, so good to hear it lands.
Quick one: how was the onboarding - was there anything you wish was different in the process? We're always looking for productive feedback. :)