Skip to content
For agencies

One sign-in setup, reused for every client.

Give each client their own project with its own users, domain and branding, and run them all from one account.

Start freeSee pricing
The problem

Every client project starts with auth again

Each build re-implements sign-in, password resets and roles, and each one is yours to maintain.

Clients want their own brand on the sign-in page, and their users kept apart from everyone else's.

An account per client means separate bills, logins and settings to keep straight.

How Anchr.ing helps

A project per client, one account for you

A project per client

Its own users, keys and apps, and a test and a production environment. Nothing is shared between clients.

White-label sign-in

The client's logo, colours and domain on the sign-in page, without an Anchr.ing badge.

Your team and theirs

Invite colleagues and clients to the dashboard. Members work in test; production opens only when you allow it.

Faster builds with AI

Your coding agent sets up the integration with the MCP server and rule files, with the same SDK in every stack.

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 howsub · amr
Rolesthe organisation and what it allowsorg.role
Billingthe plan and its payment statusbilling.plan
Flagswhat is switched on for this userflag()
In your code

One template, every client

Each client gets its own issuer, keys and users. Your code stays the same.

Read the guide
web/auth.ts
// One codebase for every client: each deploy sets its own project
import { createAuth } from '@anchring/auth/browser';

export const auth = createAuth({
  project: import.meta.env.VITE_AUTH_PROJECT,   // 'northwind', 'contoso', …
  env: import.meta.env.VITE_AUTH_ENV,           // 'test' or 'prod'
  clientId: import.meta.env.VITE_AUTH_CLIENT_ID,
  issuer: import.meta.env.VITE_AUTH_ISSUER,     // the client's domain: https://login.northwind.example
});
The plan

Team in numbers

Prices in euros, excluding VAT. Test environments include every feature on every plan.

Compare all plans
€99

a month, or €990 a year (two months free)

3

projects, each with test and production

15

sign-in apps; APIs and backend services are free

3

custom domains

Questions

Before you start

How many clients can we run?

Each client is a project. Team and Scale include several (the numbers are below), and Enterprise as many as you need.

Can our clients use the dashboard?

Yes, invite them as members. They work in test, and production opens to them only when you allow it.

Are our clients' users kept apart?

Yes. Each client project has its own namespace and databases, and our server reaches each one only through that project's own database user, so one client's users can never turn up in another's.

Do the client's users see Anchr.ing?

Not on a paid plan: the sign-in page carries the client's brand, on the client's domain, without the badge.

Set up your first client in test

Start free, and move to Team when the second client comes along.

Create your free accountGetting started
Free to start. No card needed.
Who it's for

For developers

The Free plan

For startups

The Startup plan

For B2B SaaS

The Team plan

For scale-ups

The Scale 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.