Built on Stripe as the source of truth
Billing Built for Agents, Not Humans
Seven typed entities for the full billing lifecycle — customers, subscriptions, invoices, and payments. Backed by Stripe, driven by events.
Why Typed Billing?
Stripe-Native
Every entity maps to Stripe objects. IDs sync automatically — no webhook plumbing.
Event-Driven
React to cancelled(), paid(), and upgraded() events across the billing graph.
Type-Safe
Every field, enum, status, and relationship is typed end-to-end in TypeScript.
The Billing Workflow
From product catalog to payment — three workflows that cover all seven entities.
Products, Plans, and Prices
Create products, attach plans with trial periods, then set prices by interval.
Product types: Software, Service, Addon, Bundle
Plans with trial days and feature limits
Prices: Monthly, Quarterly, Yearly, OneTime
Beyond CRUD
Events and pipelining turn static billing entities into a reactive revenue engine.
Subscribe to lifecycle events across the billing graph — trigger invoices, notifications, and workflows from typed verbs.
Chain operations across the billing graph in a single round-trip. Built on rpc.do + capnweb.
Frequently Asked Questions
Start Billing in Minutes
Seven typed entities for the full billing lifecycle. Stripe-native. One install.
- 7 Entities
- Stripe-Native
- Event-Driven
