Recklessnesz

@garGoel91 @dodopayments 4/4 Something that I am looking for is like the following flow: 1. user creates an account, 2. user creates an org (customer get created), 3. user chooses a subscription plan for their org, 4. checkout on behalf of the org.

@garGoel91 @dodopayments 1/4 We can take any collaborative app as an example. Let's go with Notion. A user can create a workspace for their business, where they invite coworkers for collaboration (in better-auth a workspace = org).

We’re excited to introduce Usage-Based Billing (Beta) at Dodo Payments. 🥳 Now you can track usage in real-time, apply flexible meters, and bill customers based on actual consumption, perfect for SaaS, APIs, and AI-native products. Scale globally with billing that adapts to your growth. ✨

@garGoel91 @dodopayments 3/4 In this example, I wouldn't like creating a dodopayments customer for each registered user as majority of them would never be charged (e.g. 1 workspace with 20 coworkers), but instead, would like creating it when a workspace (org) gets registered.

@garGoel91 @dodopayments 2/4 Everything that gets "consumed" is agreggated to the workspace level and billed to the workspace, where for businesses, the billing info is tied to a business and is not tied to a user (e.g. the one who created the workspace).

@PingStruggles Yes it will. Would be nice to have an example in docs how to implement team roles via FGA as it might be a common use-case. Thanks for the reply!

@recklessnesz I think that if we release FGA support it will solve your issue and others at the same time 🤔

What is something important but missing in BetterAuth?