Ben Foster

Lessons for any AI team from GitHub Copilot's "usage-based billing" landing

GitHub Copilot announced a move to usage-based billing but kept the same fixed-fee subscription architecture under a new label. A cautionary read for every AI startup thinking about implementing usage-based billing.

PSP integration patterns for AI billing systems

Five PSP integration patterns shape how AI billing platforms fit with existing payment setups. Compare trade-offs and pick the pattern that fits your stack.

Credyt vs Lago

Lago offers open-source usage billing with paid premium features. Credyt provides real-time wallet billing with a portal included. When does it make sense to build vs buy?

How to implement consumption based pricing

Consumption based pricing requires more than code. Covers billing architecture trade-offs, the observability step most teams skip, and how to launch or migrate.

How Stripe's usage-based billing actually works (with code)

Step-by-step breakdown of Stripe's metered billing: object chain, meter events, webhooks, pricing changes, and customer portal. With working code examples.

Revenue Recognition for Usage-Based Billing: When Credits Become Revenue

Usage-based billing changes when revenue is recognized. Credits may look identical in product UI but behave differently under ASC 606 and IFRS 15 depending on whether they represent entitlements, commitments, or prepaid usage. This matters more for AI products where usage is spiky, costs are real, and regulators scrutinize when value is actually delivered.

How to bill AI products in custom units instead of dollars

Custom assets launched today in Credyt. Teams can now bill customers in credits, tokens, GPU hours, or any product-native unit instead of dollars. This is how platforms like Midjourney and Lovable handle monetization so that when infrastructure costs shift or pricing evolves, the credits customers purchased still work because billing happens in product units, not currency.