Changelog

A dated record of what we've shipped — features, fixes, and security changes.

Unreleased

Changed

  • List pricing raised to $199 / $499 / $999 per month (Starter / Growth / Grounded), up from $100 / $300 / $600. The landing-page FAQ now renders its price labels from config like the pricing page does, so every displayed price tracks the PRICE_STARTER_LABEL / PRICE_PRO_LABEL / PRICE_SCALE_LABEL settings from one source. The amount actually charged is set by the Stripe Price objects behind STRIPE_PRICE_STARTER / STRIPE_PRICE_PRO / STRIPE_PRICE_SCALE; update those and the labels together so the page and the charge never disagree.

Added

  • Customer-cloud runner (beta, off by default) — a drill can run inside the customer's own cloud (dokaz-runner, Dockerfile.runner) so the backup bytes never reach Dokaz; only the signed result does. An account enrols a runner (cloudrunner-admin), which polls POST /internal/runner/v1/claim and then restores over the ordinary sandbox protocol. An account with a runner is always routed to it — never silently to a Dokaz sandbox. Turned on with CUSTOMER_CLOUD_RUNNER=1; dormant until a runner is enrolled. See `docs/phase-2-runner.md`.
  • Suggested checks — after every restore Dokaz records the restored database's schema (tables, columns and types, keys, row counts and the newest value of created/updated-style columns — never row data) and proposes checks from it by fixed rules, each with a plain-English reason: table_exists for key tables, row_count floors at about 90% of the rows seen, column_exists for key columns, no_nulls for id- and email-like columns that had none, freshness for live tables and foreign-key orphan checks. Nothing runs until you accept a suggestion (one by one or "accept all recommended" on the database page); dismissed ones stay dismissed. API: GET /v1/databases/{id}/suggestions, POST …/suggestions/{sid}/accept and …/dismiss.
  • `freshness` assertion — {table, column, max_age_seconds} passes when the column's newest value is at most that far behind the drill's backup time (or its start when the backup time is unknown); the result says which.
  • Schema drift — each drill compares its schema with the previous successful drill's: tables and columns added or removed, type changes, row-count drops over the database's threshold (default 20%) and newest timestamps that went backwards. Shown on the drill and database pages, in a "Schema changes since last drill" section of the signed PDF and at GET /v1/drills/{id}/schema-drift; removals and big drops are alerted by email, Slack and a drill.schema_drift webhook. Drift is informational and never changes a verdict.

Fixed

  • Regenerating a sandbox drill's evidence (staff) now keeps the restored backup object in the PDF.
  • The API reference now lists the sql_query assertion kind.

2026-10-12

Phase 1: drills of your own backups. Everything below ships in the code today; customer drills switch on per server once its restore sandbox (and, for push, its ingest bucket) is provisioned, and every page says which applies — until then drilling your own backups is in early access and the sample drill is what works.

Added

  • Drills of your own backups — a drill of a connected bucket (or of a pushed upload) now restores the backup in an isolated, single-use sandbox machine that receives only a short-lived link to that one object, never your credentials, and is destroyed afterwards. The signed report names the exact object restored, its SHA-256, and the measured RTO, which is cross-checked against when Dokaz received the sandbox's progress reports (recovery.rto_basis). A pushed upload's declared checksum is verified against the bytes restored, and the upload is deleted after the drill unless you keep uploads. On a server without the sandbox, starting one answers 409 sandbox_unavailable.
  • Connect your backup bucket — point Dokaz at the bucket your backup job writes to (AWS S3, Cloudflare R2, Backblaze B2 or MinIO) with a read-only key, choosing one exact file or the newest backup under a prefix, and click Test connection to see the backup a drill would use (or exactly what to fix). Also over the API: source on POST /v1/databases, PATCH /v1/databases/{id}/source and POST /v1/databases/{id}/test-source. The secret key is encrypted for your account and never shown or returned again.
  • Push your backups — a push database receives its dumps straight from your backup job: one curl -T to PUT /v1/databases/{id}/upload (up to 5 GiB, SHA-256 computed as it streams, optional declared checksum and backup time, ?drill=1 to drill it), or a presigned single or multipart upload for larger dumps. API keys get an uploads:write scope. Each upload is deleted after its drill unless you keep uploads (at most 7 days); unfinished uploads are removed after 24 hours.
  • Measured RTO and RPO — every drill records how long the restore took (fetch + restore) and how old the backup was, labelled with where the backup time came from (declared, upload completion or S3 Last-Modified — the last two are upper bounds). Set RTO / RPO targets per database and a drill that misses one fails. The figures are in the signed PDF's Recovery metrics section and the API's recovery object, and the ed25519-v3 evidence signature covers them: dokaz-verify rejects edited figures.
  • Daily sandbox time per plan — drills of your own backups get 6 / 24 / 72 sandbox hours per rolling 24 hours (Starter / Growth / Grounded). A drill over the budget fails at once with signed evidence saying why.

