Skip to content

Sign in

This page takes you from the sign-in screen to your instance on the Overview page.

Where the console runs

The TIDE console is served by the TIDE operator process: the Flutter web app, the JSON API under /api/*, the sign-in routes under /auth/*, and gRPC-web for the in-process services (Atlas, FORGE and the shared pages such as User, Billing and Integrations), all on one origin and one session. Each installation has its own console URL.

Step 1: sign in, or create an account

The sign-in page offers the methods the installation configured. GET /api/me tells the web app which to show.

MethodTurned on byNotes
GoogleGOOGLE_CLIENT_IDThe ID token is verified against the issuer’s keys. The email must be verified.
Username and passwordCONSOLE_ADMIN_PASSWORDThe user name is CONSOLE_ADMIN_USERNAME, default admin.
reCAPTCHA (optional)RECAPTCHA_SITE_KEY and its secretChecked before the credential when configured.

Who may sign in is decided by CONSOLE_ALLOWED_EMAILS (a list) or, when that is unset, CONSOLE_ALLOWED_HD (a hosted e-mail domain). With neither set, nobody may sign in with Google: the check fails closed.

If neither GOOGLE_CLIENT_ID nor CONSOLE_ADMIN_PASSWORD is set, the console runs open: the sign-in page says “Auth is not configured — console is open.”, reads work, and privileged writes are refused, because nobody could be named in the audit trail.

New to Runink? Create an account opens the sign-up page: organisation name, work e-mail, plan and seats, then the payment provider’s checkout. See Billing.

Sessions are server-side. The cookie core_console_session holds an opaque id; Log out in the rail footer revokes the session on the server. When a session ends, the sign-in page says so and returns you to where you were.

Step 2: choose an instance

After sign-in you land on Overview. Its bird’s-eye shows every instance (ClientInstance) and application control plane you may see. Drill into one to put it in focus. Admin appears in the rail footer only when the server reports that you administer the instance in focus; every access call checks the role again on the server.

Step 3: learn the rail

GroupRowsQuestion it answers
OverviewOverviewIs anything wrong, and where do I go next?
DevExClusters (Overview with the application consoles, Namespaces, Nodes & servers, Instances, Routing, Secrets & PKI, GitOps), Agent runs, Audit Chain (with Reviews)What runs, did it ship, what did the agents do and find, is the record intact?
DataExAgents (with Trust as a tab), TasksWhich agents act and under what limits, what model work is in flight, what did TIDE find?
IntelligenceIntelligence overview, Estate, CapEx, Business rules, PlaybooksWhat does the platform know about the data estate?
FORGENew chat (earlier chats are behind the Studio’s Chats button)What is being built?
FooterAdmin, Settings (User, Integrations, Billing); Log out is in the account blockWho you are, what TIDE connects to, what you pay.

Below a window width of 720 px the rail moves into a drawer. Every page can be linked with ?tab=<name>, for example /?tab=gitops. An unknown name opens Overview; a retired name opens the page that now owns its subject. See the console map.

Next steps