Autumn

Autumn sits between Stripe and your application so pricing stops leaking into your codebase. Products and plans are defined on a dashboard, your app makes a few calls, and upgrades, downgrades, cancellations, failed payments and webhooks stop being yours to maintain.

The argument behind it is that billing infrastructure gets complicated faster than teams expect. Payments are the easy half; the rest is permission management, metering, usage limits driven by cron jobs, and the race conditions that appear when all of that meets a plan change. Kept outside the application, a pricing experiment no longer starts with a database migration.

Three calls carry the integration. attach handles every purchase flow, returning a Stripe Checkout URL or processing an upgrade or downgrade. check asks whether a customer has access to a feature or has usage remaining. track records a usage event when a metered feature is consumed.

Any pricing model can be assembled from those pieces, including the common ones.

• Usage and overage: real-time limits reset on a schedule you choose, and customers are charged for going over.
• Credits: monetary or arbitrary credits that many features can draw from.
• Seat-based: customers are billed for their own users, each seat carrying its own limits.
• Pay upfront: a fixed quantity of a feature is bought in advance and used over time.
• Custom plans: large accounts are handled without altering application code.

Self-hosting needs bun, one install and one command, plus your own Postgres connection string if you want it. A hosted cloud version is available.