Sandbox on every machine
Linux agents run as a non-sudo user in bubblewrap with LAN blocked by nftables. Windows agents run in locked-down Docker with an egress proxy.
Start free trialFree trial agnte runs agents on hardware you control, in sandboxes you configure once, with a journal of everything they do.
agnte runs every agent in a sandbox on your own machines, applies one central command policy to every machine, never gives agents the GitHub token, stores secrets in the OS vault and journals every call and command with its actor. agnte provides audit-ready logs; it does not hold a compliance certification today.
Linux agents run as a non-sudo user in bubblewrap with LAN blocked by nftables. Windows agents run in locked-down Docker with an egress proxy.
The sandbox self-test confirms sudo fails, /etc writes fail, SSH keys are unreadable and LAN connections are refused.
73 denied commands, denied paths and research-only web access, enforced by a pre-tool hook and logged.
Only the control layer writes to GitHub.
Owner, operator and read tokens across all 110 API routes; destructive actions need confirm or dry run.
Keys live in the OS vault (DPAPI) and are shown as hints only.
Every agent call and command journaled with its actor: 1.42M events in production.
A database backup with an integrity check on every upgrade.
No. agnte does not hold a compliance certification today. It keeps audit-ready logs: a journal of every agent call, command and decision with its actor.
On your own machines: your PC and the Linux VMs you add over SSH. Each agent runs in a sandbox on that machine.
Agents cannot read SSH keys, do not hold the GitHub token, and secrets are stored in the OS vault and shown only as hints.
Yes. A central command policy with 73 denied commands, denied paths and research-only web access applies to every machine from one screen.
We do not use tracking or advertising cookies. How we handle your data is explained in our privacy policy.