The SaaS starter kit that's assembled around your product
Subscription billing, sign-in and teams, API keys, feature flags, usage metering, a status page and a changelog — the months of plumbing every product needs, delivered as a complete Laravel app you own outright, and that AI keeps up to date for you.
A starter kit normally means a generic template: you download it, then spend weeks bending its assumptions to your product. This one works the other way round. Tell us how your product works — your plans and prices, how customers sign in, what each tier gets, whether customers need API access — and we assemble the kit to that spec: billing, auth, API keys, feature flags, metering, status page, changelog and customer email, configured to your product before you write your first feature. And two things make it unlike any kit you've downloaded:
You own it. The system is yours — standard Laravel code you can take anywhere, with your customer and subscription data in your database and the revenue flowing through your own Stripe, Lemon Squeezy or Paddle account. No platform fee on your income, no framework lock-in, no losing your history if you move on.
AI manages it. When something needs to change — a new plan, a different trial length, a limit you want metered — you describe it in plain English and the AI makes the change. No digging through someone else's boilerplate, no waiting on a kit maintainer's roadmap.
What's already built
Every one of these is a finished module — proven, working, and covered by its own automated test suite that proves the rules actually hold: that a lapsed subscription loses the access its plan granted, that a metered limit can't be silently exceeded, that a webhook with a bad signature is rejected. You're getting software that's been built and tested, then assembled to your product — not a boilerplate you audit line by line before you trust it.
| The job | What it does | What you tell us |
|---|---|---|
| Plans & billing | A pricing page, checkout, trials, upgrades and failed-payment handling on Stripe, Lemon Squeezy or Paddle — the money lands in your account, not a middleman's | Your plans, prices and trial — and which billing provider |
| Sign-in & accounts | Email and password, Google and GitHub sign-in, magic links, two-factor, teams and invitations — the whole front door, ready on day one | How customers should sign in, and whether accounts have teams |
| API keys & webhooks | Per-customer API keys with scopes, and signed webhooks with retries — so your customers can build on your product the way you build on others | Whether customers get API access, and what it should expose |
| Feature flags & limits | Which features each plan gets, flipped without a redeploy — upgrades unlock instantly, downgrades enforce themselves | What each plan gets and what it's capped at |
| Usage metering | Count the thing your pricing counts — requests, seats, projects — enforce the caps, and show customers their usage before they hit them | What you meter, per plan |
| Status page & changelog | A public status page with incident history, a changelog for every release, and a launch waitlist if you're pre-launch — trust signals from day one | Which of them you want live at launch |
| Customer email | Welcome emails, receipts and payment-failure notices through your own email provider, with every send logged | Your wording and your sender address |
| Audit trail | Every sign-up, payment and plan change recorded across the product — what happened, and when | Nothing extra — it works from everything else |
It already works together
These aren't eight packages stitched together with glue code you maintain. Billing, access, limits, email and audit are one system reading one database: a plan upgrade flips the customer's feature flags in the same moment the payment lands, a lapsed card takes the access its plan granted, and the usage meter enforces the caps your pricing page promises. The scaffolding agrees with itself — which is exactly the part of a SaaS that's tedious to get right and embarrassing to get wrong.
It's your system to plug into
Every module comes with two ways in: the screens, and an API. That matters twice over for a software product. Inward, your actual product — the thing only you can build — plugs into the same billing, auth and limits everything else uses: checking a customer's plan or recording usage is one call, not a subsystem you write. Outward, your customers get the same courtesy — scoped API keys and signed webhooks so they can build on your product the way you build on others.
That's why it's built this way. A kit that's only screens is a walled box the day your product needs to ask it a question. Because every module is driven through its API, your product, your integrations and your future tools all plug into the same system you already own — no rebuild required.
Tell us how your product works
Tell us how your product works using this form and we assemble your system, run the tests, and hand it over as a complete, working Laravel application you own — yours to download, host anywhere, and change forever.