Skip to main content
Autumn’s data model has a clear pipeline: you define features, bundle them into plans with pricing, and when a plan is attached to a customer, it creates a subscription and provisions balances that you can check and track in real-time.

​
Features

Features represent the parts of your product you want to control access to. There are three types: boolean (on/off flags like premium analytics), consumable (usage that resets, like API requests or credits), and non-consumable (persistent quantities like seats or storage). Features are the atomic building blocks — everything else is built on top of them.

Features

Learn about feature types and how to create them

​
Plans

Plans bundle features together with a base price. Each plan represents a distinct pricing tier or package you offer — free, pro, enterprise, or any add-on. You define which features are included, how they’re priced, and any properties like trials or auto-enable.

Plans

Learn about plan pricing, properties and groups

​
Plan Items

When you add a feature to a plan, it becomes a plan item with its own configuration. Included items grant a usage amount at no extra cost. Priced items add billing — either prepaid or usage-based — with options for billing units, tiers, and proration. Plan items are where the “what” (features) meets the “how much” (pricing).

Plan Items

Configure grants, pricing and usage models

​
Subscriptions

When you attach a plan to a customer, Autumn creates a Stripe subscription under the hood and provisions balances for each feature in the plan. Subscriptions track status (active, trialing, past_due, etc.) and handle the payment lifecycle.

Subscriptions

How Autumn manages Stripe subscriptions

​
Balances

Balances are the customer-facing result of everything above. Each plan item becomes a balance that tracks what the customer has been granted, what they’ve used, and what remains. Balances from multiple sources (plans, add-ons, top-ups) stack together, with shorter-interval balances consumed first. Your app interacts with Autumn primarily through balances — calling /check to gate access and /track to record usage.

Balances

Understand balance stacking, resets and deduction order

​
Runtime

Once your features, plans and pricing are configured, your app interacts with Autumn through four core endpoints.
  • Customer: Idempotent get-or-create. Call on every login/signup and Autumn returns the existing customer or creates a new one. Aggregates subscriptions, balances, invoices and payment methods in a single response.
  • Attach: Subscribe a customer to a plan or purchase a one-time product. Handles new subscriptions, upgrades, downgrades and add-ons, creating the Stripe subscription and provisioning balances automatically.
  • Check: Feature gate. Returns whether a customer has access based on their active plans and remaining balance. Set send_event to atomically deduct usage while checking.
  • Track: Record usage against a customer’s balance. Each call decrements the remaining allowance for a feature, powering metered billing and usage limits.