Talk to sales

Built so you never have to take our word for it.

Nobody can quietly change a Runfile record, including us. Here’s what protects the evidence and your data, and the documents your security team can have today.

Try to tamper with a recordGet the security pack
01 — Who could change a record?Pick someone

Who could change a record? No one, quietly.

Four people who might want to alter the evidence, and what stops each of them. Pick one to see what happens.

Scenario 01 of 04Detected

An engineer on your team

Tries to: Edit one event so a mistake disappears.

  1. Event 1a41f
  2. Event 27c09
  3. Event 3e2d5
  4. Event 43b8a
  5. Event 5f61c
  1. Daily seal8a3f
  2. Public log8a3f
The chain breaks after the edit, so the daily seal no longer matches.
What stops it
Each event carries a hash of the one before it. Change one and every later link stops matching. Nobody at your company holds the signing key, so no one can re-seal the day.
What the auditor sees
The verifier fails and points to the exact event that changed.
How the sealing works →

In every case, the auditor checks the result with our offline verifier. No network calls, and Runfile isn’t in the loop. See a sample evidence package →

02 — Your data, start to finishFive protections

From your systems to the public record.

What protects an event from the moment your agent creates it.

01In your systems

Personal data becomes tokens

The SDK swaps personal data for tokens before anything leaves. We never see the originals.

M. Okafor → tok_3f9a
02In your region

Kept where you choose

Each customer’s records stay in one region: EU or US today, UK from month six.

EU · US · UK
03As it’s written

Chained to the event before

Every event carries a SHA-256 hash of the one before it, so an edit or a gap shows.

SHA-256 hash chain
04Every day

Signed and locked

A daily seal is signed with a key unique to you, inside a FIPS 140-2 Level 3 HSM, then stored where nobody can change it.

HSM · S3 Object Lock
05Every week

Anchored in public

The week’s seal goes into Sigstore Rekor, a public log. It holds the hash only, never your data.

Sigstore Rekor

Where it runs

Three ways to deploy. In every one, your team can’t touch the signing keys, and the public log means we can’t misuse them.

Option 01Default

Shared, in your region

Multi-tenant SaaS on AWS, in the region you pick.

For most teams
Option 02

Single-tenant

Your own isolated deployment, run by us.

From $150K a year
Option 03v1.5

In your own cloud

Ingest runs in your AWS account. Signing stays with us, so the keys stay out of reach.

For the largest customers
03 — Certifications & roadmapWith honest dates

What’s done, and what isn’t yet.

No badges for things we don’t have. Here’s what’s in place, what’s underway and what’s next.

In place4

  • SOC 2 Type ISecurity, Availability and Confidentiality criteria, from an AICPA-registered CPA firm.Issued month four
  • HIPAA business associate addendumReady to sign. Health data is tokenised before it reaches us.From day one
  • Penetration testBlack- and grey-box, by Independent Security Evaluators. Two medium findings, both fixed and re-tested.2026 · Q1
  • EU and US data residencyRecords stay in the region you choose.Live

Underway4

  • SOC 2 Type IIThe observation window is running now.Report expected mid-Q3
  • ISO 27001All 93 Annex A controls tracked. Stage-1 audit booked for Q3 2026.Certified by month fifteen
  • ISO/IEC 42001The AI management system standard, prepared alongside ISO 27001.In parallel
  • UK data residencyA UK region for your records.Month six

On the roadmap5

  • Attested signingSigning inside a Nitro Enclave, with proof of the exact code that ran.v1.5
  • OAuth2 and mTLSClient-credential and mutual-TLS access, on top of scoped API keys.v1.5
  • SIEM streamingStream the audit trail into your own Splunk, Sentinel or Datadog Security.v1.5
  • Two-approver workflowsMulti-approver sign-off on Enterprise.v1.5
  • FedRAMP ModerateNot before we have paying federal customers, and it needs a sponsoring agency.Long-range

The spec sheet

Quick answers for your security questionnaire.

Signing keys
Held by Runfile, one per customer, in a FIPS 140-2 Level 3 HSM. Never in your agent runtime.
Integrity
SHA-256 hash chain per event, a signed Merkle root every day, a Sigstore Rekor anchor every week.
Storage
S3 Object Lock in compliance mode. Not even the AWS root account can delete within the retention period.
Personal data
Tokenised in your environment. The token vault has its own key, IAM boundary and audit log.
Retention
30 days hot on Starter, 90 days on Growth, 7 years on Enterprise.
Residency
One region per customer: EU or US today, UK from month six.
Access
Scoped API keys. TOTP multi-factor sign-in; SSO on Enterprise.
Sub-processors
AWS (your region), Sigstore (hash only), Datadog (scrubbed telemetry), Stripe (billing only). 30 days’ notice of changes, with a right to object.
Verification
Offline verifier. Checks a package with no network calls.
Insurance
Cyber liability and tech E&O, $5M aggregate.
04 — The security packPick what you need

Everything your security team will ask for.

Pick what you need and we’ll send it. Anything under NDA follows once our two-page mutual NDA is signed.