Security

We sell governance. So here is ours.

Our job is refusing the wrong action and proving the right one. Every claim below can be checked independently.

Bring your security team

EVERYTHING BELOW IS BUILT AND RUNNING · NOT A ROADMAP

Fail-closed posture

When anything is uncertain, the answer is no.

Ambiguity, misconfiguration, or partial failure produces refusal, never silent success.

The rule

One failure, one outcome.

Unverifiable input is refused, not given the benefit of the doubt
A degraded component stops rather than running weaker
A partial failure keeps none of what succeeded

Why it's the default

The expensive failure is a fast, wrong yes.

A slow no costs a retry. A confident, wrong yes costs money and trust.

The evidence chain

Don't take our word for anything. That's the design.

Ed25519 signatures and SHA-256 hash chains, deliberately unoriginal. Every signed format is versioned, so the algorithms can evolve without breaking today's receipts.

§1

Signed receipts

Any third party holding one can verify it independently.

§2

Hash-chained ledger

Integrity anchors are independently verifiable. Tampering is mathematically visible, not policed after the fact.

§3

Consent & lead evidence

Content hashes, defined retention windows, redaction support.

No separate compliance view. The evidence chain is the system of record.

Isolation & identity

A caller proves what it is. It never decides what it's trusted to do.

Multi-tenant systems fail quietly at the boundary. Identity, trust, and access never come from the caller.

TENANT ISOLATION

Adversarially tested. Public responses never reveal whether a resource exists.

ENFORCED

RATE & SIZE LIMITS

Rate-limited and size-capped at edge and application.

DUAL-LAYER

AGENT IDENTITY

Resolved server-side. A caller says what it wants, never who it is.

SERVER-RESOLVED

Perimeter & credentials

Every operator request clears two independent identity checks before anything renders.

Most breaches walk in through an admin panel or a leaked secret.

Production access

Basic Auth, then per-operator SSO, on every request.

The operator console clears HTTP Basic Auth, then per-operator SSO through WorkOS, before any page renders
Host access is tailnet-only: SSH is closed to the public internet at the cloud firewall
Databases and internal services are never exposed to the internet

Secrets & credentials

Nothing plaintext, nowhere.

Secrets are encrypted at rest
No plaintext credential exists in the codebase

Supply-chain risk, handled

The quietest attack surface, kept deliberately small.

Six controls, exercised in CI on every change rather than audited once.

STATIC FRONT DOOR

Static HTML. No npm, no build step, nothing to poison.

4 RUNTIME DEPS

The operator console runs four. Adding one is a reviewed decision.

IGNORE-SCRIPTS

Disabled for every npm install. The worm class's primary vector never runs.

LOCKFILE-EXACT

CI installs exactly what the committed lockfile says.

7-DAY COOLDOWN

Updates wait seven days, then land as one human-reviewed batch.

PINNED PYTHON

Pinned per-service requirements. CodeQL on every pull request.

Full dependency review 2026-07-11: zero advisories, production and full tree.

Independent penetration test (Phase 1) 2026-08, all in-scope findings remediated. Full-codebase security review 2026-07. Provisional patent filed 2026-07-24.

FOUND SOMETHING? Reports go straight to the founder: [email protected]. Full terms: security.txt.

Certifications

Verifiable today. Certified next.

The controls below are architecturally verifiable right now: check the receipt and key endpoints yourself. Third-party certification is separate work, stated here rather than left silent.

Signed receipt verificationLIVE

Hash-chained settlement ledgerLIVE

Public key endpointLIVE

SOC 2 Type IIPLANNED

Certification changes who else has checked our homework, not what holds.

Verify a real receipt yourself, entirely in your browser →