Security built around the host
ServerX secures identity, transport, routing, audit and revocation without pretending that Full Root is less powerful than it is.
Local configuration stays local
The ServerX agent reads its authority from the machine it runs on. Linux system installs use /etc/serverx/config.yaml, Linux user installs use ~/.config/serverx/config.yaml, and Windows uses C:\ProgramData\ServerX\config.yaml. The host is the source of truth.
Outbound connection
The agent opens an outbound authenticated connection to ServerX. No inbound ServerX management port is required. Enrollment uses a short-lived one-time code and the agent creates its own device identity.
Restricted or unrestricted
Read Only, Scoped and Custom enforce local rules. Full Access intentionally permits arbitrary shell and file operations with the agent account. Full Root and Full Administrator intentionally provide real privileged authority.
Revocation and audit
Disconnect an AI app or revoke a host from the dashboard at any time. Activity lists recent operation metadata: type, client, host, outcome, duration and request identifiers. New central audit entries exclude commands, paths and operation parameters. Older immutable security entries may contain target summaries.
Where requests and responses stay
Agent 0.3.2 and later keep a private local detail archive beside the device identity, limited to 24 hours, 20 MB and 1,000 operations. Older entries are removed first; large request or response previews are explicitly shortened. Cleanup runs while the agent runs, including when disconnected, and on the next startup. Activity reads these details from an online host only when you request them, without saving a cloud history. Closing the detail clears the browser view. ServerX sees tool calls and agent results, not your full AI conversation or the AI’s final reply.
Temporary delivery and security metadata
The control plane temporarily holds encrypted execution payloads for delivery. Arguments are cleared on completion; results are cleared after delivery, with fallback cleanup within about 65 seconds after the execution deadline while the service runs. The activity index is kept for about 24 hours. Security audit metadata is retained separately. Encrypted backups can retain queued payloads beyond that window until the backups are rotated. Account, host and security metadata remain necessary to operate the service. Reading local detail uses the live connection and never adds its content to that queue or the database.