Built to be verified, not trusted.
A record that must be believed is worth less than one that can be checked. Everything below can be checked by you, with no account and no call to us.
Quoted or absent
Each fact carries the verbatim clause, the source URL and the date read. A fact whose quote is not found in the source is held, never published.
Signed and chained
Snapshots, facts, changes, checks and corrections are appended to one Ed25519-signed hash chain. The recipe and the public key are published at /v1/keys.
Anchored daily
The chain head is written to a signed anchor every day.
Yours to prove
Your organization can fetch the signed ledger entry for any of its own events, reports and detections. Nobody else can ask whether one of your records exists, or when.
Public corrections
Anyone may dispute a fact from its profile. Requests and resolutions are shown on the profile and ledger-entered; nothing is edited silently.
Labels, not content
No content is kept. Labels only: who, which service, what kind of data, within policy or not. An owner can choose a redacted excerpt when a policy is broken, or exact submissions for evaluation; each is sealed, opened only with a stated reason, and expires on the period set. What each sensor records. The check API has no field for content at all.
Live health
The same report our uptime monitor reads, at https://api.openwake.ai/health/deep.
| Status | healthy |
| Vendors on record | 150 |
| Last document read | 2026-10-22 05:19 UTC |
| Ledger entries / head | 64887 / #64887 |
| Last anchor written | 2026-10-22 |
| Signing key id | 2f898a895f05b7a0 |
| Extraction | deterministic rules, no model |
Numbers we publish
Only what is measured. A count of documents read is not a count of facts proven; a fact still has to carry its quote. Coverage by product and account type is not recorded yet, and is not shown until it is.
150
340
281
latest fetch a 2xx with text
51
blocked, erroring or empty on the last read; 8 not yet fetched
109
high materiality only; noise is not counted
1 / 0
10 days
since the latest readable snapshot
The trust section, in full
What a security review needs, and where each part stands. Nothing here is a badge: a part is available, documented, or planned with its scope stated.
| Part | Status | Where |
|---|---|---|
| Security architecture and what we hold | documented | Security and trust model |
| Data flow, sensor by sensor | documented | How Openwake sees |
| Evidence standard and methodology | documented | How Openwake knows |
| Sensor capability matrix | documented | How Openwake knows, capability matrix |
| Encryption model (signing, sealing, keys, rotation) | documented | Security and trust model |
| Data retention and deletion | documented | Privacy policy |
| Closing an account or organization | available | An owner emails support@openwake.ai; export first under Reports; deleted within 30 days, backups within a further 90. Settings › Organization says the same inside the product |
| Data residency | documented | Our subprocessors, with the region stated per processor |
| Subprocessors, with 30-day notice | available | Our subprocessors |
| Access controls in the product | available | Sign-in and single sign-on; roles in Settings |
| Incident response and vulnerability disclosure | available | security@openwake.ai, published in security.txt; acknowledged in two business days, critical fixes in seven |
| Penetration-testing summary | planned | on request after the first assessment |
| Availability history | available | Status page, hosted outside the app |
| Data processing addendum | available | DPA |
| Privacy policy | available | Privacy policy |
| Worker-monitoring deployment guidance | documented | Purpose, proportionality and the employee notice, on What Openwake collects |
| Public corrections and vendor claims | available | Corrections policy |
What we hold, and where
Our own subprocessors, with the same 30-day notice we expect of vendors: /legal/subprocessors. Privacy policy: /legal/privacy. DPA: /legal/dpa.
Security contact: security@openwake.ai. We acknowledge within two business days and fix critical issues within seven. A SOC 2 Type I is planned; ask us for the current status. What each part of Openwake records, and what never leaves the machine, is on What Openwake collects.