Dedicated environment
A complete Authio deployment for your account alone — its own API, console, PostgreSQL and Redis — provisioned once you pay and operated from your console.
On the Dedicated plan, Authio provisions a whole environment that serves your account and nobody else: its own API, its own administration console, its own PostgreSQL database and its own Redis cache, in a project of its own at the hosting provider. Your realms, clients and users live there, not on the shared platform.
The shared console becomes the place where you follow and operate that environment: its health, resources, logs, settings and addresses. What the environment holds — realms, clients, people — is managed in the environment’s own console, at its own address.
What you get
| Service | What it does |
|---|---|
| API | Signs people in, issues and verifies tokens and serves the hosted sign-in pages. Its address is the issuer your applications trust. |
| Console | The administration console of your environment, where your team creates realms, clients and users. |
| Database | PostgreSQL, where realms, clients, users and their history are kept. |
| Cache | Redis, which keeps sessions, authorization codes and the rest of the sign-in state. |
The environment runs the same product as the shared platform, so the rest of these docs applies inside it. Plan quotas do not: inside your environment, the number of realms, clients and users is not capped by a plan.
Isolation and resources
Each environment runs in a project of its own on Railway, with its own services, data volumes, encryption key and secrets. No other customer’s traffic or data reaches it.
Every service is held to a memory ceiling, so the environment as a whole uses at most 4 GB:
| Service | Memory ceiling |
|---|---|
| API | 1.5 GB |
| Console | 1 GB |
| Database (PostgreSQL) | 1 GB |
| Cache (Redis) | 0.5 GB |
| Total | 4 GB |
The ceilings are set when the environment is provisioned. The dashboard compares what each service uses with what it may use: a service close to its ceiling slows down first and may be restarted by the hosting provider.
Where it answers
An environment answers on two addresses: one for the API and the hosted sign-in pages, one for the console. It starts on addresses the platform gives it, and you can move it to a domain of your own — auth.acme.com and console.acme.com, for example — by creating a few DNS records. See Domains and email.
Who it is for
- Teams that need their identity data and sign-in traffic kept apart from every other customer’s.
- Companies that want sign-in to run on their own domain, on infrastructure provisioned for them alone.
- Teams that want to watch and operate the servers behind sign-in themselves: read their logs, restart a service, send e-mail through their own server.
If you only need realms and clients, the shared platform covers it and starts on a free trial. Both run the same product, so you can integrate on the shared platform first.
Buying the Dedicated plan
Choose the Dedicated plan
On the pricing page, choose Subscribe now on the Dedicated plan. This plan has no free trial: the card is asked for at sign-up.
Create your account
Fill in the sign-up form. Instead of starting a trial, it takes you straight to payment once the account is created.
Pay
Enter your card on the payment page. If you leave before paying, the account waits for the payment: signing in asks you to finish it, and the payment page can e-mail you a link that picks it up where you left off.
Watch it being provisioned
As soon as the payment is confirmed, Authio starts building your environment. Sign in to the console to watch it assemble, step by step; you also get an e-mail when it is ready. See Provisioning and lifecycle.
What your console shows
Once your account is on the Dedicated plan, the shared console shows only what applies to it:
- Environment, at /environment: the dashboard, services, monitoring and configuration of your environment. This is where you land after signing in.
- Account pages: your profile and settings, the subscription and the team.
The realm, client and user screens of the shared platform are not shown: opening one takes you to your environment. Those screens live in your environment’s own console, and the shared API refuses to create realms or clients for a Dedicated account with the error code SharedTenancyNotIncluded.