Chargebee
Subscription billing and revenue management for recurring businesses
Autumn
Plug‑and‑play billing layer for any pricing model
Autumn provides a lightweight integration between your app and Stripe, enabling subscriptions, credits, usage‑based billing, and custom plans without handling webhooks, upgrades, or payment failures.
Overview
Overview
Autumn is a thin abstraction over Stripe that lets developers embed full‑featured billing with just three API calls: attach for purchases, check for access verification, and track for usage events. It supports subscriptions, credit systems, usage‑based overages, seat‑based licensing, and upfront feature bundles, all configurable from a web dashboard.
Who it’s for & Deployment
Designed for SaaS teams and product engineers who want to decouple billing logic from their core application, Autumn can be run as a hosted cloud service for rapid onboarding or self‑hosted via Docker with a PostgreSQL backend. The self‑hosted path requires bun, Docker, and a Postgres instance, but gives full control over data and environment. Once deployed, you manage products and plans in the dashboard, then call the three functions from your TypeScript code, letting Autumn handle Stripe Checkout, webhook processing, upgrades, downgrades, cancellations, and payment failures automatically.
Highlights
Unified API for attach, check, and track actions
Supports subscriptions, credits, usage‑based overages, and seat‑based plans
Handles Stripe webhooks, upgrades, downgrades, and cancellations internally
Self‑hostable via Docker or available as a cloud service
Pros
- Reduces billing logic in application code
- Flexible pricing models out of the box
- Built‑in Stripe integration removes webhook complexity
- Can be self‑hosted or used as SaaS
Considerations
- Requires PostgreSQL and Docker for self‑hosting
- Learning curve around Autumn’s API functions
- Limited to Stripe as payment processor
- Custom UI beyond dashboard must be built by developer
Managed products teams compare with
When teams consider Autumn, these hosted platforms usually appear on the same shortlist.
Looking for a hosted option? These are the services engineering teams benchmark against before choosing open source.
Fit guide
Great for
- Startups needing rapid billing feature rollout
- SaaS products with evolving pricing structures
- Teams that want to separate billing from core app logic
- Developers comfortable with TypeScript and Docker
Not ideal when
- Companies requiring multiple payment gateways
- Projects without PostgreSQL or Docker environment
- Very simple one‑time purchase sites
- Teams that need a fully managed enterprise billing suite
How teams use it
Subscription SaaS with tiered plans
Launch monthly/annual plans, handle upgrades/downgrades, and automatically enforce usage limits.
Credit‑based AI token consumption
Allocate token credits, track usage, and bill overages without custom code.
Seat‑based enterprise licensing
Bill per user seat, enforce per‑seat caps, and allow bulk custom plans for large customers.
Pay‑upfront feature bundles
Sell fixed‑quantity feature packs that decrement as users consume them.
Tech snapshot
TypeScript95%
Lua3%
PLpgSQL1%
JavaScript1%
CSS1%
Shell1%
Frequently asked questions
Do I need to use the hosted Autumn service?
No, you can self‑host via Docker and a PostgreSQL database, or run the cloud version for quick start.
Which payment processor does Autumn work with?
Autumn is built on Stripe and uses its Checkout and billing APIs.
How are webhooks handled?
Autumn abstracts webhook processing internally, so you don’t need to implement them yourself.
What environment is required for self‑hosting?
Node‑compatible runtime (bun), Docker, and a PostgreSQL instance.
Can I customize the billing dashboard?
The default dashboard is provided, and you can extend it by modifying the React components in the repo.
Project at a glance
Active- Stars
- 2,305
- Watchers
- 2,305
- Forks
- 177
LicenseApache-2.0
Repo age1 year old
Last commityesterday
Primary languageTypeScript
Last synced yesterday