autumn.config.ts
file.
You can export features
and products
from this config file, and push them to Autumn using npx atmn push
CLI functionality is in beta. Please let us know any issues you run into and
we’ll resolve them ASAP.
Feature
The features of your application that can be gated depending on pricing tier. These will be used to define your products.The ID of the feature that will be used via Autumn’s APIs.
The display name of the feature
One of
single_use
, continuous_use
, credit_system
or boolean
. See below
for examples.Feature Types
Single-use meter
Single-use features are those that can be used-up and replenished. They may have a reset interval (eg 200 per month). Examples: AI messages, credits, API calls.Continuous-use meter
Continuous-use features are those used on an ongoing basis. They do not reset periodically and may be prorated when billed for. Examples: Seats, storage, workspaces.Credit system
Use a credit system when you have multiple metered features that each cost a different amount. Eg, if a basic model message costs 1 credit, and a premium message costs 5 credits.If you set the price per credit to be 1 cent when you create your products,
these can be used as monetary credits (eg 0.05 USD per premium message)
Boolean
A feature flag that can be enabled or disabled.Products
Products are made up of features and prices, and define your pricing plans. You should create products for any free plans, paid plans and any add-ons / top-up products.The ID of the product that will be used via Autumn’s APIs.
The display name of the product.
Whether the product should be attached by default to new customers
Whether the product is an add-on and can be purchased alongside other products
(as opposed to trigger upgrade/downgrade flows)
An array of objects that define the product. Can be one of:
featureItem
: a feature to grant access to when the product is enabledpriceItem
: a fixed price to pay for the productpricedFeatureItem
: a feature that has a price associated based on usage or quantity purchased.
Item Types
Define your products using a combination of the 3 item types below.Feature Item
A feature that is included with the product.Feature ID for the product item
How much usage is included with this item. This acts as a usage limit. Not
applicable for boolean features.
month
| hour
| day
| week
| quarter
| semi_annual
| year
How often the feature’s balance should be reset back to the included_usage.
Set as null
for one-time grants.The entity feature to assign this item to: eg, seats. This will set a usage
limit at the entity level (eg, 10 message per seat per month)
Price Item
A fixed price to be charged with the product: either one-time or a subscription.A fixed amount to charge for this product
month
| quarter
| semi_annual
| year
How often this price should be billed to the customer. Set as null
for
one-time prices.Priced Feature Item
A price to be charged based on the usage or prepaid quantity of a feature.Feature ID for the product item
A fixed amount to charge per
billing_units
of this feature.The package quantity that the price is charged in (eg 5 USD for 100 messages)
prepaid
| pay_per_use
Whether the feature is charged based on how much is used (pay_per_use
), or if a fixed quantity is purchased upfront (prepaid
).For continuous use meters that are pay_per_use
(eg paying per seat used), you can define billing behavior in the dashboard (eg, whether to bill immediately or at the end of the cycle).How much usage is included with this item.
month
| quarter
| semi_annual
| year
How often this price should be billed to the customer. Set as null
for
one-time prices.The entity feature to assign this item to: eg, seats. This will set a usage
price at the entity level (eg, 0.01 USD per message per seat per month)