Roadmap

In progress. Parts of these are already in the product; the item stays here until the whole of it has shipped.

• Fix the domain identityMailS · days

  Make the server domain, the AI address default and the environment agree, and accept both spellings during the cutover. The code accepts both spellings and its defaults agree; the environment setting on the server is the remaining step.

• Kill switch, retention, one send pathMailS · days

  The platform and per-mailbox kill switches exist and the hub's mail goes through the platform's one listener; three direct send sites (the mail handler, the chat tool, the cascade scheduler) still bypass the one send function, and the mail retention job is not written.

• Passkeys and device sessionsPlatformS · days

  WebAuthn sign-in with hardware keys for admins, next to the existing two-factor flow. The device list with one-click revoke shipped in 1.45.0, and a revoked session ends on the server at once; the passkey sign-in itself is the open part.

• Publish MX, SPF, DKIM, DMARC and PTRMailS · days

  The DNS records that make mail arrive and be trusted. The deliverability card shows the state; publishing the records is operator work.

• Rate limits and daily capsMailS · days

  Per-mailbox hourly and daily caps are in the policy, and token buckets guard the send endpoint and the chat tool; the per-account limit on the relay is still to come.

• Single status vocabulary and badge setObservabilityS · daysQ4 2026

  The canonical set of states, the mapping table per source and the one StatusBadge exist. The list endpoints do not yet return the canonical state beside the native one, and the old badges are still in use; that is the open part.

• AI bridge for documents that never leaveDocument StoreM · weekssovereign2027

  Excerpts and citations are redacted by class before they reach a prompt (the PII redactor for personal documents, citation only for bsn, special and secret). Summarise, extract, classify and question answering over a set, and the local-lane refusal by code, are the open part.

• Chunked resumable transfer and Grote Berichten both waysDocument StoreM · weeksQ4 2026

  Grote Berichten publish and fetch with checksum verification and byte-offset restart run on the hub. Chunked, resumable upload and download in the document store itself, so a 1.5 GB file is normal there too, is the open part (the store caps an upload at 50 MB today).

• Data classification labels with enforcementPlatformM · weeks

  Tag every collection field as public, internal, personal, BSN or secret, so the vault, masking, export and retention all key off one label instead of three separate lists. The document store and the vaults already share one class vocabulary (public to secret); applying it to every collection field is the open part.

• Data loss prevention on the classes before anything leavesDocument StoreM · weekssovereignQ4 2026

  Before a share, a delivery, a transfer or a prompt, the content is checked against the document's declared class and the purpose and counterparty, and a mismatch is refused, redacted or logged, so a BSN in a file marked internal never leaves the server. Content checks at upload raise the class, and shares and transfers are gated by class; the check against purpose and counterparty at share, delivery and prompt time, and the NER lane, are the open part.

• Data-subject requests for documents about a personDocument StoreM · weeksQ4 2026

  Listing every document and protocol row about a person works on the API, in chat and over MCP. Erasure has no route yet, and nothing is joined to the vault's request flow, export bundle or one-month clock; that is the open part.

• Malware scanning and content disarm on premiseDocument StoreM · weekssovereignQ4 2026

  An uploaded file is refused outright when its bytes say executable or macro-enabled Office, scanned by a local malware daemon when one is configured, refused rather than accepted unscanned when that daemon cannot answer, and read by the identifier detector so a file carrying a citizen service number is filed under at least the class it demands. Still open: the sandboxed content-disarm rebuild, the quarantine of an infected original, and the same gate on files arriving over file transfer.

• MCP and chat tool set for documents with scoped bridge keysDocument StoreM · weeks2027

  Search, read, put, share, subject and verify tools exist on MCP and in chat. Per-key scopes (tenant, class ceiling, purpose, rate, term), a send tool, and opening restricted classes after the unlock ceremony rather than citing them are the open part.

• One notification busPlatformM · weeks

  Replace the separate toast stacks and ad-hoc mails with one event bus that fans out to in-app, mail, Teams and Signal. The per-user preferences shipped in 1.40.0 and 1.41.0 (pop-ups and action toasts off by default, on per person); the hub is still in-app only, and the fan-out to mail, Teams and Signal is the open part.

• Peppol document exchangeDocument StoreM · weeks2027

  SML and SMP discovery with signature checks and AS4 sending exist on the hub. BIS Billing 3.0 validation against the Dutch rule sets and filing each exchanged document with its receipt are the open part. The Peppol invoicing flow of certified-flow-library becomes the packaged starting point.

• PGP and S/MIME payload protectionDocument StoreM · weeks2027

  OpenPGP encrypt-and-sign and decrypt-and-verify per partner profile run on the hub, so a file handed to a partner's SFTP server stays unreadable there. S/MIME is the open part.

• Prompt-injection hardeningMailM · weekssovereign

  Mail inside an untrusted frame with its closing tag neutralised, no tools during understanding and drafting, and recipients fixed before the model runs are built. The regression suite of known injection payloads run against the verifier is the open part; today one phrase is checked against the guard.

• Replay lineageObservabilityM · weekssovereign

  Reruns link to their parent run and a replayed message counts its replays. Dry runs are not recorded, a run has no kind or sandbox parent, and a message lists a replay count rather than its children with outcome; that is the open part.

• Scenario forecasting and deal coachingNexusM · weeks

  What-if scenarios on the pipeline forecast. The per-deal coaching, the second analysis pass (stakeholders, risks, plan, win probability) and the Monte Carlo forecast shipped as Deal intelligence in 1.49.0; adjusting a deal's probability, value or close date and seeing the band move is the open part.

• Shared timeline component setObservabilityM · weeksQ4 2026

  Timeline, StatusBadge and IdChip ship in the component suite and the transaction timeline is drawn with them. Still open: Waterfall, DurationChip, TokenChip and ExportMenu, and the other pages that show a transaction moving onto the same components.

• Transaction id contractObservabilityM · weeks

  The platform collections carry the trace id and the id chip copies and lands on the timeline. The hub writes no trace id yet on its runs, logs and message rows, and the chip is on two pages rather than every page; that is the open part.

• Transaction searchRobeeflowM · weeks

  One search box over outbox, inbox, runs and logs by correlation id, partner or content, with saved searches and a single timeline per transaction. Search by correlation id and the one timeline per transaction exist (tracking page, timeline); search by partner or content and saved searches are the open part.

• Work log integrationObservabilityM · weekssovereignQ1 2027

  The work log has its API, MCP tool, chat tool and cascade step, and an entry carries the trace from its context. Hub operator actions do not write entries yet and the report does not link an entry to its timeline; that is the open part.

• Finish the FSC interop layerFSCL · a quartersovereign

  The cryptography is right and the request path works: mTLS inway and outway, certificate-bound tokens, SHA3-512 grant hashes over RFC 8785 canonical JSON, detached JWS signatures, and a self-test that drives a token end to end and rejects a tampered one. Since the assessment of 1 October 2026 the front door was reshaped too: the token endpoint takes the client-credentials form, the signing keys are served at the well-known JWKS location, the error codes come from the standard and are checked against its OpenAPI in tests, and the transaction log is written. Left: the peer and service listings of the Manager API, directory federation and the regulated area.

• Hub run recorder joined to the platform trace storeObservabilityL · a quartersovereign

  A hub flow run shows up on the Interactions page as one waterfall beside chat turns and cascades, with each node, send and acknowledgement as a step. The platform side that stores an external run exists and the timeline reads the hub over loopback; the hub does not yet send its runs, so nothing lands on the Interactions page.

• MFT protocols with partner profiles and checkpoint restartDocument StoreL · a quartersovereignQ4 2026

  Partner profiles, SFTP and HTTPS both ways, watched folders, checkpoint restart and a contract gate shipped on the hub in 1.20.0. AS2, OFTP2, the dead-transfer operator queue, a DLP policy per profile and an operator page are the open part. The tested SFTP and Peppol flows of certified-flow-library install against these profiles.

• One vault access layer for all four channelsBastionL · a quartersovereignQ4 2026

  The gate is live for every vault, the platform bridge calls it for chat, MCP and agents, and the document store runs the same layer over files: it checks who is asking and why, masks by field class and writes the protocol and lineage rows. Still open: remote vault nodes behind the same layer.

• The peer-facing Manager APIFSCL · a quartersovereign

  The paths FSC Core requires a Manager to expose to other peers over mTLS, separate from the operator's management plane. Announce, the contract lifecycle of accept, reject and revoke, and the signing keys at the well-known JWKS location are served; the peer and service listings are the open part.

Planned work sized in days or weeks, smallest first.

• Audit reading roomObservabilityS · dayssovereignQ1 2027

  One page for audit exports with days, row counts, verdicts and downloads, lineage verification per day, evidence verification per id, AI Act dossiers per module and attestations. Today all of these are API only.

