Autumn Review (2026): Pricing, Features & Honest Verdict

Reviewed by MakerStack · Published · 4 min read

TLDR

Autumn is a YC-backed, open-source billing infrastructure layer over Stripe that makes usage-based pricing, credits, and subscriptions work in 3 API calls with zero webhooks. Best for: AI startups implementing complex billing. Price: Free up to $8K monthly revenue, then $375/month. Rating: 7.9/10

What is Autumn?

We found Autumn through Product Hunt’s weekly leaderboard where it was a top product in August 2025 with 574 upvotes. Built by YC S25 founders Ayush Rodrigues (ex-Checkout.com PM) and John Yeo (Imperial College London engineer), Autumn is middleware that sits on top of Stripe and eliminates the complexity of implementing usage-based billing, credits, and subscription management.

The pitch is simple: billing infrastructure takes weeks to build properly, especially if you need usage-based pricing, credit systems, or metered billing. Stripe handles payments but leaves the hard parts (tracking usage, enforcing limits, managing plan transitions) to you. Autumn abstracts all of that into 3 API calls.

Key Features

Three API Calls

The entire API surface is three endpoints. /attach (or /checkout) handles purchases and returns Stripe Checkout URLs. /check validates whether a customer can access a feature based on their plan and usage limits. /track records usage events for metered billing. That simplicity is the core product promise, and it delivers.

Credits, Usage Limits, and Metered Billing

Built-in support for credit systems, top-ups, periodic resets, rollovers, and overage billing. This is critical for AI startups that charge per API call, per token, or per generation. Most billing tools treat usage-based pricing as an afterthought. Autumn treats it as the primary use case.

No Webhooks Required

Autumn handles all Stripe webhook complexity internally. If you have ever debugged a webhook failure at 2 AM because a subscription renewal did not process correctly, you understand the value of never writing another webhook handler.

Pre-Built React Components

Ships with shadcn/ui-compatible pricing tables, paywalls, and checkout dialogs ready to embed. These are not generic components. They connect directly to your Autumn-defined plans and update automatically when you change pricing in the dashboard.

Pricing

Autumn charges flat fees based on your monthly revenue band. No percentage-based transaction fees from Autumn (standard Stripe fees still apply):

  • Free: $0/month. Up to $8K monthly revenue. 10 products. Discord support.
  • Startup: $375/month. $8K-$50K monthly revenue. Unlimited products. Slack support.
  • Growth: Custom pricing. $50K+ MRR. Unlimited products. Dedicated Slack support.

The free tier is genuinely generous. Most startups will not outgrow it until they are making real money, and at $8K MRR you can easily justify $375/month for billing infrastructure you did not have to build or maintain.

PlanPricePlan FeaturesBest For
Free$0Up to $8K monthly revenue, 10 productsEarly-stage startups
Startup$375/month$8K-$50K MRR, unlimited products, Slack supportGrowing startups
GrowthCustom$50K+ MRR, dedicated supportScaling companies

Who is Autumn Best For?

AI startups that need usage-based or credit-based billing. SaaS companies implementing complex pricing models (subscriptions + usage + credits). Seed to Series A companies with revenue between $0-$50K MRR. Technical founders who want to ship pricing fast without spending weeks on billing infrastructure.

Pros

  • Radically simple API (3 endpoints) eliminates weeks of billing infrastructure work
  • Free until $8K MRR is perfect for early-stage startups
  • Open source (Apache 2.0) with 2,400+ GitHub stars and active community
  • YC-backed with notable angel investors (Paul Graham, founders from Heroku, Supabase, Sentry)

Cons

  • Only works with Stripe, limiting options for teams using other payment processors
  • Two-person team means support capacity is limited compared to established billing platforms
  • Still early, so enterprise features like SSO and advanced permissions are not yet available
  • $375/month jump from free can feel steep for companies just crossing $8K MRR

Alternatives

Stripe Billing

Stripe’s native subscription and usage billing handles basics well but requires significant webhook wiring and custom code for complex models. If your billing is straightforward subscriptions, Stripe Billing alone is fine. If you need credits, usage caps, or metered pricing, Autumn saves you weeks.

Lago

Open-source billing platform with 8,900+ GitHub stars (vs Autumn’s 2,400+). Stronger community adoption and focuses on real-time event metering. More mature and feature-rich but significantly more complex to set up and operate. Better for teams that want maximum control over their billing stack.

Orb

Purpose-built for usage-based billing with high-volume event ingestion and plan versioning. More enterprise-focused with custom pricing. If you are processing millions of billing events, Orb handles the scale better. For most startups, it is overkill.

FAQ

Does Autumn replace Stripe?

No. Autumn sits on top of Stripe. You keep your Stripe account and Autumn manages subscriptions, usage tracking, and feature access through Stripe’s APIs. Payments still flow through Stripe.

Can I self-host Autumn?

Yes. Autumn is open source under the Apache 2.0 license. Self-hosting is available via Docker Compose. The cloud version at app.useautumn.com is the easiest path for most teams.

How long does integration take?

The 3-API-call design means basic integration takes hours, not weeks. Define your plans in the dashboard, add the three endpoints to your app, and billing works. The pre-built React components speed up frontend implementation further.

Verdict

Autumn solves one of the most tedious problems in SaaS development: billing infrastructure. The 3-API-call design is not just marketing. It genuinely reduces weeks of work to hours. The free tier until $8K MRR removes all risk for early-stage startups, and the open-source Apache 2.0 license means no vendor lock-in. The main concern is the two-person team, which limits support capacity and feature velocity compared to established players like Lago or Stripe Billing. But for AI startups that need credits and usage-based billing without the infrastructure headache, Autumn is currently the best option at its price point.

Autumn Pros & Cons

What We Like

  • Radically simple 3-endpoint API eliminates weeks of billing work
  • Free until $8K MRR is perfect for early-stage startups
  • Open source (Apache 2.0) with 2,400+ GitHub stars
  • YC-backed with notable angels (Paul Graham, Heroku/Supabase founders)

What Could Be Better

  • Only works with Stripe, no other payment processor support
  • Two-person team limits support capacity
  • Enterprise features like SSO not yet available
  • $375/month jump from free can feel steep at $8K MRR

Autumn FAQ

Does Autumn replace Stripe?

No. Autumn sits on top of Stripe. You keep your Stripe account. Payments still flow through Stripe.

Can I self-host Autumn?

Yes. Open source under Apache 2.0, self-host via Docker Compose or use the cloud version.

How long does integration take?

Basic integration takes hours, not weeks. Define plans in the dashboard, add three endpoints, and billing works.

What is Autumn?

YC-backed, open-source billing infrastructure over Stripe. Implements usage-based pricing, credits, and subscriptions in 3 API calls with zero webhooks.

How much does Autumn cost?

Autumn pricing starts at Free (up to $8K MRR). A free plan is available.

Is Autumn worth it?

Autumn solves one of the most tedious SaaS problems: billing infrastructure. The 3-API-call design genuinely reduces weeks of work to hours. Free until $8K MRR removes all risk. For AI startups needing credits and usage-based billing, currently the best option at its price point. We rate it 7.9/10.

Disclosure: MakerStack is funded by featured placement fees, sponsor slots and a small number of affiliate links. Nobody paid for this review. Where any of those does apply to a review, we say so on the page. The scoring criteria are the same in every case. See our editorial policy.