Security model
The security boundary is not a promise — it is six verifiable mechanisms
Each one is written into product behavior, not marketing copy.
Back to home →01
Explicit target routing
Every browser, command, and file action names its target computerId. Wrong machine, offline, or not allowed — it fails explicitly and never silently switches to another machine.
- Missing ID, mismatch, revocation, or missing capability: explicit failure, every time
- Resource handles stay bound to their original computerId — no cross-machine reuse
- Operation records name the machine that actually executed
02
Actions you can audit and answer
Every action answers two questions: which machine it landed on, and who approved it. Audit records are written in the same transaction as the operation, not added afterwards.
- The approved target is the machine that actually executes
- Results and audit records name the target machine
03
Credentials and encryption
Admin passwords are stored as argon2id in PHC form; plaintext never touches storage. Sensitive fields get field-level encryption. Model keys are BYOK — they belong to your company's own accounts and never ship inside the client build.
- The workspace stays locked until the first-launch password change completes
- Passwords live only as argon2id in PHC form — plaintext never touches storage
- Model keys are BYOK and never ship in the client
04
Network egress, fail-closed
The agent reaches internal systems through a client egress you authorize. Dropped links, expiry, revocation, or a policy failure close the path — falling back to direct access is never allowed.
- Egress selection is an explicit lifecycle
- Switching egress never reuses the old channel
05
Device lifecycle
Existing computers and servers enroll with a single command. Unenrolling revokes access only — no shutdown, no reinstall, no touching the machine's own data.
- Enrollment completes in one command
- Unenrolling revokes access only
- No shutdown, no reinstall, no touching the machine's data
06
Data you own
Self-hosted deployments default to SQLite, with data files on your own server. This site itself carries zero third-party tracking — data ownership starts with not peeking yourself.
- The default and only required database is SQLite
- Data files live on your own server
- Zero third-party tracking on this site