CHECKING
Control plane API
Checking.
Requesting /health from the local backend.
↗GET /health— ms
INFRASTRUCTURE CONTROL CENTER
Command overview.
A clear view of your control plane, its dependencies, and the next step to bring your VPS fleet online.
Awaiting first check
YOUR INFRASTRUCTURE, ONE CONSOLE
Own the signal.
Operate with clarity.
The dashboard is connected to the API foundation. The next milestone is enrolling monitoring agents so real node health and resource telemetry can flow in.
NO DEMO TELEMETRY/LIVE API CHECKS/SELF-HOSTED
NX/01
Control plane status
Live checks against the backend running on this VPS.
CHECKING
PostgreSQL readiness
Checking.
Readiness endpoint checks database connectivity.
↗GET /ready— ms
NOT SET
VPS enrollment
Not ready.
The current API has no node registration endpoint yet.
↗Agent registryPENDING
NO SOURCE
Node telemetry
Awaiting.
CPU, memory, disk, and network require an enrolled agent.
↗Metrics ingestionPENDING
INFRASTRUCTURE
Server fleet
Registered nodes and their latest reported state.
No nodes enrolled yet
This is an empty fleet, not sample data. The server registry and agent enrollment API are the next backend milestone.
Resource metrics will appear here after real agents are connected.
DEPENDENCIES
Service diagnostics
Requests made by this browser through the web proxy.
API processGET /health
CHECKINGDatabase connectionGET /ready · PostgreSQL ping
CHECKINGAPI versionGET /api/v1/meta
CHECKINGWhat this means
API and database readiness are checked live. Fleet, alerts, and resource usage remain unavailable until their backend services exist.
INFRASTRUCTURE
Server fleet.
A single inventory for VPS instances managed by NEXUS FIELD OPS.
REGISTERED NODES—Registry endpoint not implemented
ONLINE—No agent heartbeat data
RESOURCE TELEMETRY—No metric samples received
NODE INVENTORY
Managed servers
Real server records will populate once enrollment is implemented.
| SERVER | LOCATION | STATUS | CPU | MEMORY | LAST HEARTBEAT |
|---|---|---|---|---|---|
Inventory is not connected The current API exposes health, readiness, and version metadata only. It does not yet store server records. | |||||
No mock rows are being shown. Once node registration and heartbeat APIs are added, this page can display live status instead of placeholder metrics.
ONBOARDING
Agent setup.
The path for attaching additional VPS instances to this control plane.
ENROLLMENT READINESS
One control plane.
Many independent nodes.
Additional VPSs should connect outbound using a short-lived enrollment token. The agent should never require publicly exposing its own management port.
ENROLLMENT API NOT IMPLEMENTEDRequired backend milestones
These are prerequisites, not features that are already running.
Secure enrollment
Create node records and one-time enrollment tokens. Store only token hashes and expire unused tokens.
NOT IMPLEMENTEDAgent heartbeat and telemetry
Authenticate agent reports and persist CPU, memory, filesystem, network, uptime, and last-seen timestamps.
NOT IMPLEMENTEDNode identity and audit
Rotate node credentials, authorize every node-specific action, and log sensitive operations for review.
NOT IMPLEMENTEDOne-command installer
Publish a versioned installer only after the API can issue enrollment credentials and verify the installed agent.
BLOCKED BY 01–03Security boundary: Do not run a public installer that accepts arbitrary commands or embeds a shared admin secret. Enrollment needs expiring credentials and server-side authorization first.
OBSERVABILITY
Session activity.
Recent checks and interactions captured during this browser session.
This is a temporary browser-session log, not a backend audit trail. Persistent operator audit events are not implemented in the API yet.
LOCAL SESSION
Recent events
Newest events appear first. Nothing is uploaded or persisted.
No session events yet
Run a health check or navigate around the dashboard to record local events.
PREFERENCES
Console settings.
Configure browser-side polling and inspect where this UI routes its API requests.
CONNECTION
Control plane endpoint
The frontend talks to a same-origin proxy; backend traffic stays on the VPS loopback interface.
Web consoleCurrent browser origin
Loading…API routeProxied by the Node web server
/api/v1/metaSAME ORIGINBackend targetConfigured server-side; not exposed to the browser
127.0.0.1:8080PRIVATEHealth check intervalHow often this tab checks API and database readiness
BUILD INFORMATION
PRODUCTNEXUS FIELD OPS
FRONTENDNode.js · Static UI
BACKENDChecking…
API STAGEChecking…
Authentication, node management, command execution, alerting, and persistent audit logs must be implemented and reviewed before this console is used for remote server operations.