Operations and monitoring

Read your environment’s health, resources, usage and logs, act on its services, change its variables and sign in as its first administrator.

Everything about the running environment is on Environment, in four views: Dashboard, Services, Monitoring and Configuration. The address keeps the view you are on, so a link to it opens the same view, and Environment guide at the top of the page explains each part on screen.

Health, resources, logs and variables are read live from the hosting provider and from the environment itself on every visit, never from a stored copy.

Who can do what

Who	What they can do
Owner or administrator of the account	Everything on the page: restart the environment, act on its services, save variables, change the domain, recreate or remove the environment, and reveal the first-access credentials once.
Team members who can read the account	Read the page: health, services, resources, usage, logs, variables and domain.
Platform operator	Every action on any environment, even before it is ready, including resuming a failed provisioning. Never the first-access credentials.

An owner can operate the environment only while it is Ready. Every change made here is written to the account’s audit trail with who made it; the values sent, such as variables, are not recorded. See Audit and insights.

Dashboard

The dashboard sums the environment up in tiles, and each tile opens the view that details it.

Tile	What it shows
Environment	Its name and version, the console and API addresses, the user name to sign in with, the administrator’s e-mail, and when it was created and became ready.
Health	The overall reading, refreshed every 30 seconds from the API’s own health check, with the status code it answered and how long it took.
Services running	How many of the four services are running.
API errors	The errors among the latest 100 lines the API logged. Opens the logs narrowed to errors.
First access	Reveals the first administrator’s credentials, once. See First administrator.
CPU and memory	What the services use now against what they may use. The dials turn to a warning from 80% and to critical from 95%.
Network and disk	Traffic in and out over the chosen period, and the disk the database and the cache use.
Each service	Where its latest deployment stands, its CPU and memory, and when it was deployed. Opens in the side panel with its actions.
Usage	Realms, clients, users, people who signed in, sign-ins and their success rate over the last 7 days.

Health

Reading	What it means
Healthy	Every service is deployed and the API answers its health check.
Degraded	The API answers, but a service is not in a running deployment.
Unavailable	The API does not answer, or its deployment failed.
Unknown	The environment is not running yet, so there is nothing to measure.

Services and deployments

Services lists the API, the console, the database and the cache, each with its latest deployments and their status. Every action asks for confirmation first and says what will happen.

Action	What it does
Restart	Restarts the running deployment with the same build, data and settings. The service stops answering for a moment. Try it first when a service misbehaves.
Redeploy	Makes a new deployment from the current image and settings, which takes over once it is up, within a few minutes. On a stopped service it reads Start.
Stop	Stops the running deployment until the service is started again. Its data and settings are kept.
Cancel deploy	Offered only while a deployment is still building or rolling out. The deployment that ran before it, if any, keeps answering.

Stopping the API or the database makes every sign-in fail while it is stopped, and stopping the cache may too. Stopping the console only keeps your team out of it; sign-ins keep working.

Restart environment, at the top of the page, redeploys the API and the console together, with the same data and settings.

Monitoring

Resources

CPU, memory, network in and out, and disk for each service, as the hosting provider measures them. Pick the last hour (a reading a minute), 24 hours (a reading every 15 minutes) or 7 days (a reading an hour).

Usage

Usage is counted by the environment itself, over 7 or 30 days: realms, clients and users as they stand now, sign-ins with their success rate and the number of people who signed in, sign-ins per day (UTC), and the realms and grant types used most. When it cannot be read, the page says why instead of showing zeros:

Message	Why
Usage is not available yet	The environment is not ready.
Usage reporting starts after the next update	The environment was created before usage reporting existed.
Your environment did not answer	The environment did not answer this time. Try again in a moment.
Your environment runs a version without usage reporting	The version it runs does not report its usage.

Logs

Pick the service and how many of its latest lines to read — 50, 100, 250 or 500, newest first — then narrow them by text, by period or by severity. The lines come from the service’s latest deployment. A line opens whole in the side panel, where it can be copied.

Configuration variables

Configuration → Variables holds the settings that are yours to change. Everything else — connection strings, keys, addresses — is managed by the platform, and a request to change it is refused with DedicatedVariableNotEditable.

Group	Variables	What they set
E-mail	`EMAIL_FROM_NAME`, `EMAIL_FROM_ADDRESS`	The name and address e-mails are sent from.
E-mail	`EMAIL_SMTP_HOST`, `EMAIL_SMTP_PORT`, `EMAIL_SMTP_USERNAME`, `EMAIL_SMTP_PASSWORD`, `EMAIL_SMTP_ENABLESSL`	Your own SMTP server.
E-mail	`EMAIL_MAILERSEND_APIKEY`	A MailerSend key. While it is set, e-mail goes through MailerSend instead of SMTP.
Messaging	`SERVICEBUS_CONNECTION_STRING`	An Azure Service Bus namespace for background work. Optional: without it, the API delivers e-mails and events itself.
Push notifications	`FIREBASE_SERVICE_ACCOUNT`	The Firebase service account JSON push approvals are sent with. Without it, push approvals fail; the other sign-in steps work.
AI advisor	`ANTHROPIC_API_KEY`	The key the AI advisor calls Claude with. Without it, the advisor reports itself unavailable.

Variables are saved together with Save and redeploy, which redeploys the API — every variable above is set on it — within a few minutes. Save when a short interruption is acceptable.
A secret — the SMTP password and every key above — only says whether it is set; its value is never shown again. Typing a value replaces it, leaving the field blank keeps it, and Remove clears it when you save.
Variables can be changed only while the environment is ready.

Moving e-mail to your own server is covered step by step in Sending from your own e-mail.

First administrator

Your environment’s console has no public sign-up. It starts with one administrator, created when the environment is first deployed, who creates the realms, clients and users and invites the rest of the team.

Reveal the credentials
Once the environment is ready, choose Reveal credentials on the First access tile of the dashboard. Only an owner or administrator of the account can do it, on their own environment.
Copy the password
The user name, the e-mail and the password are shown once. Leaving the page hides the password for good: Authio no longer keeps it, for you or anybody else on the account.
Sign in by user name
Open the console address and sign in with the user name — admin, unless the platform chose another — not with the e-mail. The e-mail is the account owner’s address, where password resets go.
Change the password
In your environment’s console, open realm authio → Users, edit your user and set a new password.

Lost the password after it was shown? Use password recovery on your environment’s sign-in page; the link goes to the administrator’s e-mail. Administrators of the authio realm also renew their password through an e-mailed link when it expires, at most every 90 days, so keep the environment able to send e-mail.

Next steps

Domains and emailMove the environment to your own domain and send e-mail through your own server.Provisioning and lifecycleFailures and retries, recreation, removal and suspension.Audit and insightsThe trail of every change made to your account.Error codesWhat each code the API answers with means, the Dedicated ones included.