useautumn / autumn

Autumn Autumn is an open-source layer between Stripe and your application, allowing you to create any pricing model and embed it with a couple lines of code. On Autumn you can build: • Subscriptions • Credit systems & top ups • Usage-based models & overages • Custom plans for large customers All this without having to handle webhooks, upgrades/downgrades, cancellations or payment fails. Getting Started **Cloud**: The quickest way to start using Autumn is through our cloud service. **Self Hosted**: If you'd like to self-host Autumn: • Make sure you have installed • Install the project dependencies • Run our set up script: • Generate the relevant tables in your postgres DB • Run Autumn: For Windows For mac/linux: That's it! You should be able to see the Autumn dashboard on . > ⚠️ To log in, enter an email at the sign in page, and an OTP should appear in your console / terminal. Normally, we use Resend to email an OTP or Google OAuth -- these can be set up by providing your credentials in > ℹ️ Our set up script initializes the required env vars and (optionally) a Supabase instance. If you'd like to use your own Postgres instance, you can do so -- just paste the connection string in the env variable at Troubleshooting If you encounter a error when running again after previously running it, you may need to clear your database tables first. This is a known issue that can occur when running database migrations multiple times. To resolve this: • Connect to your database • Drop all existing tables • Run the setup script again: Why Autumn **1️⃣ Billing infra gets complex fast** More than payments: it's building permission management, metering, usage limits with cron jobs, and connecting it to upgrade, downgrade, cancellation and failed payments states. Race conditions, edge cases, and other bugs will slow you down. **2️⃣ Billing and app logic should be decoupled** Growing companies iterate on pricing often: raising prices, experimenting with credits or charging for a new feature. DB migrations, rebuilding in-app flows, internal dashboards for custom pricing and grandfathering users on old pricing is a nightmare. How it works First, create your products and plans on the dashboard. We support **any** pricing model. Some popular ones we've seen include: • **Usage & Overage** ⚡: set real-time usage limits and choose when they reset. Charge users if they go over. • **Credits** 💰: users can access monetary or arbitrary credits that many features can draw from • **Seat-based with per-seat limits** 👥:: bill customers for their users (or other entities) • **Pay upfront** 💳: let users purchase a fixed quantity of a feature upfront, which is used over time Next, all your billing logic can be implemented through just 3 functions: • : One function call for all purchase flows. We return a Stripe Checkout URL, or handle an upgrade/downgrade. • : Check whether a customer has access to a product, feature or remaining usage. • : When a customer uses a usage-based feature, record a usage event. Others **Contributing** 🤝: If you're interested in contributing, you can check out our guide here. All types of help are appreciated :) **Support** 💬: If you need any type of support, we're typically most responsive on our Discord channel, but feel free to email us too! Contributors Thanks to all our contributors for helping make autumn a better product!