Autumn

Key features

• Plans and pricing defined in code or the dashboard Developers create products, plans, prices, and features in TypeScript or through the dashboard, with type-safe helpers for checking entitlements and tracking usage. Pricing changes are versioned rather than edited live, which keeps plan history auditable.[1]

• Usage metering with event-based billing Applications send usage events through the SDK and Autumn aggregates them against plan limits, supporting seat, usage, and credit based models including features with unlimited allowances. Overage behavior and thresholds are part of the plan definition.[1]

• Stripe stays the system of record Autumn creates and manages the corresponding Stripe prices, subscriptions, and invoices behind the scenes, so finance keeps working in Stripe. Teams connect their own Stripe account instead of migrating payments to a new processor.[1][2]

• Embeddable pricing tables and checkout A React component library renders pricing tables, plan switching, invoice history, and checkout flows that call back into Autumn entitlements. This removes the need to build paywalls and billing pages from scratch.[1]

• Coupons, trials, add-ons, and free trials Plans support trial periods, coupon codes, one-off add-on products, and free-trial-with-card flows. These map onto Stripe coupons and trial configurations so promotional pricing stays consistent.[1]

• Entity-based billing for teams and agents A newer entity model attaches balances and feature access to objects such as organizations, projects, or AI agents rather than only to end users. This fits B2B SaaS with workspaces and credit pools shared across seats.[1]

• MCP server and agent integration Autumn ships a Model Context Protocol server so coding agents can scaffold plans, features, and paywalls from the repository context. The docs position agent-assisted onboarding as a supported integration path.[1]

• Analytics on revenue and feature usage The dashboard reports tracked revenue, new and upgraded customers, active subscriptions, trials, and per-feature usage over time. These are observed billing aggregates from Autumn-tracked events, not third-party market estimates.[1]

Who will love it

• SaaS teams pricing seats, usage, or credits Teams whose pricing mixes subscriptions with metered usage or credit pools get the most from Autumn, since entitlements, event tracking, and paywalls live in one layer. Flat single-plan products gain less.[1][2]

• Teams committed to keeping Stripe Shops that already process through Stripe and want to keep their Stripe dashboard, tax setup, and payment history will like that Autumn extends Stripe instead of replacing it. Migration risk stays low.[1][2]

• TypeScript shops that prefer code-defined pricing Codebases already in TypeScript or React can define plans beside application logic and render Autumn components directly. Teams outside that stack face more integration friction.[1][2]

Who should avoid it

• Teams avoiding Stripe or needing other processors Autumn is documented as built for Stripe; there is no documented support for Adyen, Paddle, or other processors. Teams that cannot use Stripe should choose a processor-agnostic platform instead.[1][2]

• Teams needing a self-hosted billing deployment The documented product is Autumn Cloud connected to your Stripe account, with no self-hosting guide in this pass. Regulated shops that must run billing inside their own boundary should verify or look elsewhere.[1][2]

• Non-technical founders without developers Every integration step assumes SDK calls, entitlement checks, and event tracking written by a developer. A solo non-technical founder will move faster with a hosted no-code billing page than with Autumn.[1]

Alternatives and compatibility