Changed

  • Product copy follows the server — the home page, pricing, how it works, help, the dashboard, the API docs and the welcome email describe connecting a bucket, pushing from your backup job, the isolated sandbox and measured RTO / RPO only on a server that runs them; elsewhere they say drilling your own backups is in early access and point at the sample drill. The early-access "concierge setup" offer is withdrawn.
  • Plan limits stated from the code — pricing lists each plan's largest backup per drill (Starter 50 GB; Growth and Grounded 166 GB, the most the largest sandbox disk can restore), restore budget (1 / 8 / 24 hours) and daily sandbox time. SSO/SAML, a runner in your VPC, hourly drills, a BAA, region selection and annual invoicing are no longer mentioned, not even as roadmap: none exists.
  • Early-access dump files move to push — new databases can no longer use a dump file on Dokaz's server (the deprecated source_uri is refused with 400). Databases already set up that way keep drilling their file unchanged and already accept uploads; we switch each to push once its first upload arrives (an upload before then answers drill_error: migration_pending).
  • Where drills run, stated precisely — each drill restores into a throwaway database Dokaz creates for that drill and drops afterwards; it never connects to your production database.
  • Pricing page — removed features that were listed but not built (a custom assertion library, 30-day raw restore logs, 500 GB / 2 TB restore caps). Evidence bundle export is on demand and included on every paid tier.
  • Compliance strip — now names the controls the evidence is built for (SOC 2 A1.3, ISO 27001 A.8.13, HIPAA §164.308(a)(7)) instead of claiming auditor or insurer acceptance. Dokaz makes no HIPAA-compliance or BAA claim.
  • Legal — the sub-processor list names the actual vendors (Fly.io, Neon, Stripe, Postmark, Firebase Cloud Messaging; PostHog, Sentry and Cloudflare R2 — for pushed backups — when enabled). Privacy Policy and DPA describe the temporary restore database and sandbox, that the sandbox never receives your storage credentials, how long pushed backups (at most 7 days) and early-access dump files are kept. The DPA is marked as a draft pending legal review.
  • API reference — lists the signature, logs, alerts, and check-in endpoints; examples use https://dokaz.net (the old app.dokaz.net host never resolved).
  • Schedule hint — no longer says higher plans unlock sub-daily drills; every paid plan drills daily and sub-daily is by arrangement.

Fixed

  • Responder app (Android) — fixed a launch crash (the main activity was declared in the wrong package), and the app now defaults to https://dokaz.net instead of a host that never resolved.
  • Check-in ping example in Help now uses https://dokaz.net/ping/<token>.

2026-07-06

Added

  • Teams within an organization — an account can partition its databases and members into teams. A non-privileged member sees only their teams' databases (plus any left unassigned); owners and admins see everything. Managed from a new Teams page. (#29)
  • Evidence master-key rotation — the at-rest encryption master key can now be rotated with zero data loss: retired keys are accepted during a rotation and each per-account key is re-wrapped under the new key on access. Ships an evidence-keys ops tool (verify / rewrap / shred-poison) and a rotation runbook (docs/runbooks/evidence-key-rotation.md).
  • "Verify a report" in the main navigation — the public evidence verifier is now reachable from the site header nav and the in-app sidebar, not only the footer.
  • Offline-verifier discoverability — the /verify page now links to the Apache-2.0 dokaz-verify CLI source and shows the command to run it, so an auditor can verify evidence fully offline against the published keys.

