This changelog lists, week after week, what was built into the platform. New features reach hosted organisations as they are rolled out to production.
- Engine — ordering guaranteed per reference. Messages sharing a reference (for instance successive versions of a transaction) are processed in order, even when they arrive out of order. A studio setting decides what happens to a message without a sequence number.
- Messaging — nothing lost on restart. Every message is journaled before it is acknowledged; on restart, processing resumes from the journal.
- Workflow — a step handled by an AI agent, as an option. A transition can call a deployed agent, with a trace of every call and an incident when a call fails.
- Console — MCP call log. Per server, per account and per organisation, with filters, details and CSV export; the organisation's prompts and resources are versioned.
- Studio — projects in git. A project links to a repository: push, pull, conflict detection; deployment can be driven by an external CI pipeline.
- Sites — versioned publishing. An external website is published in versions, with rollback to a previous one.
80 fixes over the period.
- Reports — interactive report editor. Filters, visuals and data on one screen; totals, subtotals, median and standard deviation computed by the data service; clicking a chart filters the report.
- Organisations — isolated at creation. Each organisation gets its own network perimeter, on containers as on Kubernetes, released when it is deleted.
- Per-organisation catalogues. Each organisation sees the use cases and services open to it; the others are refused by the server, not merely hidden.
- MCP connectors — OAuth sign-in. An MCP client connects with an organisation API key, after a consent screen in English and French.
- Studio — usable on tablets and phones. Workflow designer, mappings, reports and forms adapt to small screens.
- Studio — guided decision tables, checked and testable the way the engine evaluates them; flow validation offers to fix findings in one undoable command.
72 fixes over the period.
- Security — one identity per instance. Each instance starts under its own identity, with secrets derived for it alone, inside its organisation's network.
- Resources — per-instance limits. Memory, CPU and process count are capped for every instance.
- API keys — wider scopes. A key can request access to the studio, messaging, the CMS or flow ingestion, and nothing more.
- Data services — allow-list exposure. A dataset is exposed only when declared; everything else is refused by default.
- Database — versioned schema. Changes to the platform schema go through versioned, replayable migrations.
95 fixes over the period.
- One instance console for every instance type: configuration on one page, with the origin of each setting and those awaiting a restart.
- Instance logs readable for every type, with levels, search and live tail.
- CMS — storage of your choice. Content on the database of your choice, files on any S3-compatible object store.
- Studio — a site publishes in a single action, and the publishing log stays available after the dialog is closed.
- Workflow — recovery. A lost process instance is restored in place, and the screen shows where it stands.
- E-mail — restricted recipients. An instance can limit the addresses it writes to.
68 fixes over the period.