• Boomi licence optimiserNexusS · daysQ4 2026

  Model the Boomi licence the migrated estate needs (connections by class, trading partners, environments) and show what consolidation, retirement and design choices save, before the customer signs with Boomi. (A13, P2)

• Cascade and hub handoff recordObservabilityS · dayssovereignQ4 2026

  When the hub asks for a cascade it passes the transaction ids and gets the run id back, which it writes on the run and the message; when a cascade sends through the hub the message carries the cascade run id. A cascade that consumed a message can be found from the message and the other way round.

• Conformance evidence packRobeeflowS · days

  Run the loopback harness and the interoperability suite and produce the evidence bundle Logius or a partner asks for during connection tests, as a PDF with the envelopes attached.

• Consumer API documentation from policiesLayer 7S · daysQ1 2027

  Generate consumer-facing documentation per service from the policy itself: how to authenticate, which headers and scopes are required, rate limits, error responses and examples. (D22, P2)

• Decision ledger for AI permissionsObservabilityS · dayssovereignQ4 2026

  Allowed decisions are not recorded and denials land in a JSONL file. Every decision about what an AI may do (custom role, agent manifest, plan limit, autonomy level, kill switch, a person approving or rejecting AI work) becomes a hash-chained row tied to the span it governed, allowed and denied alike, so the question why was the AI allowed to do this has an answer.

• Deployment drift and environment comparisonNexusS · daysQ1 2027

  Compare what is built with what is deployed, per environment: components changed but not deployed, different versions between test and production, extensions that differ, and packages deployed by hand outside the normal path. (B4, P2)

• Exit-readiness assessment for BoomiNexusS · daysQ1 2027

  A fixed-price assessment product: portability score per process, the lock-in hotspots (scripts, platform-specific shapes, process properties, Boomi-only connectors), a target comparison and a cost and timeline range per target. (C2, P1)

• GitLab and Azure DevOps with pull requestsLayer 7S · daysQ1 2027

  Support GitLab and Azure DevOps next to GitHub, commit as the real user instead of a fixed author, and open a pull request with the lint, baseline and risk report attached. (D17, P2)

• Grafana-compatible metrics endpointObservabilityS · days2027

  Both binaries expose a metrics endpoint in Prometheus text with runs, messages, ack latency, dead letters, AI calls, tokens and cost, spool sizes and dropped log entries, plus a shipped dashboard definition, so a customer's Grafana sees the hub.

• Hub run detail as an interactionObservabilityS · dayssovereignQ4 2026

  The hub run page renders the same waterfall as Interactions, with nodes as steps, AI calls nested, sends and acks as steps, and the message, parent run and children in the header. The flow designer's messages panel uses the same component.

• Licence and connection usage analyserNexusS · daysQ1 2027

  Show which licensed connections are used, by which deployed processes, in which environments, and what can be consolidated or retired, with the annual saving. (B7, P2)

• Lineage or nothing, as the law saysObservabilityS · daysQ4 2026

  The accountability law says a model answer whose lineage row cannot be written must not be used; the code spools the row and hands the answer out anyway. Either the code follows the law for the modules that need it, with a strict mode per module, or the law is amended to say a spooled row counts. A decision for a person to sign, then built either way.

• Masked test data generatorBastionS · days2027

  Synthetic BRP, BAG, KVK and WOZ records that pass elfproef and IBAN checks and keep the structure of real messages, labelled as test in every record and protocol row, so integrators and demos never touch real citizens.

• My AI activityObservabilityS · dayssovereignQ1 2027

  Every user gets a page of what the AI did on their behalf and with their data (conversations, tool calls, documents read, runs started, cost), with the same masking as the custody policy. Transparency a user can check for themselves, and the basis for answering a data subject request in minutes.

• Observability health pageObservabilityS · daysQ1 2027

  One page for both binaries shows the logging pipeline queue, dropped and failed counts, span write failures, spool sizes, chain heads and last roots, export state, retention state per class, collector delivery and bridge round trip, each with what to do about it.

• OWASP API Top 10 coverage matrixLayer 7S · daysQ1 2027

  One matrix per service: the ten OWASP API risks against the evidence that covers each, from the policy (baseline controls) and from outside (scanner findings), with gaps marked. (D13, P2)

• Saved viewsObservabilityS · daysQ1 2027

  Save filters, columns, sort and time window on any observability table, per user or shared with the team, with a link and a pin to the dashboard home.

• Security and exposure reviewNexusS · daysQ4 2026

  Review the account for security risk: credentials in plain properties instead of extensions, disabled TLS verification, shared integration users, web services and APIs exposed without authentication, and APIs exposed as MCP endpoints to AI agents. (B6, P1)

• What did the AI do todayObservabilityS · dayssovereignQ1 2027

  The daily digest grows from counts into a narrative with numbers, covering model calls by module and model, cost, active agents, decisions taken and held, hub messages processed with AI, failures, replays, denials and the spool and chain state. It is delivered on the bus and kept as a page with history.

• Academy certification tracksAcademyM · weeks

  Hands-on tracks where the exercises are real Robeeflow flows and Layer 7 policies run in a sandbox tenant, graded automatically.

• Access model for observabilityObservabilityM · weekssovereignQ1 2027

  One role matrix decides who sees spans, lineage, usage, hub logs, message payloads, exports and bundles; payloads are masked by default with the existing masking profiles and a break-glass reveal is protocolled. Collection rules derive from the matrix instead of being set per collection.

• AI-assisted field mappingRobeeflowM · weekssovereign

  Given a sample source and a target message definition, the local model proposes the mapping and the operator confirms field by field.

• API inventory and OpenAPI reconciliationLayer 7M · weeksQ1 2027

  Compare what the gateway exposes (services and resolution paths) with the customer's API specifications and the scanner's discoveries, and list undocumented ("shadow") and retired-but-reachable ("zombie") APIs. (D12, P1)

• Approval and release workflows with second approverDocument StoreM · weeks2027

  Require a release step before a document may be shared or sent, with a second approver for bsn and special-category material and for registered deliveries, time-boxed grants and a rejection path with reasons; the approval is itself a signed, chained event.

• Attachment handlingMailM · weeks

  Persist attachments with size and type limits, block executables and macros, scan when a scanner is installed, show them read-only and never feed them to a model.

• Audit exports and evidence bundles for documentsDocument StoreM · weekssovereign2027

  Hand an auditor or a court one self-contained bundle per period, customer, counterparty or case with the documents or their hashes, chain segments, signed and timestamped day roots, protocol rows, delivery receipts, scan verdicts and an offline verifier. Uses the exporter of the audit-chain daily export and the spectre-evidence archive.

• Auditor exports on every viewObservabilityM · weeksQ1 2027

  JSON and CSV on every list and detail view, PDF on every report, one export shape that carries the same ids and hashes the screen shows, and a record of who exported what.

• Boomi account connector and inventoryNexusM · weeksQ4 2026

  Read a Boomi account through the Platform API (read-only) or from a component export: folders, components of every type, versions, packaged components, deployments, environments and runtimes. This is the source side of the migration tool, which today rejects any source but Adeptia with "Boomi is planned as the next source". (B1, P1)

• Boomi health check with a house-style reportNexusM · weeksQ4 2026

  Score every Boomi process for quality and risk with explicit rules, give the account a grade, and produce the same kind of Word report we now deliver for Layer 7: management summary, findings per area, an appendix per process, worst first. (B2, P1)

• Boomi Platform API push with dry run and rollbackNexusM · weeksQ4 2026

  Create the generated components directly in the customer's Boomi account through the Boomi Platform API, in a dedicated folder per wave, with a dry run first and a rollback that removes exactly what was created. This is the accelerator the estimate assumes. (A2, P1)

• Both products on one notification busObservabilityM · weeks2027

  Puts the hub's announcements, delivery and certificate alerts and the platform's bell, mail and Discord digest on notification-bus, with both binaries publishing to it and every notification opening the timeline it refers to.

• Calibrated estimate in hours and moneyNexusM · weeksQ1 2027

  Convert effort units into consultant hours and euros with a calibration that learns from completed waves, and show the estimate as a range with a confidence band instead of one number. (A10, P2)

• Certified flow libraryRobeeflowM · weeks

  Tested flows for Digikoppeling ebMS2, WUS, REST-API, Peppol invoicing and SFTP exchange as configuration bundles that install in one click.

• Cited answers onlyPlatformM · weekssovereign

  Retrieval answers must cite indexed documents; a sentence the verifier cannot ground in a citation is shown as unverified.

• Compliance pack: DORA, ISO 27001 and PCI DSSLayer 7M · weeksQ2 2027

  Add DORA, ISO 27001 Annex A and PCI DSS 4.0 to the existing BIO, NIS2 and NCSC views, with an auditor-ready evidence export in the house style. (D14, P2)

