Early Access
Request early access

Security and trust

Ghosts only go where they are invited.

A tool that drives browsers against applications has to be careful about where it goes. This page describes the controls that exist today, and is just as specific about what has not been independently reviewed or approved yet.

Pixel checks the paperwork before any ghost moves.

01Boundaries

Every layer checks again.

Authorization is not a single gate at launch. Each layer between your workspace and the lab enforces its own rule, and the run stops if any of them changes its answer.

  1. 01Your workspaceSigned-in members, roles, verified email, optional two-step sign-in
  2. 02APIValidation, tenant-scoped queries, rate limits, audit records
  3. 03WorkerRe-checks grants and kill switches before every task
  4. 04Per-run sandboxgVisor, fresh Chromium, no route to internal services
  5. 05Egress proxyOne authorized origin, DNS pinned, redirects refused
  6. 06Approved labSynthetic data, reset before each attempt

02Controls

What is in place.

Target authorization

  • A platform operator grants one workspace access to one exact origin, using a signed operator tool. Workspaces cannot authorize themselves.
  • Public targets must prove ownership with a DNS record or a well-known file, and are re-verified while in use.
Implemented and tested

Isolated browser execution

  • Every run gets its own gVisor sandbox with a fresh Chromium profile, resource limits and no route to internal services.
  • All traffic leaves through a proxy that allows only the run's authorized origin and re-checks DNS on every connection. Redirects to other origins are refused.
Implemented, tested on every change

Tenant separation

  • Every workspace resource is loaded through a query joined to the caller's membership. Other workspaces get "not found".
  • Cross-tenant tests cover reads, writes, live streams and catalogs.
Implemented and tested

Credential handling

  • Test-account credentials are envelope-encrypted, injected only into the run that needs them, and never logged or returned by the API.
  • Findings, fix prompts, CLI output and AI requests never include credentials or target addresses.
Implemented; production key management pending acceptance

Evidence privacy

  • Evidence is private to your workspace, stored with retention rules, and screenshots use privacy-safe layout capture.
  • Some indirect information channels in execution results are partially mitigated and waiting for an independent privacy review.
Implemented; independent review open

Kill switches and revocation

  • Global and per-workspace kill switches, and revocable grants, are checked at start, at pickup, before every task and while actions are in flight.
  • An action already dispatched when access is revoked is aborted within a few seconds. Interrupted actions are never replayed.
Implemented and tested

03Release boundary

What is supported, and what is not yet.

Ghost Company is in early access. Customer-origin browser testing stays disabled until an independent security review, production acceptance of the infrastructure and a signed release decision are complete.

  • Browser tests in operator-approved synthetic labsAvailable
  • Browser tests against customer applicationsDisabled
  • Controlled customer pilotBuilt and tested locally; activation blocked
  • Independent security assessmentNot yet completed
  • Production infrastructure acceptancePending
  • Compliance certificationsNone claimed

What we do not claim

No completed third-party audits, penetration tests or compliance certifications. No production readiness for testing customer applications. When that changes, this page will say so with dates.

Found a security issue?

Email [email protected] with "Security report" in the subject. Please do not include real customer data. We will acknowledge your report and keep you informed.

Request early access