Clone, npm install, supply a Stripe test key, watch a working multi-tenant billing system come to life.
The boring base layer, done right once.
The flows real customers actually hit.
Failed payments handled like adults, not panic.
Every state change traceable; reconciles to Stripe daily.
MIT-style license for the code. Use it as a starting point, lift the parts you need, or run it as-is.
TypeScript monorepo: API service, worker, admin UI, shared types, fixture data, end-to-end tests against Stripe test mode.
Migrations included. Multi-tenant by default. Partitioned audit log. Idempotency table sized for production load.
An ADR per non-obvious choice: why this retry policy, why this dunning shape, why this proration approach.
94% coverage. Integration tests run against Stripe test mode; unit tests run offline. CI configuration included.
24-page PDF for adopting the patterns into your existing codebase, even if you can’t use the code wholesale.
If something isn’t answered here, ask in your intro email — we keep this list short on purpose.
The reference is Stripe. Patterns generalize cleanly to Paddle, Lemon Squeezy, or Chargebee. We have notes on the diff for each in the migration guide.
The reference code is TypeScript. The patterns translate cleanly — we’ve included the equivalent shapes in pseudocode for Python and Go in the migration guide.
It saves 8–12 senior-engineer weeks. We could keep it private and only ship it on Custom Software engagements (where it’s included), but more teams benefit from it as a standalone artifact.
Use it inside your product, yes. Resell it as a standalone product, no — that’s the only restriction in the license.
We do bespoke kits, too. Send a paragraph about the problem and we’ll come back inside 48 hours.