Autumn centralizes billing state, credits and entitlements for AI SaaS products

Autumn is billing infrastructure for AI and usage-based SaaS teams that do not want subscription state, credit ledgers and entitlements scattered across code, a database and Stripe webhooks. It is a developer-facing control layer, not a payment processor replacing Stripe.

What it does

Autumn says it becomes the source of truth for subscription state, balances, feature access and usage enforcement. Its core operations are modeled around checkout, tracking usage and checking whether a customer can access a feature or has credits left. The docs describe support for subscriptions, credits, rollovers, grants, spend caps, overages, seat allowances, enterprise contracts and pricing changes. Autumn docs ↗

The product’s advantage is change management. An AI company can move from free plans to credits, metered usage, multiple subscription groups or custom enterprise terms without rebuilding every Stripe product ID and access check. Autumn is open source and sits on top of the customer’s Stripe account; the docs say subscriptions, customers and payment details remain in Stripe.

Price and tradeoffs

The public pricing page lists Free at $0 per month with 8,000 monthly billing volume, 10,000 customers and entities, and 10 million API requests. Pro is $375 per month with 50,000 monthly billing volume, unlimited customers and entities, usage aggregation and data-warehouse integrations; Scale is custom. Stripe fees still apply. Autumn pricing ↗

The tradeoff is centralizing access state in another system. Autumn’s docs say its SDK defaults to fail-open and fail-fast when it cannot be reached, which can temporarily grant additional access; teams need to decide whether that behavior fits the product and revenue risk. The same docs describe self-hosting, data export and a gradual migration path. Those are useful controls, but they do not remove the need to test proration, concurrency, refunds, failed payments and entitlement drift in the buyer’s exact stack.

The YC profile ↗ identifies Ayush Rodrigues as a former Checkout.com product manager and John Yeo as a software engineer and Imperial College London computer-engineering graduate. That background maps directly to the billing and developer-experience problem.

My editorial take

I would shortlist Autumn when an AI product is already changing plans or usage rules faster than its billing code can safely keep up. The Free tier is enough to model the state machine. Move to Pro when the team needs production volume and aggregation; keep a rollback path in the app until failure-mode behavior is proven. For simple fixed subscriptions, Stripe alone may be the smaller system.

Quick facts

Sources checked

Autumn’s YC profile, homepage, pricing page and docs were checked on 2026-09-19.

Cohort context

Autumn is listed in Summer 2025. In our 2026-09-18 directory snapshot, 112 of 166 listed companies in that cohort have YC’s primary industry label B2B (67.5%). This is a current-directory comparison, not an original intake count or a performance ranking. Nine-cohort dataset.

Public website snapshot

Observed 2026-09-19 16:17 UTC in raw homepage HTML. This records visible metadata and advertised links, not agent execution or product quality.

Public observations · Collection method. Missing links here do not establish that a capability or file is absent elsewhere.