@emmettm This is so spot-on it hurts. I remember spending a ridiculous amount of time gluing Supabase + Stripe + some hacked-together roles logic just to get a basic paywall working—and even then it felt fragile.
Update looks like the infra glue we’ve all been duct-taping ourselves. One SDK to rule the boring parts—auth, billing, permissions—so we can stop reinventing the wheel and actually build the product. Big fan of the stack flexibility (FastAPI folks rise up 🙌), and the fact that you’re not forcing a UI but giving the option is chef’s kiss.
I’d love to hear how you handle more advanced usage-based billing patterns (e.g. tiered, rollover credits) and what’s coming next in terms of dashboards or webhook/event integrations.
HabitGo
@emmettm This is so spot-on it hurts. I remember spending a ridiculous amount of time gluing Supabase + Stripe + some hacked-together roles logic just to get a basic paywall working—and even then it felt fragile.
Update looks like the infra glue we’ve all been duct-taping ourselves. One SDK to rule the boring parts—auth, billing, permissions—so we can stop reinventing the wheel and actually build the product. Big fan of the stack flexibility (FastAPI folks rise up 🙌), and the fact that you’re not forcing a UI but giving the option is chef’s kiss.
I’d love to hear how you handle more advanced usage-based billing patterns (e.g. tiered, rollover credits) and what’s coming next in terms of dashboards or webhook/event integrations.
Definitely keeping an eye on this 👀
HabitGo
@emmettm I love it
Product Hunt Dark Screen
Whoops! Got another Auth provider