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.
Interesting , What's one thing most unique about creem? that's you are proud of !
Creem
Thanks @easeops The one I'd pick: you set a revenue split or an affiliate commission once, per product or store-wide, and every sale pays out to each person automatically. All on top of Creem as merchant of record, so tax and compliance in 190+ countries are handled. What are you building?
Super cool :). Waiting for Creem Atlas, for agent-based Delaware company creation + Creem Treasury for banking :)
Creem
TY@michael_yagudaev ! We don't do company formation yet ;) What's live in that direction: the Partner Plan comes with a Visa card to spend your Creem balance, and payouts to a bank account or stablecoin on demand. What are you building and we can talk!
Creem
@michael_yagudaev 😎
@sudoferraz Nice! I'm building on Convex, any integration there or am I wiring webhooks by hand?
Creem
@thongyj87 glad you like what we are building. There's a Convex component for Creem, so no hand-wiring: it handles checkout, subscriptions and the webhook events for you - more on our docs page. What are you building on Convex?
Creem
@thongyj87 Hey Jason!
Great to see a familiar face around here! Btw we actually allow the creation of webhooks through the API, CLI and SDKs! So now you can even give that to your AI agent!
Hey team, nice work. Not sure if this is a dumb question but if I put checkout on my domain, could I also have a little store page there? I don't have a website yet, just a product.
Creem
@valentin_manes1 Not dumb at all. The hosted storefront is served at the root of your custom domain, with views and orders tracked in the dashboard. What product are you selling?
Creem
Hey Product Hunt! 👋 Märt here
I run Merchant Success at Creem — basically I spend my days watching how people actually get from "just signed up" to "took my first real payment," and removing every bit of friction in between.
That's the lens I look at 2.0 through. A lot of MoR platforms make you feel like you've been handed a compliance homework assignment before you can sell anything. We've been obsessed with the opposite: get a store live, get products in, get a checkout that converts — fast — and let Creem quietly handle the tax, fraud, disputes and payouts underneath.
The feature I'm most excited about is how much of the setup is now self-serve and fast. You can import your existing site, get your catalog pulled in, and be selling globally without hiring anyone to babysit it.
The thing I love most is honestly just reading the data every morning and seeing more merchants cross that first-real-payment line. If you're onboarding and something feels clunky, ping me here — I read all of it and half our roadmap comes from exactly that.
Creem
Hey Product Hunt! 👋 Slava here, CTO at Creem 🍦
I run engineering, and for 2.0 my own corner was the billing and developer side: usage-based billing with credit wallets, checkout on your own domain, and a CLI with full API coverage.
If you can ship a product in a weekend, you shouldn't need a week to start charging for it. So the rule for 2.0 was simple: everything you can do in the dashboard, you can do from the API, the CLI, and our MCP server. Creem is meant to be run by an agent as much as by a person. Point Claude Code or Cursor at it, and it can create products, wire up webhooks, ship a checkout, and watch your first sales come in, without you reading a single reference page.
The part I spent the most nights on is billing. When we surveyed merchants this summer, nearly every serious "usage-based" request came from an AI product whose cost of goods is inference tokens. Nobody asked for pure pay-per-use. They asked for subscription plus overage, and prepaid credits that top up automatically instead of cutting a user off at the cap. So that's what we built: a credit wallet per customer, custom meters drawing against it, and tax and invoicing handled by us as merchant of record, same as any other sale.
Custom-domain checkout was our most-upvoted request by a wide margin. Your checkout now lives on your own subdomain: point a CNAME at us, TLS is issued automatically, and you're live.
If you're integrating today and something is missing from the API, or the docs let your agent down, reply here.
I'm around all day, and that's the fastest way to get it onto the roadmap.
Questcity
Congratulations with the launch on Product Hunt! Question > how you differs from Stripe and why should SME start using Creem?
Creem
Hey Grigori, good question!
In short: Stripe is a payment processor, you stay the seller so the tax, VAT and compliance is your problem. Creem is a merchant of record (MoR), so we become the seller of record and handle all of that for you. For a small team that means no tax registrations in 40 countries, no chargeback handling, no invoicing headaches. You just ship and get paid. 👌🏼
Saw you're building Questcity, that must mean travelers buying from all over. How are you handling VAT across all those countries today?