Billing
- Stripe checkout
- Subscriptions
- Payment webhooks
Ships with every SaaS starterA second app.
A second app.
Not a settings tab.
Your customers get the product. You get a second app with its own login, and every pack you install adds to it.
users
124
organizations
317
mrr+12%
$18,940
the second app
A command center, included with auth.
Its own login
Lives at admin.my-app.com with separate sessions, away from customer traffic.
Zero setup
Install the SaaS starter and this app is already in the repo, deployed with the rest.
admin.my-app.comsuper admin
users
124
organizations
317
mrr · added by billing
$18,940
Support without engineers
Users, licenses and billing actions: whoever is on support resolves the ticket here.
Grows with each pack
Stripe adds revenue widgets, notifications adds read rates. No admin work per feature.
2ndapplicationnot a settings tab
0setuparrives with auth
+2widgets per packthe board grows itself
The command center
A command center, included with auth.
You do not install an admin panel. You install auth and this is already in the repo. Real captures from the Aether template.
Dashboardadmin.my-app.com
Usersadmin.my-app.com/users
Billingadmin.my-app.com
its own login, its own deploy
Install a pack, get new powers
Install billing. The dashboard changes.
A pack ships admin files and the codemods register them. Both screens below arrived with a pack. Nobody on your team built them, and nobody paid for the build days they would have cost.
localhost:4100Billing
localhost:4100/notificationsNotifications
The CLI writes those files, and shows the plan first. See how compose installs a pack.
What you get
What your team gets.
Six outcomes, each with a receipt. Nothing here rests on a promise.
A real back office
Its own app, its own sign-in, deployed on its own.
apps/adminAny customer in seconds
Search by email: plan, sessions and history on one screen.
One screenplan · sessions · historyGrows with every pack
Install billing and four new admin screens arrive with it.
Support without engineers
Resets and plan changes are buttons, every action logged.
Every actionaudit-loggedCampaigns without tickets
Pick a segment, write the message, send it.
/notifications
Revenue at a glance
Subscriptions, MRR and failed payments on your own dashboard.
The payoff
What it saves you.
Fewer tickets escalated to engineering, no per-seat admin tool on the bill, and problems fixed before customers write in.
no eng time
Answer support yourself
Look up the account, fix the plan, resend the invite.
one glance
Revenue always in view
MRR and subscriptions on your dashboard, not in Stripe.
kept accounts
Catch problems before churn
Failed payments surface here before the customer writes in.
0 build days
New tools with every pack
Billing alone adds four admin screens, already registered.
$0 per seat
A second app you own
No hosted admin tool, no per-seat pricing, ever.
risk gone
Nobody needs the database
Role-based access instead of raw SQL on production.
0
Engineers pulled off work per support ticket
Look up the account, fix the plan, resend the invite. Yourself.
ticketengineeringyou+4
Admin screens arrive with the billing pack alone
Every pack ships its own admin tools, already registered.
day one+ billing pack$0
Per-seat bill for your internal tools
It is your app in your repo, not a hosted subscription.
hosted admin toolgrows per seatyour admin app$0 flat
One retheme covers the product and the panel. See how theming works.
Your customers get the product.
You get the controls.
my-app.comadmin.my-app.com
Feature by feature
What runs through the panel.
The features behind the screens above. Each one ships its admin side into the same app, wired to the same typed API as the product.
Emails & notifications
- Live notification inbox
- Emails via Resend
- Admin broadcasts
Admin panel
- Manage users
- Manage organizations
- Track revenue
Organizations
- Team workspaces
- Email invitations
- Member roles
Roles & permissions
- Role-based access
- API permission checks
- Permission-aware navigation
Admin integrations
- MRR dashboard
- Active subscriptions
- Revenue by organization
Typed permissions
- Typed actions & subjects
- Compile-time checks
- API access control
Shared enums
- One shared enum package
- Frontend, backend & admin
- Update values in one place
Feature packs to grow with
Every pack ships real source code: frontend, backend, and admin surfaces where the feature needs them. Add them when you need them, one command each.
FeatureBilling (Polar)Polar integration, subscriptions, billing flows, and an admin revenue widget.Polar checkout & portalMerchant of recordFeatureAI ChatStreaming conversations, voice, and image generation with reusable, feature-owned tools.Streaming conversationsVoice and imagesFeatureBilling (Lemon Squeezy)Lemon Squeezy integration, subscriptions, billing flows, and an admin revenue widget.Lemon Squeezy checkout & portalMerchant of recordFeatureWhiteboardA collaborative whiteboard: sticky notes, freehand ink, shapes, images, and layers on one infinite canvas, synced live.Infinite canvasLive multiplayer
Questions, answered
Yes. Everything lands as plain source in your repository: frontend, backend, admin, database schema. There is no runtime dependency on us and nothing phones home.
Stop running your company from a SQL client.
It comes with either SaaS starter, so there is nothing extra to buy.
included with either starter