Lark

Problem 🔴

Too often, customers tell us they use Stripe for billing but when I ask how they manage their credits or track usage, I always hear the same answer: “we built it in-house”. These pricing models are not edge-cases. They’re the new normal in the age of AI.

Solution ⚒️

uselark.ai is a modern billing platform with the flexibility to support any pricing model (credit-based, usage-based, hybrid, dimensional, token-based, etc…) at any scale (10x more than Stripe).

Whether you’re building an AI powered API or a B2B SaaS product, Lark provides everything (including checkout + customer-facing portal) you need to implement complex billing logic without the hassle.

A few nice things about us -

• You don't have to manage any webhooks or store custom billing state (like stripe customer id) in your database
• Our APIs are simple. You don't have to integrate with a separate checkout API. We also provide frontend SDKs to check billing state (like remaining credits, feature access)
• Seamless pricing changes that automatically apply to your customers without involving engineers
• We also help you track margins & LLM costs per customer for AI applications

📘 Quickstart: https://docs.uselark.ai/

Checkout + customer-facing portal included

No separate APIs, state management, or webhooks

Customer-facing portal includes real-time usage and subscription management

Scalability

Lark supports up to 1M events per second so you don’t have to worry about pre-aggregating your data.

Team

Vijit and Jack both previously built the usage based billing and customer portal product at Stripe.