Hey HN,
We just finished the YC batch and saw how long founders spent implementing pricing.
A few years ago SaaS pricing was just a monthly subscription. But AI companies today have many pricing options they want to experiment with: eg credit systems, usage based systems, top ups etc.
Building this in-house, with upgrades, downgrades, pro-ration, free trials, just sucks.
Similar to how Clerk 'solved' Auth for people that don't want to waste time building non-core features, I think we can do something similar for pricing.
I built an abstraction over Stripe to create any price model (subscriptions, usage-based, credits, trials etc), then embed it in a couple lines of code.
1. use /attach when a customer purchases a plan. A Stripe checkout URL is returned if needed.
2. use /entitled to check if a customer has access to a plan or specific features.
This means no more dealing with webhooks, syncing subscription states etc. It's all open source and I'd love to hear your feedback!
We just finished the YC batch and saw how long founders spent implementing pricing.
A few years ago SaaS pricing was just a monthly subscription. But AI companies today have many pricing options they want to experiment with: eg credit systems, usage based systems, top ups etc.
Building this in-house, with upgrades, downgrades, pro-ration, free trials, just sucks.
Similar to how Clerk 'solved' Auth for people that don't want to waste time building non-core features, I think we can do something similar for pricing.
I built an abstraction over Stripe to create any price model (subscriptions, usage-based, credits, trials etc), then embed it in a couple lines of code.
This means no more dealing with webhooks, syncing subscription states etc. It's all open source and I'd love to hear your feedback!