Overall health
—
Core, credential storage, and node readiness.
Dashboard
Overall health of your core and connected nodes.
Sign in to core
Use your local account to access this platform.
Administrator token access
Use the deployment token for recovery or initial setup.
Core service
—
The central API and configuration service.
Credential storage
—
Secure credential storage availability.
Node overview
—Registered
—Running
—Configured
—Healthy
Instance
Client
—License UUID
—A healthy node must be running and have one available default credential. Expand a node to manage its credential sets.
| Node / endpoint | Running | Configured | Health | Credentials |
|---|
◇
No nodes registered
Add your first node when it is ready to connect.
Local Authentication
Manage the local accounts that can sign in to this core. Administrators can configure the platform; viewers can read its configuration and status.
Local users
Change your password
Network configuration
Your current connection and saved routing settings.
Loading network configuration…
Keep the original HTTP core port private. Forward only TCP 80 and 443 to the routing container. Public routing requires administrator sign-in; saved lab access is disabled when local authentication or routing is enabled.
Loading live system inventory…
Containers
System services and their current Docker state.
| Container / service | Image | State | Docker health | Started |
|---|
No system containers found.
Volumes
Actual volumes and bind mounts attached to system containers.
| Volume / source | Type | Container | Mount path | Access |
|---|
No attached volumes or bind mounts found.
Consolidated credentials
Retained revisions stay available until you approve disposal. Review the impact, snooze a reminder, or keep a revision. Provider authorization is never revoked by routine cleanup.