Architecture
How Connect works.
A layered architecture where the dashboard orchestrates the Agent, and the Agent manages the Linux system.
- ⌜
Connect Dashboard
Browser-based control plane.
- ⇄
Connection Layer
Secure session transport with retries and backpressure.
- ⚙
Anoneurx Connect Agent
Persistent, identity-bound runtime on the server.
- ⊞
Linux System
Terminal, files, processes, services, logs and network.
Agent
Runs on the user's server. It is the bridge between the dashboard and the Linux system.
Identity
The Agent has a persistent cryptographic server identity that is verified before any management session is allowed.
Authentication
Only authenticated clients can establish management sessions. No session is created without proof of identity.
Authorization
Operations are checked against the session's capabilities. The Agent refuses actions outside its granted scope.
Operations
Terminal, files, services, processes, logs and system information are all exposed through the Agent connection.
Audit
Administrative actions can be tracked and attributed, providing a verifiable record of server activity.
Example architecture diagram
┌─────────────────┐
│ Connect Dashboard │
└────────┬────────┘
│ Secure Session
▼
┌─────────────────┐
│ Connection Layer │
└────────┬────────┘
│
▼
┌─────────────────┐
│ Connect Agent │
└────────┬────────┘
│
▼
┌─────────────────┐
│ Linux System │
│ (terminal, │
│ files, proc...)│
└─────────────────┘