Enable this installation
Nobody has taken ownership of this deployment yet, so it will not hand out names, shares or agents. The controller printed an installation token when it first started. Enter it to become an administrator and enable the platform.
It works once. Whoever presents it becomes the first administrator and can then promote colleagues from the Platform section.
Get started
Overview
Getting started
Names and shares
A reservation is a name you hold. A share publishes something local under one — on the internet, or privately to people you name.
Reservations
Shares
Create a share
A private share gets no DNS record, no certificate, and no public port. Nothing on the internet can reach it; it exists for the platform's own access path.
Each share keeps its own, so two shares can serve two apps on two ports from one agent. It must be a loopback address, and an agent started with --upstream uses that instead.
Private access
Private services have no public address at all. Access is granted to named people, groups, or a whole domain — default deny, and a revocation cuts connections that are already open.
Private services
Groups
Activity
Live access sessions
Access history
Agents and tokens
An agent is a machine holding a tunnel out to the platform. An API token is for a script or a CI job. Both are credentials — each is shown once, and revoking one takes effect immediately.
Agents
To add a machine, run argus-agent enroll --label "$(hostname)" on it with an API token from below. It gets its own credential and stores it there — nothing to copy across.
API tokens
Platform
Every account, name, share and agent on this deployment — not just yours. Machine accounts belong here too: they are identities the organisation owns, for connectors that must outlive whoever set them up.
Machine accounts
A machine account owns reservations and shares the way a person does, but offboarding a person never touches it. Its agent tokens are issued here and shown once; issue a new one to rotate, then revoke the old agent.