Security
How we isolate sessions and handle your data.
Every session runs in its own Firecracker microVM, destroyed when the session stops. Saved profiles are encrypted with AES-256-GCM. We don’t record CDP traffic or live view.
Isolation
A fresh microVM for every session.
Stopping a session destroys its VM. Warm-pool VMs are fresh boots that no session has used, so no VM is ever reused.
- Firecracker jailer
- Every session gets its own Firecracker microVM, started through the Firecracker jailer.
- Resource limits
- Each VM has cgroup v2 limits on CPU, memory and process count, and its own PID namespace.
- Read-only images
- The kernel image, the root filesystem and the browser drive are read-only.
- Network
- Each VM has its own TAP device behind default-deny firewall rules. It can reach only its own relay port, and IPv6 is disabled.
Warm
Booted fresh, never used.
Leased
Runs exactly one session.
Destroyed
Deleted when the session stops.
Default size 2 vCPU2 GiB RAM100 Mbps
Saved profiles
Profiles are encrypted at rest.
- Encryption
- Profiles are encrypted with AES-256-GCM in 1 MiB chunks.
- Keys
- Each saved version is encrypted with its own random 256-bit key.
- Integrity
- A hash of each saved version is checked before the profile is restored.
Data handling
Your traffic is relayed live, not recorded.
- CDP and live view
- Commands, replies and the live-view stream pass through in real time. We don’t record their content.
- HTTPS
- The relay passes your sessions’ HTTPS traffic through without decrypting it.
- Page history
- Apart from your jobs and saved profiles, we don’t keep a record of the pages your sessions visit.
- Your content
- You own it. We use it only to run, secure and support the service, to look into suspected Terms violations, or when the law requires it.
Have a security questionnaire? Email [email protected].