Changed

  • Pricing — self-serve tiers rebuilt as Starter $100 / Growth $300 / Grounded $600 (monthly, USD); prior prices archived. Existing subscribers are unaffected — they stay on the price they signed up under.
  • Reports — the 12-month history window and CSV export now unlock on any paid plan (previously only the middle tier, which wrongly excluded the top tier), consistent with the evidence-bundle export beside them.
  • API reference — the authentication example is now cross-platform (bash / zsh and Windows PowerShell). (#32)

Fixed

  • Subscribe & billing buttons on production — the live Stripe Customer Portal had no configuration, so every "Manage billing" click and every already-subscribed "Subscribe" redirect returned a 500. The portal is now configured and verified end-to-end. Billing handlers additionally log Stripe failures server-side instead of surfacing raw errors to users. (#33)
  • Evidence report step failing after a good drill — drills that restored and passed every assertion were failing at the report step (unwrap account key: message authentication failed) for accounts whose encryption key was created before the persistent master key was set. The stale (unrecoverable) key rows were cleared; the new rotation tooling prevents recurrence.

Security

  • License & copyright — the repository is now explicitly proprietary / all-rights-reserved (© 2026 Ian Lee), with an Apache-2.0 carve-out for `cmd/dokaz-verify` so auditors retain an unambiguous right to build and run the independent evidence verifier. Per-file notices, LICENSE, and NOTICE added.
  • Team-scoped access control — database, drill, and evidence access — including auditor share links and the evidence-bundle export — is now scoped to a member's teams and enforced in the data layer, not just the UI.
  • Evidence-key rotation — closes the "lost or changed master key ⇒ permanently unrecoverable evidence" risk by making key rotation a supported, no-data-loss operation.

2026-07-05

Added

  • Exec and Auditor roles — an internal executive (read-only) role, and an external Auditor role: a real account for a compliance reviewer, scoped to drills, evidence, and targets, with no access to billing or the member roster.
  • Backup check-ins (heartbeats) — a passive complement to drills. Register a monitor with an expected period, ping a URL from your backup job, and get alerted (webhook + audit event) when a check-in goes overdue.

Changed

  • Pricing rebrand — self-serve tiers renamed Starter / Growth / Grounded, daily drills on every tier, and the drills/day cap reframed as a workload budget.
  • Restore timeout raised from 30 minutes to 6 hours to accommodate large dumps (surfaced by a new drill-stress harness).

Fixed

  • Assertions on schema-qualified tables — row_count / no_nulls now schema-qualify their target, and a "relation does not exist" failure is explained clearly instead of leaking a raw database error.

2026-05-25

Security

  • Hardening pass — a security-review remediation across revenue- and data-safety-critical paths (idempotency, CSRF, and related fixes). See `docs/security-audit-2026-05.md`.

Added

  • Full pg_dump format coverage — the runner restores all four logical formats (plain, custom, tar, directory), detected from file content rather than the extension.

2026-05-22

Added

  • Public marketing surface — landing page, a "how it works" explainer, and a public pricing page.
  • Subscriptions & billing — Stripe subscription lifecycle (Checkout, Customer Portal, signature-verified webhooks), usage-based metering, staff-issued refunds, and per-tier plan limits.
  • 14-day trial (read-only until subscribed), scheduled recurring drills, and month-over-month drill reporting.
  • Per-drill Fly Machine sandbox and an S3 / R2 evidence store (SigV4-signed, Object-Lock capable).
  • Staff admin panel with SSO step-up and safe, reason-logged impersonation; feature flags (PostHog) and Grafana dashboards as code.

2026-05-21

Added

  • The 11-layer foundation — the drill orchestrator and restore-and-assert pipeline; multi-tenant accounts with RBAC; perimeter security (CSRF, rate limiting, login throttle, signed webhooks); signed Ed25519 evidence with 7-year retention and GDPR data rights; observability (structured logs, metrics, tracing); transactional email + analytics; legal pages and a WCAG 2.2 AA pass; the staff support/admin panel; and the versioned /v1 JSON API (API keys, idempotency, cursor pagination).
  • Identity & auth — TOTP two-factor, passwordless magic-link login, Google + GitHub OAuth, and email verification.
  • Evidence integrity — at-rest encryption with per-account crypto-shred, signing-key rotation via a verification-key set, and multiple assertion kinds per database.

2026-05-20

Project began as Restore Drill, the automated backup-verification product that became Dokaz (renamed Restore Drill → Soteria → Vesta → Dokaz). Earlier commits under a "Screen Dissector" prototype predate that pivot.