Thoughts on billing infrastructure, usage-based pricing, and building for AI startups.
How we migrated our core database to PlanetScale, and why it's been a game-changer for performance, reliability, and developer experience.
Post-mortem write up of an outage that affected a number of requests between 15:00 and 16:00 UTC, 15th March 2026.
We worked with Theo and Mark from T3 Chat to build a cool new way of pricing. We learned about the psychology behind how AI products are consumed, and what that means for how we should monetize them.
A bit of context about what will be changing in the new version of the Autumn API and SDK.
Replit’s 2026 pricing shift highlights three trends in AI-first products: usage-based billing creates anxiety, seats don’t map to AI value, and credits/effort-based pricing reduce transparency as agents run longer.
Learnings about building a component library for a billing platform for AI companies
A little write up on our thoughts and exploration around how to market our developer tool for billing and payments.
Handling stripes upgrades, downgrades, schedules, one off and subscriptions all in 1 endpoint.
Stripe has been the go-to for billing, subscriptions and managing payment logic for 16 years. We think that'll change soon.
We decided to use a shadcn/ui registry to set up our pricing components, instead of a Reactjs library. We used this approach for pricing pages, upgrade and downgrade flows and paywalls.
We wanted to make payments, billing, usage limits and tracking as easy as possible. We explored a billing integration that required no backend setup, but ultimately gave up.
How we generated our first revenue as a startup, and got into Y Combinator.