Security & data boundary

An agent control plane is a security product first.

Hosted Hermes runs an always-on agent on a fenced VPS. The agent touches repositories, inboxes, and infrastructure — so the boundary around it is the product. This page states that boundary plainly. No certifications are claimed here; every statement below describes shipped behavior you can verify.

01

Fenced execution

Hosted Hermes tasks execute in isolated fenced VPS sandboxes — not on your machine, not in a shared pool identity. Every task thread holds a 90-second renewable lease; only the current unexpired lease-holder can complete a task, so a crashed or superseded run cannot race its replacement.

02

Human gates on consequences

Money, customer-facing, and production actions pause for your approval in the thumbgate.app browser. Before sensitive tool calls execute, an LLM-as-a-Judge policy layer checks for destructive commands, secret exfiltration, and spend overruns. The agent cannot approve itself.

03

Receipts, not surveillance

Every consequential action produces a receipt inside your authenticated workspace — an audit trail of what the agent actually did. Receipts exist for you, not for us: they never feed our analytics and never leave your workspace.

04

Content-free analytics

Our telemetry is aggregate counters on a fixed event allowlist: an event name, a day, optional first-party campaign tokens. No prompts, no thread contents, no keystrokes, no email addresses, IP addresses, cookies, or user-agent strings. Free-form fields are rejected at the endpoint.

05

Your runs stay yours

We do not train models on your data. Public stats on the expertise page are aggregates with canary runs excluded and organization identities never exposed. The methodology is published at /api/expertise/stats.

06

The browser is untrusted

A signed-in browser session does not get full VPS access. Sessions without a matching capability cannot reach core commands, and gated actions still pause for explicit approval — a stolen tab is not a stolen agent.

Verify it yourself

The machine-readable boundary lives at /llms.txt. The engineering write-up is on the blog — start with “Leases, receipts, and a judge” and “Your agent’s telemetry should be content-free.” Live aggregate stats: /api/expertise/stats.