Skip to content
TestAutomate Join the waitlistWaitlist

Get notified at launch

TestAutomate isn't released yet. Leave your name and email and we'll notify you when it launches.

Home / Security TRUST & SECURITY

Security: BYOK data path, sealed secrets, self-hosting

Your key, your browser, your data. An agent that drives a real browser inside your logged-in sessions has to earn trust with architecture, not adjectives. Here is exactly how the data flows and where it stops.

Request the security overview →See the BYOK model
THE ARCHITECTURE

Six design decisions that do the heavy lifting

BYOK data pathWith bring-your-own-key, prompts and page content go from your workspace to the AI provider you configured — Anthropic, Bedrock, Gemini, or Groq — under your own key and your own data-processing agreement.
Containment by designThe agent drives your own Chrome, so logged-in sessions, cookies, and VPN access stay in the browser where they already live. Every run is bounded: step limits and hard budget ceilings stop a runaway agent by construction.
Encryption at restApp credentials the agent needs — test-account logins, tokens — are stored AES-256-GCM encrypted at rest. For the full credential-handling details, ask us for the written security overview.
Confirm-gated writesThe agent reads freely but writes carefully. Filing a Jira bug, closing a fixed issue — every outbound write is deduped and gated behind an explicit confirm. Nothing lands in your tracker because a model felt confident.
Self-host the whole stackThe entire platform runs on Node and Postgres on your own infrastructure, behind your VPN. For teams whose data cannot leave the building, nothing has to.
Tenant isolationMulti-tenant with per-workspace storage: your playbooks, learned login recipes, and run history are scoped to your org.
DATA INVENTORY

What we store — and what we never touch

Data we store

  • Your tests. Portable, human-readable YAML you can export or diff any time.
  • Run records. Step transcripts, verdicts, and the screenshots that back them.
  • Learned knowledge. Playbooks from your ingested docs, plus nav notes and quirks your runs teach the platform.
  • Encrypted credentials. Test-account logins, AES-256-GCM encrypted at rest.
  • Spend metering. Per-run model costs, so your live meters and ceilings are accurate.

Data we never store

  • Your logged-in sessions. The agent drives your own Chrome, so sessions are used in place — in the browser where they already live.
  • Your production database. The agent sees what a user sees in the browser — nothing below it.
  • Plaintext credentials. Stored credentials are persisted only AES-256-GCM encrypted.
  • Data for third parties. On BYOK, prompts and page content go to the provider you configured, under your own agreement.

For retention, logging, and model-training specifics, ask us for the written security overview.

Compliance, honestly

We are pre-launch, and we will not decorate this page with badges we have not earned. SOC 2 is on the roadmap, not on the wall. What we can give you today: a current written security overview, architecture answers directly from the engineers who built the system, and — for strict environments — a fully self-hosted deployment where the compliance boundary is your own. Ask us for the security overview and we will send the real document, not a marketing PDF.

SECURITY FAQ

The three questions every security review asks first

Where do my prompts and page contents actually go?

On BYOK, straight to the provider you configured — Anthropic, Bedrock, Gemini, or Groq — using your key, at cost, with live meters showing every call. On managed credits, to our provider account at the provider's price plus a stated fee. In both cases, never to any third party you didn't choose.

Can we run this entirely inside our network?

Yes. The full stack self-hosts on Node and Postgres. The agent already drives your own Chrome, so the browser side is inside your network by default; self-hosting brings the server side in too. Bedrock support means even inference can stay inside your cloud boundary.

How are our test-account credentials protected?

AES-256-GCM encrypted at rest, in per-workspace storage isolated per tenant. For the full credential-handling details — decryption, logging, and retention — ask us for the written security overview.

Put the architecture through your review

Get the current security overview, or start on your own key today.

Start free — no cardTalk to the founders