Draft / published data separation
PATCH writes to a draft data path; reads with the read scope return the published version. Today the approval workflow gates publish but PATCH still hits the production-served data immediately.
— roadmap
Quarterly buckets, not engineering tickets. Honest about commitment levels: shipping means active development right now, next means committed direction with details settling, considering means on the radar but not yet committed. We update this page alongside the changelog when buckets shift.
● shipping ● next ● considering
Now in active development
PATCH writes to a draft data path; reads with the read scope return the published version. Today the approval workflow gates publish but PATCH still hits the production-served data immediately.
Workspace-level inbox at /settings/approvals listing every pending request across every entry. Approvers see what needs action without hunting through the Library.
First-run checklist for new workspaces: push your first schema, invite teammates, configure preview URL, mint a public API key.
Engagement in progress with an EU-based audit firm. Type I targeted for Q3; Type II observation period commences immediately after.
Committed for the next cycle
French, Dutch, German translations. Locale switcher in the header. Auto-detect on first visit; respect the user's choice afterward.
Pause / resume per subscription without delete. Manual replay of a single delivery. Per-subscriber rate limiting.
Today every Object-Storage-backed asset is public-read so imgproxy can fetch without presigning. Customers needing private assets get a per-asset opt-in.
Sovereign-cloud customers get their own AWS Outpost / Scaleway sovereign-cloud region. Standalone Helm charts for single-tenant deployment.
Committed direction; details settle as we ship Q4
Audit window completes; report available to Enterprise- and Sovereign-tier customers under NDA.
Information-security-management-system implemented against the standard's control set; stage 1 audit planned alongside SOC 2 Type II completion.
When DORA pack generation, webhook delivery, or residency proofs sustain >5/s, the workers extract from the API container into a dedicated apps/workers deployment. Trigger-on-demand.
Move from the S3-backed queue to Valkey + BullMQ when alerts fire on queue depth or oldest-pending age.
Specialised approval policies for regulated content categories — financial disclosures, medical-information leaflets, government communications. Pre-built role templates per regime.
On the radar but not committed
Strict opt-in module for customers who want it. Brand voice is sovereignty + durability; AI can't become the default. The integration that lands first will be EU-hosted and explainable.
For agencies running multiple regulated customers from the same Studio. Per-tenant theming + sub-processor register + DPA tooling.
Today GraphQL is read-only; writes go through REST. Mutations land if Enterprise customers ask for them; otherwise the simpler surface stays.
Two-editor concurrent editing on the same entry with operational-transform conflict resolution. Big lift; the use case has to be widespread before we commit.
— what's missing?
Customers shape the roadmap. If a capability you need is missing from this page, email us — every request goes into the same review process as our internal priorities. We don't do feature-gated "pay for development" deals; customer signal moves work earlier in the queue.
Contact us →