• Connector as a two-way MFT edge agentDocument StoreM · weekssovereignQ4 2026

  The connector on the customer's network grows from inbound pickup into a two-way edge agent with outbound drops to partner folders and SFTP, hashed chunked transfer to the hub, files beyond 16 MB, schedules and quiet hours, an on-agent pre-scan and a status page, while holding no data at rest beyond its queue.

• Connector fleet operationsRobeeflowM · weeks

  Bulk upgrade with canary rollout, remote configuration diff and a fleet health map for the on-premise connectors.

• Continuous model evaluationPlatformM · weeks

  The benchmark harness as a product page: golden sets per module, nightly regression runs and a promotion button that only unlocks when a candidate beats the incumbent.

• Cost per outcomeObservabilityM · weekssovereign2027

  See what the AI cost per message processed, per cascade report, per approved work output, per mail sent, per partner and per customer, and where spend does not turn into outcomes. The report inference-scheduler promises, built on the joined records.

• Cross-platform regression harnessNexusM · weeksQ1 2027

  Replay the same inputs through the source and the target platform and compare the outputs, for any pair of platforms. This is the general form of the Adeptia mapping tester (A5). (C6, P1)

• Customer-held key optionBastionM · weekssovereign2027

  A municipality or company supplies the key that wraps its vault from its own KMS, HSM or a split-knowledge ceremony, so the operator can never decrypt that vault alone. The vault stays sealed at boot until the customer unseals it.

• Cut-over and parallel-run plannerNexusM · weeksQ2 2027

  Plan the switch per wave: which Adeptia triggers to stop, which Boomi schedules to start, in what order, the freeze window, the parallel-run checks and the rollback. (A12, P2)

• Dependency and impact graphNexusM · weeksQ1 2027

  Show how processes, sub-processes, connections, operations, profiles and maps depend on each other, answer "what breaks if I change this connection", and find orphaned components. (B3, P1)

• Directory federation and peer discoveryFSCM · weeks

  List in and read from the public FSC directory, discover peers and their services, and propose contracts from the discovered catalogue.

• Encapsulated assertion libraryLayer 7M · weeksQ1 2027

  Grow the rollout templates from three (audit, security headers, server-header removal) to a versioned library of fifteen: JWT validation, OAuth scopes, CORS, rate limiting, threat protection, structured logging, error envelope and more. (D19, P2)

• Environment extensions and connection packNexusM · weeksQ1 2027

  Generate the Boomi connections, operations and environment extensions for every environment (development, test, acceptance, production) from the 30 databases, 8 file hosts, 5 accounts and 2 keystores the tool already inventories. (A6, P2)

• Error-to-assertion root causeLayer 7M · weeksQ2 2027

  When a request fails, point to the assertion and the line in the policy that caused it and suggest the fix, using the runtime record, the simulator and the assertion explanations. (D6, P2)

• Evidence attestationsObservabilityM · weekssovereignQ1 2027

  A signed statement per message, run or day names the rows, hashes and chain heads it covers and the key and time that signed it; the lineage, audit and evidence roots of a day combine into one platform root, with a verify endpoint and a page.

• Exact tokens and budgets per workspaceObservabilityM · weeksQ1 2027

  Token counts are estimates and nothing knows the customer workspace. Read the exact counts the providers return (Ollama included), add the workspace to every usage, span and lineage row, count image generation and embeddings too, and set budgets per user, per feature and per workspace with a warning before the limit and a hold at it. Local GPU time is counted as well, so a customer engagement shows what its AI work cost, hosted or not.

• Exposure graphSentinelM · weeks

  Link Spectre CVE findings to Sentinel projects and assets, score exposure, and raise tickets automatically.

• Inference scheduler and budgetsPlatformM · weeks

  Priority lanes, queueing and per-module token budgets on the single GPU, with a cost-per-outcome report, so a background job and a live chat no longer compete without rules.

• Lineage rows for hub AI nodesObservabilityM · weekssovereign

  The hub's AI node calls the platform's governed model API under the hub's manifest, so every hub inference gets a lineage row, a span and a usage entry with the execution, node and message ids attached. Not started: the hub's AI node is still a mock and calls no model.

• Live tailObservabilityM · weeks2027

  A live stream of timeline events filtered by id, flow, partner or model, so a run detail and a transaction page update while the run is in progress. The same stream feeds the alert rules.

• Map translation engineNexusM · weeksQ2 2027

  Translate Boomi map functions and Adeptia mapping rules into a neutral rule form and from there into XSLT 3, DataWeave, JSONata or the Robeeflow mapping format. (C7, P2)

• Mobile app shell with offline approvalsDesign systemM · weeks

  A progressive web app for approvals, alerts and work review that queues actions while offline and syncs when back.

• Model comparison over real trafficObservabilityM · weekssovereign2027

  Compare two models on the same lane over a period on latency, tokens, cost, error and fallback rate and outcome signals such as review approvals, mail verdicts and hub node success, side by side with the bench scores. The traffic-side counterpart of continuous-model-evaluation.

• Model runtime telemetryObservabilityM · weeksQ1 2027

  Watch the local models as a fleet (which model is loaded where, GPU memory, a model that slipped onto the CPU, queue depth and wait time per lane, tokens per second, load and unload events) with alerts on a model silently running on the CPU or a queue that keeps growing. Today a slow answer cannot be told apart from a busy GPU.

• Multi-gateway sync with drift alertsLayer 7M · weeksQ4 2026

  Scheduled sync per workspace and per gateway, instead of one global sync into the default workspace, with a notification when production drifts from what was approved. (D4, P1)

• OpenTelemetry export to a customer's collectorObservabilityM · weeks2027

  Traces, logs and metrics from both binaries go to the customer's own collector in OTLP with W3C propagation and shared resource attributes, per tenant, with a page that shows delivery status.

• Organisation-wide search with class-aware resultsDocument StoreM · weekssovereign2027

  Full-text and semantic search over document content and metadata on the local embedding fleet, filtered by your purpose and class ceiling before ranking, with restricted hits shown as citations without snippets and every search recorded as a read.

• Partner SLAs and scorecardsRobeeflowM · weeks

  Delivery and acknowledgement targets per agreement, alerts on breach, and a monthly partner report from the tracking data that already exists.

• Per-agent reportObservabilityM · weekssovereignQ1 2027

  For any agent and manifest, see calls, tools used, denials, work outputs and XP, decisions taken, cost, hub messages processed and incidents, with the manifest's permitted scope beside what the agent actually did.

• Per-flow and per-cascade reportObservabilityM · weeksQ1 2027

  For a flow or cascade and period, see runs, success rate, p50 and p95 duration, the failing nodes or steps ranked, AI cost per run, alerts and replays, with a partner breakdown for flows and report and XP history for cascades.

• Per-message reportObservabilityM · weekssovereignQ1 2027

  One document per message id with parties and agreement, envelope facts, delivery attempts, the acknowledgement with proof, flow runs and nodes, AI calls with model, manifest and hashes, alerts, replays, cascade follow-ups, archive location, audit rows and chain verification. Export it as JSON or PDF.

• Per-model reportObservabilityM · weeksQ1 2027

  For any model and period, see calls, latency percentiles, tokens, cost, error and fallback rate, the lanes, agents and hub flows that used it, and the bench results for the same model next to real traffic, with the trend against the previous period. Complements the golden sets of continuous-model-evaluation.

• Performance and cost lensLayer 7M · weeksH2 2027

  Estimate the processing cost of each policy (XSLT, schema validation, cryptography, external calls) and, with runtime data, find the policies that cost the most latency and capacity. (D24, P3)

• Plain-language process explanation and documentationNexusM · weeksQ2 2027

  Explain every Boomi process shape by shape in plain language, the way the Layer 7 policy viewer explains assertions, and generate up-to-date process documentation for the customer. (B8, P2)

• Policy builder from a descriptionLayer 7M · weeksQ1 2027

  Describe an API in words or give an OpenAPI file, and get a policy draft built from the right blueprint with authentication, validation, rate limiting, routing and error handling, ready for review in the designer. (D9, P2)

• Policy-as-code syncLayer 7M · weeks

  Import and export policies as files with a diff view and the existing lint and security analysis as the gate, so policies live in version control and are reviewed like code.

• Portable sealed vault bundlesBastionM · weekssovereignQ4 2026

  Export a whole vault as one sealed bundle, with the ciphertext, the key envelopes wrapped for the destination, the classification schema, the registered purposes, the protocol history and a signed manifest, so a vault can move to another host or an air-gapped machine without ever being decrypted in transit. The export is itself a protocolled event and a moved vault keeps its identity and its protocol chain.

