{"id":33432051,"user":"brycelarkin","time":1667371218,"time_ago":"3 years ago","type":"comment","content":"

How is this better than the Stripe Terraform provider? https://registry.terraform.io/providers/franckverrot/stripe/...","comments":[{"id":33434514,"user":"jmacd","time":1667391501,"time_ago":"3 years ago","type":"comment","content":"

I like that provider and it's really useful in a lot of situations. Configuring Stripe as it is currently designed doesn't always help as much for SaaS and infrastructure billing models. We wrote here about how we map to Stripe https://www.tier.run/docs/mapping/

Even after Stripe has been set up, you then get our SDK (node available, Go shortly) which gives you things like .subscribe(), .report(), .whois() (gets stripe ids) and .limits() that you can use to tool your app. The benefit is that when you change your plans or pricing, you don't need to refactor your front end. These are the benefits of the pillars on https://priceops.org

The CLI also acts as a sidecar in your network to do things like rollups and it manages Stripe pretty gracefully (Stripe can often have rate limits or requirements that aren't always clear). It also handles metering for you via the above referenced methods.

Someone made another comment on this thread that outlines some of the benefits vs Stripe raw as well. https://news.ycombinator.com/item?id=33431567","comments":[],"comments_count":0,"level":0,"url":"item?id=33434514"}],"comments_count":1,"url":"item?id=33432051"}

Comment by brycelarkin