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.
124
signups chart below
317
+9 this week
$18,940
412 subscriptions
added by Billing
62%
18 campaigns
added by Notifications
- 09:41sarah@acme.io moved to PremierBilling
- 09:12Northwind created an organization
pack installed
Billing and Notifications
brought two widgets to this board
example data
A command center, included with auth.
You do not install an admin panel. You install auth and this is already there. Real captures from the Aether template: the dashboard, the users table, and billing. Whoever is on support that day can resolve the ticket without pulling an engineer off their work.
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.
The CLI writes those files, and shows the plan first. See how compose installs a pack.
What it does, and where to check.
Plain answers on the left, the file or route that proves each one on the right. Nothing here rests on a promise.
Separate admin application with its own login
apps/adminFind any customer account in seconds
/users/:userIdEvery pack you install adds new admin tools automatically
+4 from billingYour team manages users without touching the database
withSuperAdminSend customer campaigns yourself, without an engineer
/notificationsSee revenue and subscriptions without logging into Stripe
BillingRevenueRow
What it saves you.
Fewer tickets escalated to engineering, no per-seat admin tool on the bill, and problems fixed before customers write in.
Answer support yourself
Look up the account, fix the plan, resend the invite.
Revenue always in view
MRR and subscriptions on your dashboard, not in Stripe.
Catch problems before churn
Failed payments surface here before the customer writes in.
New tools with every pack
Billing alone adds four admin screens, already registered.
A second app you own
No hosted admin tool, no per-seat pricing, ever.
Nobody needs the database
Role-based access instead of raw SQL on production.
0
ticketengineeringyouEngineers pulled off work per support ticket
Look up the account, fix the plan, resend the invite. Yourself.
+4
day one+ billing packAdmin screens arrive with the billing pack alone
Every pack ships its own admin tools, already registered.
$0
hosted admin toolgrows per seatyour admin app$0 flatPer-seat bill for your internal tools
It is your app in your repo, not a hosted subscription.
One retheme covers the product and the panel. See how theming works.
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.
Billing
Stripe checkout, subscriptions, and customer portal, webhooks included. You can charge money the day you launch.
Emails & notifications
Realtime in-app inbox, email via Resend, admin broadcasts. Reach every user without building a messaging layer first.
Admin panel
A second app just for you: inspect users, manage orgs, watch revenue. The tool every product needs and nobody has time to build.
Organizations and invitations
Teams, roles, and email invites that just work. Sell to companies without a month of multi-tenant plumbing.
Roles and permissions
Roles, actions, and subjects checked on the API and in the UI. Nav links and routes hide themselves when a member is not allowed in.
Every feature extends the admin
Add billing and MRR, active subscriptions, and per-organization revenue land on the admin dashboard. Features ship their admin side too.
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.
Questions, answered
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