• Prompt and response custodyObservabilityM · weeksQ4 2026

  Prompt and response text is kept in spans without end and without masking, while the lineage ledger keeps hashes only and the audit log keeps chat bodies. One custody policy per module decides what is kept as text, for how long, masked how (personal data, secrets, customer names) and who may read it, with superusers only on the collection itself. Text past its term is dropped and the hash stays, so lineage still proves what was asked.

• Quality signals on AI outputObservabilityM · weekssovereignQ1 2027

  Tie what people do with AI output back to the span that made it (approved, edited and by how much, rejected, regenerated, thumbs up or down in chat, a description corrected by hand), so every model and prompt gets a quality score from real use, not only from the bench. Feeds the model comparison of obs-22 and the drift clustering of obs-24.

• Queryable OTel log storeObservabilityM · weeksQ1 2027

  OTel records land in a collection with the trace id and attributes indexed, and the OTel Logs page gains search by id, attribute and severity beside the day file download, so hub events and cascade steps become findable.

• Replay against recorded trafficLayer 7M · weeks

  Record real request corpora and simulate a policy change against them before it goes live, with a before-and-after report.

• Replay an AI callObservabilityM · weekssovereignQ1 2027

  Open any model call from its span and run it again with the same input on the same or another model, side by side, within the custody policy of obs-37. For finding out why an answer was wrong, and whether a newer local model would have done better on real work.

• Runtime analytics from execution recordsNexusM · weeksQ2 2027

  Read execution history (counts, durations, errors, document volumes) per process and runtime, find error hotspots, slow processes and processes that never run. (B5, P2)

• Secure mail and NEN 7516-conformant deliveryDocument StoreM · weeks2027

  When the recipient is only an e-mail address, send a notification with a link into a share or the portal, never the file, with recipient authentication, expiry, revocation and read receipts that meet the 7516 requirements for health and other sensitive information.

• SLA breach reports per partnerObservabilityM · weekssovereign2027

  Bind service levels to agreements and customers, measure acknowledgement latency, delivery success, availability and incidents from the outbox and inbox, and get a monthly report per partner with each breach linked to its messages.

• Sovereign speechPlatformM · weekssovereign

  Local speech-to-text and text-to-speech for Buddy and chat, so meetings and dictation stay on the machine like everything else.

• Stakeholder portal for architects and auditorsLayer 7M · weeksQ2 2027

  A read-only view for people outside the gateway team (architects, security officers, auditors) with the API inventory, health, compliance and reports, without Policy Manager access. (D21, P2)

• Steward dashboards for documents and transfersDocument StoreM · weeks2027

  One page shows sealed and unsealed tenants with key versions, chain and root health per day, documents past retention or under hold, quarantined files, expiring shares, transfers by partner with success rates and the dead queue, delivery receipts outstanding and certificates about to expire.

• Templates and document generation into the storeDocument StoreM · weeks2027

  Reports, decisions, tender answers, invoices and letters the platform generates are born inside the store with metadata, class, subject link, hash and an optional seal, as PDF/A or DOCX, instead of landing in a text field or a loose file.

• Tender bid copilotTendersM · weekssovereign

  Draft questionnaire answers from past bids and the qualification library with citations to the source bid, on the local model, inside the Tenders pipeline.

• Trading partner portabilityNexusM · weeksQ2 2027

  Move B2B and EDI trading partners out of Boomi to Robeeflow agreements or another B2B gateway, with the partner communication pack from A8. (C8, P2)

• Transaction search across both productsObservabilityM · weeksQ1 2027

  Extends transaction-search from the hub's four collections to spans, lineage, audit rows and events on the platform, by any id, partner, service, customer, flow, model, agent or free text, with typed results that jump to the timeline.

• Verified gateway lab and publish certificationLayer 7M · weeksQ4 2026

  Run a real Layer 7 gateway (the Broadcom container image with a development licence) in our test environment and certify every write path against it: publish, sync and rollout bundles. Today publishing "has not been exercised against live hardware". (D1, P1)

• What the AI readObservabilityM · weekssovereignQ1 2027

  A read ledger for the AI. Every document, vault record, memory, database row set and web page a model was given or a tool fetched for it is recorded against the span that used it, by reference and hash, never by copy. Vault reads and Spectre fetches already do this; documents, memory, Layer 7 policies and migration data do not. It answers the question an auditor and a data subject both ask, which of my data did the AI see, and when.

Planned work the size of a quarter. These need a design before a date.

• Air-gapped installerOperationsL · a quartersovereign

  One bundle with binaries, models, PocketBase and licence that installs on a machine with no internet. The sovereignty claim made literal.

• Alert rules on the unified streamObservabilityL · a quarter2027

  Write alert rules as data over timeline events, such as dead letters per agreement, failed runs of a flow, AI error rate, lineage spool growth, dropped log entries, certificate expiry, SLA breach or cost above budget, with severity, routing and cool-down. Every alert carries the transaction id that opens its timeline.

• Body-aware simulatorLayer 7L · a quarterQ2 2027

  Make the request simulator evaluate message bodies: JSON and XML payloads, XPath and JSONPath conditions, schema validation and size limits, which it now reports as unknown. (D15, P2)

• Boomi to Azure Integration ServicesNexusL · a quarterQ2 2027

  Generate Logic Apps Standard workflows, maps (XSLT or Data Mapper), Service Bus queues and API Management definitions from the C1 model, for customers standardising on Microsoft. (C4, P2)

• Boomi to MuleSoft and to open sourceNexusL · a quarterH2 2027

  Further targets on the same model: Mule 4 applications with DataWeave, and Apache Camel routes for customers who want an open-source runtime (the OpenTunnel target already declared in the concept list). (C5, P3)

• Boomi to RobeeflowRobeeflowL · a quarterQ2 2027

  Move Boomi integrations onto our own Robeeflow hub: processes become Robeeflow flows, maps become Robeeflow mappings, trading partners become agreements, with Digikoppeling and AS4 available for Dutch government exchanges. (C3, P1)

• Designer coverage from 43 to 120 assertionsLayer 7L · a quarterQ2 2027

  Make many more assertions buildable with typed fields. Today 43 of the 201 documented assertions can be built; the rest can only be explained or pasted as raw XML. (D10, P2)

• Distribution via FSC and Digikoppeling under contractsBastionL · a quartersovereign2027

  Vault data leaves the hub only under an FSC contract or Digikoppeling agreement that names the counterparty, the vault, the purpose, the field list and the term, enforced by the Inway and Outway or the message profile and protocolled on every delivery.

• Drift and error clusteringObservabilityL · a quarter2027

  Errors from spans, hub runs, outbox failures and log messages are grouped by fingerprint into incidents with first seen, last seen, count and affected transactions, and drift in latency, tokens, ack rate and error rate per model, flow and partner surfaces as an incident before a customer notices.

• E-signature and sealing with PAdES, wallet QES and organisation sealsDocument StoreL · a quartersovereign2027

  Ask one or several people to sign in order or in parallel, with advanced signatures in the portal, qualified signatures through a Dutch trust service or the signer's EUDI wallet, and organisation seals with the customer's PKIoverheid certificate, all as PAdES or XAdES with a timestamp that keeps the signature valid after the certificate expires.

• EDI trading partner migrationNexusL · a quarterQ1 2027

  Create the Boomi Trading Partner components, processing rules and communication settings for the EDI estate (125 partners, 176 active relationships, 14 message types) and give the customer a partner-by-partner onboarding plan. (A8, P1)

• EDIFACT and Peppol BIS validation nodesRobeeflowL · a quarter

  Parse and serialise EDIFACT and X12, and validate Peppol BIS 3 documents, next to the existing Validate and Transform nodes.

• Enforcement adaptersLayer 7L · a quarter

  Export a policy to Envoy, OPA or the FSC inway configuration, so Layer 7 is where policy is designed and the runtimes follow.

• EUDI wallet relying party and attestation issuanceBastionL · a quarter2027

  Citizens and companies prove attributes from their wallet to the hub over OpenID4VP, the hub registers as relying party with its access certificate, and a vault can issue attestations over OpenID4VCI for facts the customer is the authentic source of.

• Evidence bundleObservabilityL · a quartersovereignQ1 2027

  A signed zip per message, run or period with the rows, archive documents, spans, lineage rows, audit rows, day roots and a chain verification report, laid out with a hashed manifest so an auditor can verify it offline with a small tool.

• FSC Regulated AreaFSCL · a quarter

  The extension that binds participants inside a regulated area. who regulates, who takes part, the obligations that attach, and onboarding, revocation and supervision. Twenty-eight mandatory provisions, none of which bind us until we join an area, which is why it comes last.

• Full-configuration pull and bundle publishLayer 7L · a quarterQ1 2027

  Read and write everything a policy depends on, not only policies: services, encapsulated assertion configurations, cluster properties, listen ports, certificates (public parts), secure password names, JDBC connections and identity providers. Publish as one bundle with a preview and an automatic snapshot for rollback. (D2, P1)

