For scale-ups
Built for the traffic you're about to have.
Your API checks tokens offline with cached keys, so sign-in never sits in your request path. Less per user as you grow, more projects and domains, and support that answers within hours.
The problem
Growth breaks the auth you started with
An API that asks the identity provider on every request gets its latency and its outages too.
Per-user prices that climb faster than your revenue.
When something breaks at peak, a ticket queue with a three-day reply isn't support.
How Anchr.ing helps
Volume without the drama
No call per request
Tokens are verified in your API with cached keys. A slow sign-in service never slows your API.
Cheaper as you grow
More monthly active users included, and each extra thousand costs less than on the plans below.
Ship safely at volume
Percentage and organisation-wide rollouts with a kill switch, evaluated offline from the token.
Fast answers
A quick first reply in business hours, from the people who build Anchr.ing.
One token
Every check reads the same token
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.
Identitywho signed in, and how
sub · amrRolesthe organisation and what it allows
org.roleBillingthe plan and its payment status
billing.planFlagswhat is switched on for this user
flag()In your code
Zero calls per request
Flag rules are cached like the signing keys; a change in the dashboard reaches every instance within about 30 seconds.
import { createAuth } from '@anchring/auth/server';
import { flags } from './flags';
const auth = createAuth({ project: 'acme', env: 'prod', audience: 'acme-api', flags });
app.use('/api/*', auth.middleware()); // cached keys: no call to us per request
// The new checkout for the rollout percentage set in the dashboard; one click switches it off
app.post('/api/checkout', auth.guard({ flag: 'new-checkout' }), newCheckout);The plan
Scale in numbers
Prices in euros, excluding VAT. Test environments include every feature on every plan.
a month, or €2,990 a year (two months free)
monthly active users, then €1.50 per 1,000 more
projects, each with test and production
custom domains
to support's first reply, in business hours
Questions
Before you start
What happens if Anchr.ing is down?
Signed-in users keep working: your API verifies tokens with cached keys, and an expired cache keeps serving while it refreshes. New sign-ins wait until it's back.
What does going over cost?
Nobody is locked out. Monthly active users past what the plan includes are billed per thousand, at the lowest self-serve rate.
How do we move our users over?
Import them from Auth0, Clerk, Firebase, Supabase, Amazon Cognito or Keycloak. Passwords carry over where the provider exports the hashes; where it doesn't, you email every user a link to set a new one, from the dashboard.
Move your volume to Anchr.ing
Import your users, try everything in test, and switch over when you're ready.
Free to start. No card needed.
Who it's for
Anchr.ing at every stage
For developers
The Free plan
For startups
The Startup plan
For B2B SaaS
The Team plan
For agencies
The Team plan
For enterprise
The Enterprise plan
Sovereign and public sector
The Sovereign plan
Compare all plans
Every plan side by side, and the questions people ask before paying.