Stripe
Fintech
← Websites
Autumn
Managed billing infrastructure for AI startups and usage-based pricing
Visit site ↗
10.1MB · 8,359px tall · uses Geist, Geist Mono
Industry
Devtools, Fintech
Style
Dark Mode, Gradient, Typographic
Stage
Seed
Built with
Next.js
About the site
Autumn is a drop-in billing layer for AI and usage-based companies, sitting between an app and Stripe to handle entitlements, credits, usage limits, and custom contracts. The landing page is dark and technical: a black canvas divided by thin grid lines, monospace navigation, and a grey-and-white headline beside a code editor floating on a vivid purple-to-magenta gradient. A great reference for developer-first fintech and API products that want to feel engineered and a little bold.
How this page sells
For engineers at AI startups who regret hand-rolled billing: code first, then their own mess, then Autumn as the one record beside Stripe.
Primary navigation
- Docs
- Blog
- Pricing
- Discord
- Dashboard
ClickTap a section to see it on the page
'The managed billing service for scaling companies' with only the key words in white, beside a code editor on a purple-magenta gradient showing the real check() and track() calls and an 'Add Autumn to my app' prompt.
Why it converts: Engineers trust code over copy. Seeing the whole integration in a few lines tells them how small the change is before they've read a single feature.
'Powering millions of customers for the best startups' over Mintlify, Firecrawl, Poke, Mastra, Browser Use and T3.chat.
Why it converts: These are AI startups the reader follows on X. Peers at their own stage billing through Autumn is more persuasive than an enterprise logo they can't relate to.
A full-bleed green card from Mintlify's Kyle Finken, 'I would literally recommend Autumn to every person who asked', with a case-study button and more cards peeking in from either side.
Why it converts: The quote names the real fear, customers not getting what they paid for, and the half-hidden cards say there's more proof one swipe away.
'Say goodbye to your vibecoded infra.' over floating artefacts of homemade billing: '12+ custom webhook handlers', a GitHub issue about a webhook race condition, a ticket asking about rollover.
Why it converts: Every artefact is something already sitting in the reader's backlog. Recognising their own mess on someone else's page is what makes them want the fix.
A diagram placing Autumn between 'Your application' and Stripe, listing what it takes over (subscription state, credit balances, entitlements, webhooks, proration) with 'three API calls handle everything else'.
Why it converts: It answers 'where does this sit, and what do I stop maintaining?' in one picture, which is the architecture question an engineer must clear before a trial.
'Any pricing model. Seriously.' beside tabs for eight models (credits, trials, seats, usage, hybrid, rollovers, custom enterprise) and a working rollover-policy form.
Why it converts: Pricing changes are why teams outgrow their billing. Showing the actual config removes the fear of being boxed in when pricing changes next quarter.
'Everything you need for AI and usage billing' as nine cards: real-time balances, grandfathered pricing changes, custom contracts, auto top-ups, spend limits, coupons and more.
Why it converts: It's a checklist the reader runs against their roadmap. Each ticked card is one fewer reason to keep building billing in-house.
Four bright stat chips (5 billion+ monthly events, under 50ms latency, a 10-minute support SLA, zero churn) next to 'open source core, self-host ready'.
Why it converts: Billing sits on the critical path of every request. Volume, latency and a self-host exit answer 'what if you go down?' before an engineer has to ask.
The questions that block a switch, asked plainly: Do I still need Stripe? What if Autumn goes down? How is it different from Orb or Metronome? Am I locked in?
Why it converts: Naming competitors and lock-in head-on reads as confidence, and it hands the engineer ready answers for their CTO before the demo.
