Your login page.
A hosted sign-in on your domain — email, Google, Apple — for every app you ship, wired by the AI that built the app. Users are counted and never billed. The bill doesn't move when your app starts working.
$15 a month, and it isn't just this app — every Parsons product is on the same subscription. Cancel any time. Monthly active users are metered and never billed, at every size — because auth isn't what we sell.
A login on your domain, from one sentence.
Make a project.
One per app or client. It gets a hosted login page, a key, and the providers you turn on.
Set up login for the bakery site — email and Google.Paste one link into your AI.
Your account comes with one private address. Paste it into Claude, ChatGPT or Cursor once, and Auth's tools are there. No AI of your own? The console has chat built in.
https://mcp-hub.parsons.ai/p/prof_••••••••/mcpPut it on your domain.
login.sunrisebakery.com, styled with your name and mark. Email magic links, Google, Apple. Your app gets a session it can trust.
Put the login on login.sunrisebakery.com with the bakery logo.set_domainlogin.sunrisebakery.comDNS readyenable_providergoogleonset_brandingname, mark, colourdoneWatch who signs in.
Users, sign-ins, failed attempts, new devices. Rotate a key with a 24-hour overlap — but only with a person present.
Rotate the production key for invoice-lens.One login, every app, no per-user bill.
The providers people expect
Email magic links, Google and Apple sign-in, on by a switch. Enterprise SSO when you need it, not as a tier.
On your domain, in your name
Hosted, but yours: your subdomain, your mark, your colour. Users never see ours.
Users counted, not charged
MAU is a number on the console, at every size. Every other auth vendor's bill goes up when your app works. Ours can't.
Keys with a rotation you can trust
Per project, per environment. Rotation with a 24-hour overlap — and a person in the loop for production.
Activity you can ask about
Sign-ins, failures, new devices — answered from the log, not a chart you have to read.
Rate limits, published
"Rate-limited" is a phrase. These are the numbers — unrounded, on the details page in full — so you can check them against your traffic before you integrate.
It signs your users in. It cannot bill you for them.
- ×Charge per monthly active userMAU is metered for visibility and never billed, at any size.
- ×Rotate a production key without a personrotate_project_key hands you a session-gated link. A human clicks it.
- ×See another project's usersUsers belong to the project. Two apps' user tables never meet.
- ✓Create projects, enable providers, brand the login, set the domain
- ✓Read users, sessions, sign-ins and failures
- ✓Issue and rotate keys, with an overlap
There is no security slogan on this page and no badge we haven't earned. Everything in that list is a thing you can check; the full mechanism and every tool are on the details page.
Fifteen dollars a month — and it isn't just this app.
Is it worth it? Start where we look worst.
Every auth vendor has a generous free tier, and for a side project you should use one. Here's what the first paid tiers publish.
Ours is $15 with no MAU line at all — and it's also the host, the database and the domain the app needs. The lines above are fine until your app works; then they move. And there is no free tier because the free tier is where the per-user bill is hiding.