• Hub federationRobeeflowL · a quarter

  Two hubs exchanging configuration bundles and forwarding outboxes, so acceptance and production, or two agencies, can share agreements without sharing a database.

• OOTS evidence provider and requesterBastionL · a quartersovereign2027

  The hub joins the Once-Only Technical System through its AS4 access point, answering evidence queries from a vault behind a Preview Space where the citizen approves before anything is sent, and requesting evidence through the Evidence Broker.

• Per-tenant envelope encryptionPlatformL · a quarter

  One data key per customer, wrapped by the platform key, so deleting a customer is deleting a key and several agencies can share one server.

• Platform-neutral integration modelNexusL · a quarterQ1 2027

  One canonical model for flows, steps, maps, schemas, endpoints, schedules and partners that both the Adeptia and the Boomi reader write into, and every target generator reads from. (C1, P1)

• Process and shape generator from Adeptia flowsNexusL · a quarterQ1 2027

  Translate each Adeptia flow (its BPMN, activities, gateways and context variables) into a Boomi Process component with the matching shapes: start, connector calls, maps, decisions, branches, try/catch, process properties and sub-process calls. (A3, P1)

• Promotion pipeline with approvalsLayer 7L · a quarterQ1 2027

  Promote a change from development to test, acceptance and production gateways, with environment-specific values, quality gates that must pass, and an approval at each step recorded in the governance model. (D3, P1)

• Qualified timestamps and long-term preservationDocument StoreL · a quartersovereign2027

  Daily roots and signatures are anchored with RFC 3161 timestamps and re-stamped before algorithms weaken, every version keeps a write-once copy, and a file can be migrated to PDF/A with the original and both hashes linked, so proof survives for decades under the customer's own control.

• Recipient portal for citizens and companiesDocument StoreL · a quartersovereign2027

  A Doccle-style inbox on your own server where an organisation delivers invoices, decisions and letters, and the recipient logs in with DigiD, eHerkenning or the EUDI wallet, reads, signs, pays and decides with a consent record who else may see a document.

• Registered delivery with evidence (ERDS)Document StoreL · a quartersovereign2027

  For a decision, a summons or a contract the store produces the registered-delivery evidence set, from submission acceptance to content handover with the recipient's identification, each signed, timestamped and chained, so the sender holds a receipt bundle a court accepts. The hub's AS4 receipts become the relay evidence.

• Remote vault nodes that connect backBastionL · a quartersovereign2027

  Install a vault on a customer's own server or a second hub as a vault node that registers with the main platform over FSC or Digikoppeling with mutual authentication. The platform then reaches it through the same access layer and the same four channels, the data stays on the node, and the node keeps its own keys and protocol chain.

• Retention aligned with the seven-year termObservabilityL · a quartersovereignQ4 2026

  One retention registry by data class, so an ebMS exchange and everything it touched keeps for 2555 days by default in hot, warm and archive tiers, every janitor reads the same registry, every deletion is an audit event and any record shows what applies to it and when it leaves. The registry and defaults land first; tiering and protocolled deletion follow in Q1 2027.

• Runtime telemetry linked to policiesLayer 7L · a quarterQ1 2027

  Ingest gateway runtime data (audit records, service metrics, error counts) and attach it to the services and assertions they belong to, so every policy shows how it behaves in production next to how it is written. (D5, P1)

• Script converter for Adeptia services and custom classesNexusL · a quarterQ1 2027

  Convert the scripted services (122 in the reference estate, 54 of them calling compiled custom classes) into Boomi Groovy with an AI-assisted rewrite, a test harness and a clear list of what still needs a human. (A4, P1)

• Sealed document bundles and remote document nodesDocument StoreL · a quartersovereign2027

  Export a case, a customer or a citizen's inbox as one sealed bundle with ciphertext, re-wrapped key envelopes, metadata, purposes, protocol history and a signed manifest, and install it on another host as a document node that keeps its chain and registers back with the platform over FSC or Digikoppeling. The documents part of the vault-26 bundle format.

• ZGW Documenten API facadeDocument StoreL · a quarter2027

  A municipality's case system, Open Zaak or a ZDS 1.2 bridge uses the store as its document management system through the VNG Documenten API, with versions, lock and unlock, chunked upload, links to cases and the confidentiality marking mapped onto the six classes.

Roadmap items that have landed, newest first. Each one is also described under Features.

• Audit log that tells the truthObservabilityS · days

  The HTTP audit log records every request as status 200, so a request the role guard refused looks like a success, and requests without a user, such as cascades and schedules, are skipped. Record the real status, the acting system identity for background work and the guard's verdict, and remove the unused tool-call logger or wire it in.

  Shipped 23 Oct 2026 in 1.75.0 · see it under Features
• Every AI tool call inside its traceObservabilityM · weekssovereign

  Tool calls a chat turn makes today never become spans of that turn, the tool invocation rows carry no trace id, and the MCP bridge and the agent query endpoint record nothing at all. Every tool call on every channel (chat, MCP, AI-to-AI, cascades) becomes a span of the conversation or run that asked for it, with the tool, the caller, the agent, the duration, the result size and the guard's verdict, so one click goes from a chat message to each model call and each tool it made.

  Shipped 23 Oct 2026 in 1.75.0 · see it under Features
• History for AI batch runsObservabilityS · days

  Long AI runs, such as writing a description for every policy of a gateway, keep only their last state, and a restart wipes the story. Each run gets a record with who started it, the model, the start and end, every item with its outcome, duration and span, the failures with their reason, and the restarts, kept for as long as the result it produced is in use.

  Shipped 23 Oct 2026 in 1.75.0 · see it under Features
• Migrations into Layer 7 from MuleSoft and AxwayLayer 7L · a quarter

  Import MuleSoft and Axway API configurations and convert them into Layer 7 policies, scored and explained like any other policy. Planned for Q4 2026. (D20, P1)

  Shipped 22 Oct 2026 in 1.71.0 · see it under Features
• Trigger and schedule converterNexusS · days

  Turn the 103 scheduled Adeptia triggers into Boomi process schedules and the file and database events into listener or polling patterns, keeping the timing the business relies on. (A7, P2)

  Shipped 22 Oct 2026 in 1.72.0 · see it under Features
• Custom rolesPlatformM · weeks

  Admin-defined roles that give an account only the tools ticked for it (Layer 7, Migration, Tenders, Bastion, MEDDPICC, AI chat), refused by the server everywhere else, in the API, the chat tools and the Bastion vaults, where the account acts as a non-admin member. The counterpart of the roles that only grant.

  Shipped 21 Oct 2026 in 1.69.0 · see it under Features
• Live Broadcom documentation refreshLayer 7S · days

  Keep the assertion catalogue current with Broadcom's documentation automatically: re-extract from techdocs on a schedule and per gateway version, show what changed, and have a person approve before it goes live. (D7, P1)

  Shipped 21 Oct 2026 in 1.68.0 · see it under Features
• Mapping equivalence testerNexusM · weeks

  Prove that a migrated mapping produces the same output as the Adeptia original: run the Adeptia XSLT and the generated Boomi map on the same sample documents and show the differences field by field. (A5, P1)

  Shipped 20 Oct 2026 in 1.67.0 · see it under Features
• AI policy reviewer with patch proposalsLayer 7M · weeks

  Our own model reviews a policy with full context (tree, health and security findings in the workspace, the assertion catalogue, the shared encapsulated assertions) and proposes small patches as structured edits. Each is applied to a copy and judged again by the same analysis, regression cases and standard requests; only patches that fix something and break nothing are shown, with the scores before and after, what changes for callers and the exact XML lines. A person approves; approval writes the next version, never to a gateway. (D8, P1)

  Shipped 19 Oct 2026 in 1.57.0 · see it under Features
• Boomi profile builder from Adeptia schemasNexusM · weeks

  Every Adeptia schema as the Boomi profile of its kind (XML, flat file, database, JSON and EDI on its standard) with stable element keys, and the generated maps written against those keys, so a map whose rules resolve imports without re-pointing a field. Profiles that need a person say why. (A1, P1)

  Shipped 19 Oct 2026 in 1.65.0 · see it under Features
• Certificate and secret expiry radarLayer 7S · days

  Every certificate a gateway workspace holds (from bundles or uploaded as PEM or DER, public certificates only) with its expiry and level (expired, 7, 30, 90 days, fine), matched by name, common name or serial to the policies that reference it and the services that reach them; referenced certificates not held yet; stored passwords with where they are used. A daily alert fires once when a certificate reaches each threshold and when it expires. Live pull from the gateway follows with D2. (D11, P1)

  Shipped 19 Oct 2026 in 1.59.0 · see it under Features
