Your users' roles, plan and payment status travel in the same token, so one guard in your API checks them all, offline. Built for your first paying customers, and priced for them.
Auth here, payments there, feature flags somewhere else, held together by webhooks you have to keep in step.
Every request asks three services who the user is, what they paid for and what they may see.
Prices that punish growth, and basics like MFA policies kept for the enterprise tier.
Plans, checkout, proration, dunning, invoices and EU VAT on your own payment account, the plan in the token. Sold separately, later: talk to us.
Target by plan, org, role or country, roll out by percentage, switch off in one click. Evaluated offline.
Permission, plan and flag in one line, with a 402 your app turns into an upgrade.
Talk to your users with their plan, roles and flags beside each conversation. Your own AI agent can answer first.
When a user signs in, their token carries who they are, their organisation and role, their plan and payment status, and what your flags target. Your API checks it in one guard, offline, and your UI reads the same answers.
sub · amrorg.rolebilling.planflag()A plan change reaches the token at its next refresh. The same definitions shape your UI.
import { createAuth } from '@anchring/auth/server';
import { access } from './access'; // your roles, shared with the browser
const auth = createAuth({ project: 'acme', env: 'prod', audience: 'acme-api', access });
app.use('/api/*', auth.middleware()); // offline: no call to us per request
// Role, plan and flag in one check. Not on the plan: 402 plan_required, offer the upgrade
app.get('/api/reports/export',
auth.require('report:export', { plan: ['pro', 'team'], flag: 'bulk-export' }),
(c) => c.json(exportReports(c.var.user.org?.id)));Prices in euros, excluding VAT. Test environments include every feature on every plan.
a month, or €290 a year (two months free)
monthly active users, then €3 per 1,000 more
sign-in apps; APIs and backend services are free
custom domain
You do. You connect your own payment account and are the merchant; Anchr.ing runs plans, invoices and VAT around it and never holds your money.
Your users keep signing in. Extra monthly active users are billed per thousand, and you move up when you need projects or enterprise SSO.
Yes. Build on the free plan, where everything works in test, and upgrade the day you launch.
Start on the free plan and switch to Startup in Billing when your first customers arrive.
The Free plan
The Team plan
The Team plan
The Scale plan
The Enterprise plan
The Sovereign plan
Every plan side by side, and the questions people ask before paying.