What is shipped, what is next, and what we will not claim.
A public ledger of where Writ actually is. Three statuses, no invented dates, and no certification we do not hold. If a thing is not on this page, we have not committed to it.
How to read this
Three statuses, and what each one means
We use three labels and nothing else. No percentages, no progress bars, and no quarters unless a real plan puts one there.
- Shipped
- In production today. You can use it now, and we will answer detailed questions about how it works.
- In progress
- Actively being built or closed out. We give no date, because a date we cannot keep costs more trust than no date at all.
- Planned
- Scoped and sequenced, but not started. It sits behind the work above it, and it can be reordered or dropped.
Last reviewed · July 2026
The honest answer
What we can say about SOC 2 today
Writ is not SOC 2 certified, and we do not display certifications we do not hold. A code-grounded readiness assessment across all five Trust Services Criteria is complete, and the sequence from there is a Type I design assessment followed by a Type II observation window. We are not putting a quarter on that until an auditor is engaged and the window is set. When each step lands, it will be stated here.
What exists today, instead
- GDPR-aligned controls, with data export and account erasure you can run yourself.
- A Data Processing Addendum we will sign for your organization.
- Encryption at rest for sensitive material, and TLS 1.2 or better in transit.
- Tenant isolation enforced at the data layer, on every record.
- A current security review, available to enterprise teams on request.
Security and compliance
The controls a security buyer asks about, and the ones we have not built yet.
6 Shipped 2 In progress 5 Planned
SOC 2 Type II
Not certified. The readiness assessment is done and mapped to code; a Type I design assessment comes first, then a Type II observation window. No date until an auditor is engaged.
In progress
GDPR-aligned controls, DPA, export and erasure
A published privacy policy, a signed Data Processing Addendum, versioned consent capture, self-serve data export, and account or organization deletion that cascades across tenant-scoped resources.
Shipped
Encryption at rest and in transit
Sensitive material - passwords, 2FA seeds, vault secrets, tokens, sessions - is encrypted at rest. TLS 1.2 and 1.3 only in transit, with HSTS.
Shipped
Multi-factor authentication and passkeys
TOTP and WebAuthn are available on accounts today, with replay protection, progressive brute-force lockout, and single-use refresh rotation.
Shipped
Single sign-on (SAML 2.0) and SCIM provisioning
A SAML 2.0 service provider with strict assertion validation and replay protection, alongside OIDC, plus SCIM 2.0 user and group provisioning so joiners and leavers follow your directory. Available to Enterprise teams.
Shipped
Security review on request
Enterprise teams can request a current security review, the DPA, and the detail behind any claim on this page. We answer with evidence, not a badge.
Shipped
Vulnerability disclosure policy
A published intake, safe-harbour terms, scope, and response targets for reporters. Live on the security page.
Shipped
Maintained sub-processor register
The list is published today in the DPA and the Trust Center. Promoting it to a register under change control, with every vendor mapped to a countersigned agreement, is the remaining work.
In progress
Enforced MFA for platform administrators
MFA is opt-in today. Making it mandatory for platform-admin and billing-admin accounts is on the critical path to a Type I assessment.
Planned
Authentication events and tenant scope in the audit log
The audit subsystem is append-only and covers mutations. Persisting login, MFA and passkey outcomes, and stamping a tenant identifier on every record, is not done.
Planned
Read-access logging and an org-admin audit view
Today only writes are recorded, and the log is readable by platform admins only. Logging sensitive reads and giving organization admins their own view are both outstanding.
Planned
Merge-blocking CI with security scanning
CI builds, migrates and tests on every push, but does not block a merge. Branch protection, required review, secret scanning, dependency scanning and static analysis are all still to come.
Planned
Independent penetration test
No third-party test has been commissioned. An annual external test is expected by most auditors and is on the list.
Planned
Open source and self-hosting
Open core: the engine you can run yourself, and the boundary that keeps it honest.
2 Shipped 3 In progress 2 Planned
Self-hostable stack in one command
The recorder, the workflow engine, the local API and MCP come up with Docker Compose on your own server, single-tenant, with no cloud account.
Shipped
Bring-your-own AI keys, unmetered
Point the self-hosted engine at your own provider or a local model. Your keys stay on your machine and Writ never meters or marks up AI on that build.
Shipped
One repository, one history, never a fork
The commercial layer lives beside the core in the same tree rather than in a parallel project, so a community contribution flows into the hosted product without a back-sync.
In progress
A CI-enforced boundary around the core
The core must never import from the commercial layer, and the community build must be a deterministic strip of the same tree. Enforcing that in CI, for both Python and Rust, is underway.
In progress
Gateway and streaming embedded in the self-hosted backend
MCP and agent connectivity already run inside the single backend. Folding the AI gateway and the streaming session manager into mountable modules, so one process serves them all, is the remaining refactor.
In progress
Secret scanning and a release gate on the public repository
Before anything is published: history cleaned of historical keys, secret scanning on every push, and a build assertion that no commercial code or credential ships in the community artifact.
Planned
Contribution flow: CLA and CODEOWNERS
A contributor licence agreement and ownership rules on the commercial paths, so outside pull requests can be accepted without licensing ambiguity.
Planned
Platform reliability
What keeps the hosted platform up, what recovers it, and where the single points of failure still are.
4 Shipped 5 Planned
Published SLA with uptime and support targets
A 99.9% monthly uptime target for the Writ-managed services, with support response targets and an incident communication policy. Credits are measured against the public status record, not a marketing figure.
Shipped
Automated backups with a weekly restore drill
Daily database backups with retention, and an automated, schema-validated restore drill every week. The drill runs whether or not anyone is watching.
Shipped
Metrics, dashboards and alerting
Service and infrastructure metrics with dashboards and alert rules covering host, container, database, cache, queue depth and capacity, routed to chat and to an audit trail.
Shipped
Abuse and anomaly monitoring
Live quota, cost, failure-spike, velocity and blocked-domain signals, with automatic throttle or suspend rules, each action written to the audit log.
Shipped
Point-in-time recovery
Backups are snapshots today, so recovery loses whatever happened since the last one. WAL archiving to close that window is planned and not built.
Planned
Failover for stateful services
The database, cache and object store are single instances. Replication and failover, plus leader election so the coordinator can run more than one replica, are the next reliability step.
Planned
Off-platform uptime probing and paging
Alerting today runs on the same infrastructure it watches. Probing from outside it, and paging a human on critical alerts rather than posting to chat, are both outstanding.
Planned
Durable background job queue
Scheduling, heartbeats, cleanup and queue processing run as in-process loops. Moving them onto a durable queue with retries and visibility is planned.
Planned
Zero-downtime deploys with a change record
Deploys swap the stack and leave no structured trail. Rolling restarts, plus a record of who deployed what and when, are planned.
Planned
Developer surface
The API, MCP and automation surface your software calls, and what is missing from it.
3 Shipped 3 Planned
Workflows as REST endpoints and MCP tools
Publish any workflow as a callable endpoint and an MCP tool, with scoped keys, consumer keys and custom domains.
Shipped
Watch-and-Act
A change detected by a Monitor can trigger an Automation that fires a Workflow, behind a dry-run, a confirm-gate and idempotency.
Shipped
Encrypted credential vault
Secrets are referenced by name, encrypted at rest, resolved only inside a single run, and never returned by the API, shown to the AI, or written to logs.
Shipped
Webhook delivery log with retries and redelivery
Outbound webhooks are signed but delivery is not tracked. A delivery record, automatic retry with backoff, and manual redelivery from the dashboard are planned.
Planned
Per-key usage metering
Usage is metered per organization. Breaking it down per API key, so you can attribute spend to a service or a customer, is planned.
Planned
Price locked at session start
A long session reads live model rates, so a quoted price can drift from the charged one. Locking the rate at session start is planned.
Planned
Integrations
How Writ reaches the rest of your stack, and how the rest of your stack reaches Writ.
4 Shipped
n8n, Zapier and Make
Trigger a Writ workflow from an orchestrator, or map a Writ event to an action in one. Each has its own setup page, and the authorization path below is the one they use.
Shipped
OAuth 2.0 authorization server
Third-party applications connect with the authorization code grant, PKCE, token revocation and published server metadata, so a tool can be authorized once instead of holding a long-lived key.
Shipped
Signed outbound webhooks
Per-organization webhook configuration and recipients, delivered with a signature and replay protection so a receiver can verify the event really came from Writ. Delivery history and retries are the planned part, listed above.
Shipped
Notification inbox and delivery preferences
Run failures, low balance, security events and update-available land in an in-app inbox, with per-user preferences controlling what is delivered and where.
Shipped
Billing and metering
How the money paths work today, and the finance work still open before they scale.
2 Shipped 4 Planned
Prepaid wallet metered by running time
A monthly pool of included usage with a prepaid top-up past it with micro-dollar precision. Cloud runs are metered by actual running time, runs on your own machine carry no compute charge, and hard spend caps are on by default.
Shipped
Crash-safe, idempotent metering
Charges take a row lock and an idempotency key, and reserve-then-settle holds mean a crashed run cannot double-charge or silently lose a hold.
Shipped
Tax collection at checkout
Automatic tax, billing address and business tax ID collection are not wired into checkout. Required before invoicing at scale in the EU and UK.
Planned
Receipts for wallet top-ups
Subscription invoices come from the payment provider, but a wallet top-up produces no customer-facing receipt. Planned.
Planned
Dunning and a grace period on failed payment
A failed payment is recorded and emailed once, but does not yet restrict paid features after a grace period. Retry orchestration and enforcement are planned.
Planned
Settlement dead-letter queue and denied-charge audit
A settlement that fails mid-flight has no queue to land in, and a denied charge leaves no audit entry. Both are needed before reconciliation can be fully automated.
Planned
The small print, in plain words
This roadmap is indicative
It describes what we intend to build, in the order we currently intend to build it. It is not a contractual commitment, it does not form part of any agreement, and any item can change, move, or be dropped without notice. Do not buy on the strength of a planned item; buy on what is shipped. If a planned item is the reason you would sign, tell us and we will tell you honestly where it sits.
Evaluating Writ for production?
Ask us what is real today, what is close, and what we have not started. You will get the same answer as this page.