• Change risk score per publishLayer 7S · days

  Every change scored 0-100 with its reasons before it is published: services reached through fragments and encapsulated assertions, authentication, TLS, routing, threat protection or custom code touched, size and removals, fall in security or health, regression coverage, and requests that now fail or now get through. Shown in the publish dialog, on each AI suggestion and against the previous version on the policy page; input for approvals (D3). (D16, P1)

  Shipped 19 Oct 2026 in 1.60.0 · see it under Features
• Decommission workflow for dead flowsNexusS · days

  Every dead-flow candidate with the evidence an owner needs (triggers and their state, callers, errors, connections, effort, wave), a named business owner and a decision of migrate, retire or park, recorded with who and when. Each decision recomputes the scope: effort retired and parked, the waves without those flows, and the databases and hosts no remaining flow uses, which need no Boomi connection. (A9, P1)

  Shipped 19 Oct 2026 in 1.58.0 · see it under Features
• Full chat and MCP coverage for Layer 7Layer 7S · days

  Every Layer 7 page reachable from chat and MCP: overview, security and health of one policy in context, diff, simulation, the health check report and sync drift, next to workspaces, capabilities, policy, relationships and the guarded encapsulated-assertion rollout. Publishing stays with a person, because it needs the gateway password with each request. (D23, P1)

  Shipped 19 Oct 2026 in 1.55.0 · see it under Features
• Migration cockpit and weekly status reportNexusM · weeks

  Every flow through its life cycle (analysed, generated, built, tested, accepted, cut over) kept as events with who and when, blockers with their reason, a target date per wave; progress as earned effort, a weekly burndown, the pace of the last four weeks and a forecast per wave (on track, at risk, late); and the weekly status report in the house style for the steering group, downloaded or mailed every week. (A11, P1)

  Shipped 19 Oct 2026 in 1.64.0 · see it under Features
• Migration tools in chat and MCPNexusS · days

  The migration tool on all four channels: imports, readiness, flows with their Boomi shapes, mappings and the wave plan as chat and MCP tools over the same model as the pages, read-only and without the names of people in the export. The guarded generate and push tools follow with the Boomi push (A2). (A14, P1)

  Shipped 19 Oct 2026 in 1.54.0 · see it under Features
• Scheduled health check as a managed serviceLayer 7S · days

  Per workspace on a day of the month the health check runs on its own, compares itself with the month before and mails the Word report with a trend chapter: health and compliance with their change and a chart, new and resolved findings, certificates within 90 days of expiry and policies changed on the gateway. Every month is kept with its report; recipients and sending stay with a person. (D18, P1)

  Shipped 19 Oct 2026 in 1.63.0 · see it under Features
• AS4 message service handler checked against the standardRobeeflowL · a quartersovereign

  The hub's ebMS 3.0 AS4 handler built out to the OASIS AS4 profile and the EU eDelivery AS4 profiles (1.15 and 2.0), with Peppol AS4 2.0 and a Digikoppeling-identity variant as usage profiles. Processing modes under the standard's parameter names, a check per agreement with the clause behind every finding, signature coverage and algorithm enforcement, Ed25519 and X25519 for eDelivery 2.0, the pull exchange pattern on both sides, callback receipts, several payloads, the test service, the full error table. Proof against another implementation (Holodeck B2B in robeeflow/interop) is the step that remains.

  Shipped 17 Oct 2026 in 1.51.0 · see it under Features
• Deal intelligenceNexusM · weekssovereign

  MEDDPICC scoring followed by a second pass on the reasoning lane for stakeholders, risks, a prioritised plan, stage, a blended win probability and a champion test; notes added later re-score the deal and a history shows what moved; pipeline insights for the week and a Monte Carlo forecast beside it, as a Nexus page, in chat and over MCP.

  Shipped 16 Oct 2026 in 1.49.0 · see it under Features
• Page access per rolePlatformS · days

  One matrix of dashboard pages against the account roles; an unticked page leaves the menu and answers with a notice when opened by address, for administrators by the role on their account too. Visibility only; the API behind a page keeps its own guards.

  Shipped 16 Oct 2026 in 1.48.0 · see it under Features
• Gateway health report per policyLayer 7S · days

  The gateway health check report carries an appendix per policy with its grade, the controls it fails, the improvement and the tip for each, and the line inside the policy where the finding sits.

  Shipped 15 Oct 2026 in 1.42.0 · see it under Features
• Graphman bundle importLayer 7S · days

  A Graphman, GMU or Restman bundle of a customer gateway is dropped on the workspace page and becomes policies, services, encapsulated assertions, listeners and cluster properties, the same path the command line took.

  Shipped 15 Oct 2026 in 1.42.0 · see it under Features
• Resolved routing mapLayer 7M · weeks

  Route targets written as context variables and cluster properties are resolved through the bundle's properties and the policy's own assignments, hosts that resolve alike collapse into one node, and what cannot be resolved says so instead of reading as a template.

  Shipped 15 Oct 2026 in 1.42.0 · see it under Features
• Security analysis in policy contextLayer 7M · weekssovereign

  A policy is graded with what reaches it through Include fragments, encapsulated assertions and the global policies, and with the listeners of the gateway, so a service whose TLS and authentication sit in a shared fragment is no longer marked as missing them.

  Shipped 15 Oct 2026 in 1.43.0 · see it under Features
• Server-held vault devicesSentinelM · weekssovereign

  Remembering a device for the personal vault keeps a random token in a cookie the page cannot read and the vault key wrapped under the platform key on the server, beside the device name and expiry the profile lists and revokes. Passphrases become keys with scrypt and a per-account salt, and existing vaults move over on their first unseal.

  Shipped 15 Oct 2026 in 1.47.0 · see it under Features
• Shared encapsulated-assertion rolloutLayer 7M · weekssovereign

  An audit, security-headers or remove-server-headers fragment is written once as an encapsulated assertion and inserted at the top of a chosen set of services, previewed as a diff and filed as a Restman bundle in the customer's dossier; the preview grades the result before anything is applied. On the page, in chat and over MCP.

  Shipped 15 Oct 2026 in 1.44.0 · see it under Features
• FSC Logging on the audit chain we already haveFSCM · weeks

  The transaction log is written before a call goes through, an unlogged call is denied, the records go onto the hash-chained audit files the platform already writes, and a peer reads back its own records. Required rather than optional inside the Digikoppeling REST profile. Retention of the log records follows the platform retention service and is not yet configured per contract.

  Shipped 1 Oct 2026 in 1.30.0 · see it under Features
• Pass the official conformance suiteFSCM · weekssovereign

  A local certificate authority and a two-node federation on one machine, the Logius compliance tester run from a script rather than a pipeline, and a stored report saying which of the standard's mandatory provisions pass and which fail. Four of the five automated tests pass; the two interactive tests and the diff against the previous run are still done by hand. No PKIoverheid certificate is needed for this; a test authority is enough.

  Shipped 1 Oct 2026 in 1.29.0 · see it under Features
• Token issuance the way the standard asksFSCM · weekssovereign

  Access tokens obtained through the OAuth2 client-credentials flow, carrying the grant hash in the scope field and the peer id as the client, authorised against that specific grant on that specific contract rather than by service name, with the error responses RFC 6749 requires. This is the first request of any conformance run.

  Shipped 1 Oct 2026 · see it under Features
• BAG connectorBastionM · weeks

  Address and building lookups through the BAG API within Kadaster's published limits, honoured before the call rather than after a refusal, caching only for freshness and never as a second register. Addresses link to vault records by BAG identifier instead of free text.

  Shipped 28 Sept 2026 in 1.20.0 · see it under Features
• Breach detection and alertingBastionM · weeks

  Seven rules over the access record, from bulk reads and off-hours reveals to failed decrypts, break-glass and a broken chain, raise an alert and a notification, and the serious ones open an incident that carries the 72-hour clock from the moment awareness began. A rule counts rows and hashes and never names a person.

  Shipped 28 Sept 2026 in 1.20.0 · see it under Features
• Content-addressed document store with a signed daily rootDocument StoreM · weekssovereign

  Every file you put in the store is hashed on arrival, kept once by that hash and sealed into a per-day chain whose root carries the platform HMAC, so an auditor verifies documents, audit rows and vault reads with one verifier. Reuses the evidence chain of spectre-evidence. A public-key signature beside the HMAC is not yet written.

  Shipped 28 Sept 2026 in 1.20.0 · see it under Features
• DPIA generatorBastionM · weeks

  From the vault configuration the product drafts the data protection impact assessment, with the three mandatory triggers read from the configuration rather than asked of anyone, the mitigations in force listed with links to their evidence, and the whole versioned and signed beside the register of processing activities. It stays a draft until a person signs it.

  Shipped 28 Sept 2026 in 1.20.0 · see it under Features
• Field-level classification schema per vaultBastionM · weeks

  Every field of every vault carries a class (public, internal, personal, BSN, special category, secret) that decides masking, prompt access and export, and a field the schema does not name fails the read closed instead of passing as harmless.

  Shipped 28 Sept 2026 in 1.20.0 · see it under Features
