Problem

AI startups increasingly need pricing that combines subscriptions with usage-based charges, credits, limits, top-ups, overages, seats, and custom enterprise terms. Stripe handles payments but leaves the application to coordinate subscription state, webhooks, feature permissions, usage metering, credit ledgers, and edge cases such as upgrades, failed payments, proration, and concurrency. The result is substantial engineering and maintenance work, while frequent pricing changes can require new product and price IDs, database migrations, and rebuilt application flows.

The killer use case is an AI product that must decide in real time whether a customer can perform a metered action—such as sending an AI message or consuming tokens—and then deduct or record that usage reliably. Autumn targets the pain of enforcing those limits while keeping billing accurate, so startups can monetize variable AI consumption without building a fragile billing system themselves.

Product / Service

Autumn is open-source billing and entitlement infrastructure that sits between an application and Stripe. It becomes the system of record for subscription state, usage, credits, balances, and feature access, while Stripe remains the payment processor and owner of the underlying customer and subscription data. Customers can use Autumn through its cloud service or self-host it.

Developers define products, plans, features, limits, and pricing in Autumn, then integrate a small API centered on attaching a plan or purchase, checking access or remaining usage, and tracking consumption. Autumn creates and manages the corresponding Stripe subscription, provisions balances, handles upgrades and downgrades, and enforces entitlements in real time. The benefit is that pricing changes and custom deals become configuration changes rather than application rewrites, while teams avoid managing billing webhooks and duplicated state across their codebase, database, and Stripe.

Market

Autumn competes in billing infrastructure and monetization infrastructure for AI and SaaS companies, particularly the emerging usage-based billing and entitlement-management segment. Its positioning is broader than a conventional metering product: the company differentiates itself from Orb and Metronome by combining usage tracking with real-time feature gating, credit balances, subscription state, and access control. Stripe is the underlying platform it complements, as well as the build-directly-on-Stripe alternative; other adjacent usage-billing platforms include Lago and Togai.

Autumn appears to be an early but active company rather than a purely pre-product project. Y Combinator lists it as an active Summer 2025 company, and the company says it is used in production by hundreds of developers and by YC startups processing millions. Its open-source repository had a substantial public footprint in the research snapshot—2,625 stars, 234 forks, and 9,747 commits—and supports both cloud and self-hosted deployment. Public evidence reviewed here does not establish revenue or customer concentration, so its commercial scale should be treated as unquantified even though developer and production traction are evident.