• Governed share links with recipients, expiry, limits, view-only and watermarkDocument StoreM · weekssovereign

  Share a document with a named recipient under a purpose, an expiry, a download limit and an optional view-only mode; a share link lands on a page that names the document before anything is served. The store keeps only a keyed hash of the token, so a lost link is reissued and never recovered, revocation is immediate, and every open and every refusal writes a row instead of bumping a counter. The watermark travels as a response header; stamping it into the file is not built.

  Shipped 28 Sept 2026 in 1.20.0 · see it under Features
• Haal Centraal BRP connectorBastionL · a quarter

  A live connector to the BRP API with the field list derived from the registered purpose and the authorisation, PKIoverheid and Diginetwerk transport, a short freshness cache with provenance, and protocollering of both the acquisition and the provision. The published test persons load as a labelled test vault.

  Shipped 28 Sept 2026 in 1.20.0 · see it under Features
• KVK connectorBastionM · weeks

  Company profiles through the KVK search, basic profile and establishment profile APIs. Public company data is kept apart from the personal data of a sole trader or a partnership, whose whole registration is stored under a class the gate treats as personal.

  Shipped 28 Sept 2026 in 1.20.0 · see it under Features
• Managed file transferRobeeflowL · a quarter

  Partner profiles with a pinned host key and sealed credentials, transfers over secure file transfer in both directions, over HTTPS and from watched folders, payload-level encryption, checksums that travel with the file, retries with backoff and restart from the byte a transfer stopped at.

  Shipped 28 Sept 2026 in 1.20.0 · see it under Features
• Metadata schema aligned with MDTO and the six classesDocument StoreM · weeks

  Every document carries the MDTO elements a Dutch archive expects, from archive creator and retention term to checksum and format, plus exactly one classification class that decides masking, sharing and export. A document without a class does not save.

  Shipped 28 Sept 2026 in 1.20.0 · see it under Features
• OIN register upgradeBastionS · days

  The existing mirror loads into a vault of its own through the access layer, refreshed daily from the Logius export, with parent and sub-OIN relations, the KVK cross-link and a freshness stamp and provenance on every lookup.

  Shipped 28 Sept 2026 in 1.20.0 · see it under Features
• One access layer for documents on all four channelsDocument StoreM · weeks

  Every list, get, put, share, deliver, sign and delete passes one on-server layer that resolves who is asking, checks the purpose, applies the class rules, decrypts, writes the row and attests egress, and the API, the Document Keeper flow node, the MCP tools and the chat tools are adapters over it. This extends the vault access layer of vault-01 with a document resource type.

  Shipped 28 Sept 2026 in 1.20.0 · see it under Features
• Per-document envelope encryption on the vault key hierarchyDocument StoreM · weekssovereign

  Each document gets its own data key, wrapped by its tenant key, wrapped in turn by the platform master key, so rotation re-wraps keys without touching a single document. Every record names the data key and the tenant key version that sealed it. A tenant the operator cannot read waits on customer-held keys (vault-03).

  Shipped 28 Sept 2026 in 1.20.0 · see it under Features
• PII-aware storageMailM · weekssovereign

  Scan at ingest, redact before any model call, and encrypt stored bodies.

  Shipped 28 Sept 2026 in 1.20.0 · see it under Features
• Protocollering per open, download, share and deliveryDocument StoreM · weekssovereign

  Every read of a document on any channel writes a tamper-evident protocol row with actor, purpose, channel, document hash and version, pages returned with their class, counterparty and outcome, kept append-only for its legal term, so a steward answers who saw what and a data subject lists the rows about their documents. Extends vault-07 from records to documents.

  Shipped 28 Sept 2026 in 1.20.0 · see it under Features
• Purpose binding per vault with a generated verwerkingsregisterBastionM · weeks

  Purposes and lawful bases are registered per vault and per consumer, the gate refuses free text and any purpose it does not know, a Guardian approves purposes with a BSN scope, and the article 30 register of processing activities is rendered from that configuration alone, versioned by content hash, signed and regenerated whenever a purpose or a retention term changes.

  Shipped 28 Sept 2026 in 1.20.0 · see it under Features
• Records belong to a customer and an authorisation covers a populationBastionM · weekssovereign

  A record names the customer it belongs to and a purpose names the people it covers rather than the whole register, the way a Dutch autorisatiebesluit does. A read is answered for the caller's own customer, an authorisation narrows further by any field of the record, and reaching across customers is a declared, operator-only act recorded on every row.

  Shipped 28 Sept 2026 in 1.21.0 · see it under Features
• Retention and archival per vaultBastionM · weeks

  Each vault and protocol store gets a retention rule tied to the Archiefwet selection list or the customer's own term, with a legal hold and an archival step before deletion, and a daily sweep that respects both. The retention page shows what is past its term and what the sweep would do.

  Shipped 28 Sept 2026 in 1.20.0 · see it under Features
• Retention per class and legal hold for documentsDocument StoreM · weeks

  Each document inherits a retention term from its information category and class, a document past term becomes a tombstone and is purged after a grace period, and a legal hold for litigation, a Woo request or an investigation freezes deletion until a recorded decision lifts it. Sealing into an archive before purge is not built.

  Shipped 28 Sept 2026 in 1.20.0 · see it under Features
• Unified transaction timelineObservabilityL · a quartersovereign

  Paste any id and get one ordered list of everything that happened because of it, on both sides of the bridge, from message received through nodes, AI calls, deliveries, acks, alerts, replays, cascade steps, reports, notifications, audit rows, archive documents and evidence. Each event carries its source, status, duration, links and hashes.

  Shipped 28 Sept 2026 in 1.20.0 · see it under Features
• Vault console with break-glass and no direct database accessBastionM · weeks

  The console shows masked records with a reveal that needs a reason and is protocolled, and a BSN-class or special-category reveal first needs a second administrator to approve a request that is valid for fifteen minutes and for one reveal. Break-glass without a second person takes an explicit flag and raises an alert somebody has to answer for.

  Shipped 28 Sept 2026 in 1.20.0 · see it under Features
• Versions, immutability and tombstonesDocument StoreM · weeks

  A new upload of a known document becomes a new version linked to the old one, and a deletion leaves a tombstone with actor, reason and legal basis, so the same bytes cannot quietly come back and content only disappears once retention and holds allow it.

  Shipped 28 Sept 2026 in 1.20.0 · see it under Features
• Withholding a record from disclosureBastionM · weekssovereign

  A person can ask for their record to be withheld, which the population register calls a verstrekkingsbeperking. It disappears from every read, search and count, a single time-boxed look needs a second administrator, and out of scope, withheld and absent all answer in the same words so the answer itself reveals nothing.

  Shipped 28 Sept 2026 in 1.21.0 · see it under Features
• WOZ connectorBastionM · weeks

  LV WOZ queries over Digikoppeling WUS limited to the fields the Waarderingskamer authorisation matrix gives the customer's role, which narrows the answer a fourth time after the purpose, its field list and the authorisation. Every value is stored with its reference date and the authority it was obtained under.

  Shipped 28 Sept 2026 in 1.20.0 · see it under Features
• A real MCP server for SpectreSpectreM · weeks

  scrape, crawl, map, search, extract and watch over MCP with streamable HTTP and stdio, backed by the existing bridge and API keys, so outside agent runtimes call Spectre natively.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• Agent permission manifestsPlatformM · weekssovereign

  Each agent declares the tools, collections and hosts it may touch; anything outside the manifest lands in an approval queue.

  Shipped 27 Sept 2026 · see it under Features
• AI Act dossier generatorPlatformM · weekssovereign

  From the ledger, the model registry and the routing file, produce the Annex IV technical documentation and a risk classification per AI use, as a versioned document per module.

  Shipped 27 Sept 2026 · see it under Features
• AI bridge keys stored as hashesBastionM · weekssovereign

  Every AI-side caller, whether a chat tool, an MCP key, an agent manifest or a flow node, holds a scoped bridge key that names the vault, the purpose, the field classes and the rate. The key exists on the server only as a keyed hash, the bridge resolves records on the server and hands the local model only class-filtered fields or citations, and a hosted model lane is refused by code.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• AI call lineage ledgerPlatformM · weekssovereign

  Each inference records prompt hash, model, parameters, output hash, user and module, hash-chained. The logging the EU AI Act asks for on high-risk use.

  Shipped 27 Sept 2026 · see it under Features
• AI chat bridge with vault tools for local modelsBastionL · a quartersovereign

  Ask Buddy about a person, building or company and the local model calls a server-side vault tool whose result is redacted by class before it enters the prompt, pinned to a local lane by code, and cited back to the record and its protocol row. An unlock ceremony precedes the first read of a session.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• AI-to-AI autonomous vault accessBastionM · weekssovereign

  A flow or cascade step queries a vault for another agent under that agent's permission manifest, decrypts only the allowed fields, writes a lineage row linking both agents to the record, and refuses to hand BSN-class fields to steps that send outward.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• Allow, deny and suppression listsMailM · weeks

  Sender and domain policy per mailbox plus a global suppression list, enforced before any draft is written.

  Shipped 27 Sept 2026 · see it under Features
• Autonomous responder with a held queueMailL · a quartersovereign

  Guard, understand, draft, verify, decide, send and record, shipped with draft as the default and an Approve, Edit, Reject queue in the mail page.

  Shipped 27 Sept 2026 · see it under Features
• Backup rehearsalOperationsS · days

  Scheduled PocketBase snapshots restored into a scratch instance with a report of what came back.

  Shipped 27 Sept 2026 · see it under Features
• Batch improvementsSpectreS · days

  URL dedupe, per-batch formats and schema, concurrency honoured against the browser pool, paginated results.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• Caller-controlled cachingSpectreS · days

  maxAge, minAge and storeInCache per request, with cachedAt in the answer.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• Crawl-wide schema extractSpectreM · weeks

  One schema over every page of an extraction or a URL list, chunked and merged, validated with one retry.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• Data-never-leaves attestation per queryBastionM · weekssovereign

  Every vault read through any channel produces a signed row stating the local lane and model used, that no outbound connection was made during the query, the fields and classes returned, and the protocol and lineage identifiers, exportable for auditors.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• Data-subject rights toolingBastionM · weeks

  Look a person up by BSN under a registered purpose and produce an access export with protocol history, record a rectification with before and after, and delete with a tombstone so a later import cannot bring the person back.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• Decision audit trailMailS · dayssovereign

  One record per stage with model, lane and prompt hash, shown as a timeline on the mail and counted in the usage tables.

  Shipped 27 Sept 2026 · see it under Features
• Declarative page actionsSpectreM · weeks

  wait, click, write, press, scroll, executeJavascript, screenshot and scrape steps in the existing Chrome session, replacing the raw script string; unlocks login walls and infinite scroll.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• Design-system compliance gateDesign systemS · days

  Extend the palette lint, add a raw-primitive rule and publish a component index page, so the compliance score becomes a number that only goes up.

  Shipped 27 Sept 2026 · see it under Features
• Dutch government source packsSpectreM · weekssovereign

  First-class packs for TenderNed, officielebekendmakingen.nl and the KVK register with seeds, a schema, a watch preset and legal notes.

  Shipped 27 Sept 2026 · see it under Features
• Envelope encryption with per-vault data keys and rotationBastionM · weeks

  Each vault gets its own data key wrapped by a platform key, every record carries its key version, and rotation re-wraps keys without re-encrypting every record. The readiness page shows key age and rotation status.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• Evidence-grade archivingSpectreL · a quartersovereign

  Raw response, headers, rendered DOM and screenshot per fetch as WARC, hash-chained by day and signed, with a verify endpoint.

  Shipped 27 Sept 2026 · see it under Features
• Format selector on FetchSpectreS · days

  Ask for markdown, html, rawHtml, links, screenshot or json and get only that from the cached artifacts; screenshots become reachable from the API.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• Generate and wire DKIM keys in deployMailS · days

  The deploy creates the key, sets the variables and prints the TXT record.

  Shipped 27 Sept 2026 · see it under Features
• Immutable audit exportPlatformS · days

  Hash-chain the audit history across platform and hub and export it to write-once storage on a schedule, with a verifier anyone can run.

  Shipped 27 Sept 2026 · see it under Features
• Intranet crawling under the hub's SSRF policySpectreM · weekssovereign

  The hub's URL policy adopted by Spectre so it can crawl internal wikis under an allow-list with redirect and DNS-rebind protection.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• Job cancel, errors and paginationSpectreS · days

  Cancel endpoints for batch and extract, an errors listing, and a cursor for large results.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• Keep the raw message and real headersMailM · weeks

  A proper MIME parser, the raw message kept as a file, the full header map and attachment list stored, and the truncation removed.

  Shipped 27 Sept 2026 · see it under Features
• Keyed hashing and tokenisation serviceBastionM · weeks

  A hashing key separate from the encryption key produces the lookup hashes for BSN, KVK and address keys, and every BSN is elfproef-checked first. Per-purpose pseudonyms exist only in the masked sandbox, per run; format-preserving tokens for vault data downstream are not built.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• Location and language emulationSpectreS · days

  Country and languages set Accept-Language, Chrome locale and timezone, and pick a matching proxy.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• Loop protectionMailS · days

  Honour Auto-Submitted, Precedence, List headers and null senders, never auto-reply to them, and mark AI replies as auto-replied.

  Shipped 27 Sept 2026 · see it under Features
• Masked replay sandboxRobeeflowS · dayssovereign

  Replay a real received message into a dry run with personal data masked, so an integrator can debug production traffic without seeing it.

  Shipped 27 Sept 2026 · see it under Features
• MCP vault tools with scoped keysBastionM · weeks

  External agents call vault search, get and verify over MCP with a key scoped to one vault, purpose, field set and rate. The bridge applies the same manifest check as chat and writes the same protocol and lineage rows.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• On-demand change trackingSpectreM · weeks

  A changeTracking format on Fetch with previous capture time, status, a git-style diff and a schema-driven field diff, with tags for separate histories.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• PDF and Office auto-parseSpectreM · weeks

  Branch on content type: PDF with page markers, DOCX through the existing reader, and OCR fallback for scanned PDFs on local page images.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• Per-request crawl controlsSpectreM · weeks

  limit, depth, include and exclude paths, subdomains, external links, sitemap modes, query-parameter handling, delay and concurrency on every crawl and extraction.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• PII-aware extraction with the vaultSpectreM · weekssovereign

  The PII detector runs over every page of a request whose policy asks for redaction, and findings are replaced with typed placeholders before results reach a model, disk or a webhook. Tokenising findings into the vault, so a result can be re-identified under a purpose, is not built.

  Shipped 27 Sept 2026 · see it under Features
• Protocollering per readBastionM · weeks

  Every read of a personal-data vault writes a tamper-evident protocol row with who asked, under which purpose, which fields came back and a hash of the record, kept for its legal term and never showing a raw identifier. A citizen's protocol can be listed per person.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• Public API and SDKsSpectreL · a quarter

  A versioned Spectre API with scoped keys, per-key limits and quotas, an OpenAPI description and thin TypeScript, Python and Go clients.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• robots.txt everywhereSpectreS · dayssovereign

  One shared robots cache consulted by fetch, extract, map, watch, batch and scout, with crawl-delay honoured and an explicit, recorded operator override.

  Shipped 27 Sept 2026 · see it under Features
• Route every Spectre inference through the spectre laneSpectreS · days

  Schema extract and search answers call the spectre lane, so routing edits and usage accounting see them.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• Semantic change summaries in WatchSpectreS · days

  After a hash change a local model says what changed and whether it matters, and cosmetic diffs are suppressed by a threshold.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• Semantic keywords and site searchSpectreM · weekssovereign

  Embed every fetched page locally, replace frequency ranking with hybrid search, and offer search over everything Spectre has ever crawled plus near-duplicate detection.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• Signed lifecycle webhooksSpectreM · weeks

  started, page, completed and failed events for batch, extract and watch with an HMAC header and retries.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• Signed model registryPlatformM · weekssovereign

  Every model in the fleet gets a manifest with weights hash, source, licence, benchmark scores and promotion date; health refuses a model whose hash drifted.

  Shipped 27 Sept 2026 · see it under Features
• Stealth tier and Chrome proxyingSpectreM · weeks

  Pass the proxy pool into Chrome, add basic, stealth and auto modes with retry on bot detection, and per-tenant pools.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• Stop banning legitimate sendersMailS · days

  Return a plain refusal instead of a blacklist strike for unknown recipients and keep the reverse-DNS rule as a score.

  Shipped 27 Sept 2026 · see it under Features
• ThreadingMailS · days

  Persist and emit Message-ID, In-Reply-To and References, compute a thread id, show threads in the UI.

  Shipped 27 Sept 2026 · see it under Features
• Vision-assisted extractionSpectreM · weekssovereign

  Send local screenshots of charts, scanned notices and cookie-walled pages to the local vision model for captions, table transcription and page checks, and feed alt text back into image extraction.

  Shipped 27 Sept 2026 in 1.18.0 · see it under Features
• Zero-egress guarantee modeSpectreS · dayssovereign

  A tenant policy that disables every hosted lookup and stamps every result with an egress attestation. Spectre no longer solves CAPTCHAs at all (1.47.0); a page that presents one is recorded as protected.

  Shipped 27 Sept 2026 · see it under Features