Next Matter
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Next Matter GmbH · www.nextmatter.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Next Matter at a glance
- Vendor
- Next Matter GmbH
- Headquarters
- Not stated on the vendor’s pages as of 10 Nov 2026
- Data hosting
- Default not stated; pages mention the EU and the US source, captured 10 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 10 Nov 2026
- Panel verdict
- The AI panel rates Next Matter 2.5/5, the mean of 6 judges. Next Matter scores strongest on governance and audit at 7-8 and process design at 7, weakest on run reliability at 4 and hosting and portability at 2-4. how scores are made
- As of
- Vendor pages captured 10 Nov 2026; evaluated by the panel 11 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Next Matter scores strongest on governance and audit at 7-8 and process design at 7, weakest on run reliability at 4 and hosting and portability at 2-4. Process design rests on per-step maker-checker and four-eyes approvals and versioning that keeps running instances on their original version through publishes and rollbacks. Governance and audit leads on SAML/OIDC single sign-on with SCIM 2.0 provisioning, access control to workflow and step level, and an immutable audit trail exportable as PDF, CSV or API; SOC 2 Type II is under NDA. Run reliability sits at 4: we found no public information on retries, error paths or failure alerts. The split is hosting and portability at 2-4 over the same facts — Frankfurt on AWS eu-central-1, EU or US residency enforced end-to-end, we found no public information on exporting workflow definitions or on self-hosting — and lower scores weight the missing exit path hardest. Integrations span 6-7; sovereignty 5-6, dented by a subprocessor list available only on request, a GPT-4.1 example and England-and-Wales governing law. Pricing transparency scored 0.
Speaks for it
- Versioning keeps running instances on their original version through publishes and rollbacks, with drafts tested in a sandbox before release
- Role-based access reaches workflow and step level via SAML/OIDC single sign-on with SCIM 2.0 provisioning
- The immutable audit trail captures inputs, outputs, approver identity and the policy in force at run time, exportable as PDF, CSV or via API
- Named connectors include SAP ERP, the Microsoft stack via Teams and Power Automate, Salesforce, Workday, QuickBooks and Xero, with bi-directional REST and GraphQL APIs and webhooks
- Data is stored in Frankfurt, Germany on AWS eu-central-1, with an EU or US residency choice enforced end-to-end and dedicated infrastructure available for regulated customers
Held against it
- We found no public information on automatic retries, error paths, failure alerting or a public status page
- We found no public information on exporting workflow definitions in a format another tool could read, or on a self-hosted or on-premise edition
- The subprocessor list is available only on request rather than published, and the documented AI example runs on GPT-4.1
- The SOC 2 Type II report is available only under NDA, and access logs are archived for three months
- We found no public information on deadlines, reminders or escalation chains for open tasks, or on a documented notation such as BPMN
Best for
- You run approval-heavy operational processes and need per-step maker-checker, four-eyes and delegated approvals with immutable audit evidence for regulators
- You need version discipline — publishing and rollback must not disturb already-running instances, and drafts must be tested before release
- Your stack is covered by the named connectors — SAP ERP, the Microsoft stack via Teams and Power Automate, Salesforce, Workday, QuickBooks, Xero — with webhooks and bi-directional REST and GraphQL APIs for the rest
- You need a named EU region — the pages state data is stored in Frankfurt, Germany on AWS eu-central-1, with an EU or US residency choice enforced end-to-end
Avoid if
- You need documented failure handling for unattended runs — run reliability scores cluster at 4 and we found no public information on retries, error paths or failure alerts
- Your exit plan requires workflow definitions in a format another tool can run — the documented one-click exports cover run history, approval chains and policy diffs, and we found no public information on exporting the definitions themselves
- You require a subprocessor list published with locations — the list is available only on request
- Your contracts must be governed by EU law — the data processing agreement is governed by the laws of England and Wales
The scores
| Criterion | Panel median |
|---|---|
| Process design, forms & approvals | 3.5 of 5 |
| Connectors, API & on-premise reach | 3.5 of 5 |
| Execution, error handling & monitoring | 2 of 5 |
| Governance, credentials & audit trail | 3.5 of 5 |
| Hosting options & portability | 2 of 5 |
| European sovereignty | 2.5 of 5 |
Process design, forms & approvals
Show reasoningHide reasoning
How this is scored
Modelling the process people take part in: a visual designer or BPMN, forms, approval steps with roles and substitutes, deadlines and escalation, and versioning of a process that is already running — judged on whether a business owner can change a process without breaking the instances in flight.
0 — No human steps at all: neither forms nor approval steps, only machine-to-machine automation.
3 — A visual builder with branching and a simple approval or form step.
5 — A visual designer with conditions and parallel paths, forms and approval steps assigned to roles or groups, and deadlines or reminders for open tasks.
8 — BPMN 2.0 modelling or an equivalent documented notation, versions of a process kept with running instances on their original version, substitutes and escalation chains, multi-stage approvals with four-eyes rules, forms in German with validation and file upload, a task inbox for participants, and a test or simulation mode before publishing.
10 — The process is a governed asset: version history with diff and rollback, migration of running instances to a new version documented, process analytics on cycle time and bottlenecks per step, and the design documented well enough that a business team can maintain it without the vendor.
The Process Owner
A drag-and-drop designer with conditional branching, parallel steps, forms and role-bound maker-checker or four-eyes approvals, and the versioning discipline I insist on: drafts are tested while the published version stays in use, rollback leaves already-started instances on the old version, and published versions are protected from deletion while instances are linked. I found no public information on explicit deadlines with escalation chains, on named substitutes for absence, or on a documented BPMN-style notation. 4 5 8 9
The Integration Engineer
Version handling is the strongest part: publishing a new version leaves already-running instances on their original version, rollback is documented not to interrupt running instances, and drafts can be tested in a sandbox before going live. Forms, parallel branches, conditional routing and per-step maker-checker, four-eyes and delegated approvals respecting time-off are all documented. We found no public information on deadlines, reminders or escalation chains for open tasks, or on a documented notation such as BPMN. 4 5 8
The Operations Analyst
The drag-and-drop builder covers conditions, loops, branches and parallel steps, with forms, portals, four-eyes and delegated approvals per step, and a sandbox to test before publishing. Versioning is the strong part: drafts are testable while the live version runs unchanged, running instances keep their original version across publishes and rollbacks, and the changelog records every individual change. We found no public information on deadlines, escalation chains, a BPMN or equivalent notation, migration of running instances to a new version, or cycle-time analytics per step. 4 5 8
The Head of IT
The drag-and-drop builder handles parallel steps, conditions and loops with forms and maker-checker, four-eyes approvals per step, and versioning behaves the way I insist on: instances keep the version they started on, rollback does not interrupt running instances, and drafts are tested in a sandbox before publishing. We found no public information on BPMN or another documented notation, on deadlines and reminders for open tasks, or on substitutes and escalation chains, so it stops short of the top band. 4 5 8
The Data Protection Officer
The drag-and-drop builder threads together human tasks, forms, conditional logic, loops, branches and parallel step groups, with maker-checker, four-eyes and delegated approvals per step; versioning keeps running instances on their original version through both publish and rollback, drafts are testable before release, and the changelog records each individual change as a line. I found no public information on a documented notation such as BPMN, or on forms with German-language validation and file upload. 4 5 8
The Skeptic
The drag-and-drop builder documents conditions, parallel steps, forms and maker-checker approvals with four-eyes, and the versioning story is unusually concrete: instances keep the version they started on, rollback does not interrupt running instances, and each change gets its own changelog line with a sandbox for testing drafts. We found no public information on deadlines, reminders or escalation chains for open tasks, on BPMN or an equivalent notation, or on form validation, file upload or a participant task inbox, which keeps this below the full governed-notation level. 4 5 8
Connectors, API & on-premise reach
Show reasoningHide reasoning
How this is scored
Reaching the systems a European company actually runs: maintained connectors judged by name rather than count, a generic HTTP and webhook step, custom connectors, and a way to reach systems behind the firewall without opening it.
0 — No connectors beyond email, and no API or webhook step.
3 — A catalogue of connectors to common SaaS tools, or webhooks and an HTTP step to call other systems.
5 — Named connectors with their triggers and actions documented, including Microsoft 365 or Google Workspace, a generic HTTP/REST step with inbound webhooks, and an API to start or query workflows.
8 — Connectors to an ERP or accounting system common in DACH (e.g. SAP, DATEV, Microsoft Dynamics), custom connectors buildable from an OpenAPI description or code, an on-premise agent or self-hosted runner reaching internal databases and file shares, SOAP and database steps, and connector maintenance ownership (vendor, partner or community) stated.
10 — Integration is engineered: a versioned public API with a deprecation policy, connector changelogs, rate limits per connector published, event-driven triggers rather than polling where the source allows it, and the vendor maintaining the German-market connectors (DATEV, SAP, ELO or d.velop) itself.
The Process Owner
Named connectors include SAP ERP, the Microsoft stack via Teams and Power Automate, Slack, DocuSign, QuickBooks and Xero, with inbound webhook triggers and variable extraction documented plus bi-directional REST and GraphQL APIs, and the vendor's solution engineering team activates custom connectors within days. I found no public information on an on-premise agent for systems behind the firewall or on a DATEV connector. 3 6 7
The Integration Engineer
Named connectors include SAP ERP alongside Salesforce, Workday and the Microsoft stack via Teams and Power Automate, and the webhook trigger is documented down to payload variable extraction, custom variables and a test call — documentation by action, which is what I look for. Custom connectors are built by the vendor's solution engineering team 'in a matter of days' with an OAuth2 configuration shown. We found no public information on an on-premise agent or self-hosted runner reaching internal databases behind the firewall, on a DATEV connector, or on per-connector maintenance ownership. 3 4 6 7
The Operations Analyst
Named connectors include SAP ERP, PostgreSQL, Redshift, the Microsoft stack, QuickBooks and Xero, plus inbound webhooks with variable extraction, bi-directional REST and GraphQL APIs, monthly new integrations, and the vendor's solution engineering team activating custom API connectors "in a matter of days". We found no public information on an on-premise agent or self-hosted runner, DATEV, SOAP, per-connector trigger and action documentation, rate limits, or an API versioning and deprecation policy. 3 6 7
The Head of IT
There is a broad named catalogue including Microsoft 365 via Teams and Power Automate, an SAP ERP bridge and a PostgreSQL connector, plus documented inbound webhook triggers and bi-directional REST and GraphQL APIs to start and query processes. Custom connectors are described as activated by the vendor's solution engineering team within days rather than self-built from an OpenAPI description, and we found no public information on an on-premise agent or self-hosted runner to reach internal systems behind the firewall. 3 6 7
The Data Protection Officer
Named connectors include SAP ERP, Salesforce, Workday, QuickBooks, Xero, Zendesk and the Microsoft stack via Teams and Power Automate, backed by bi-directional REST and GraphQL APIs, event-driven webhook triggers, PostgreSQL and Redshift steps, and a vendor solution-engineering team that activates custom connectors and ships new integrations monthly. I found no public information on an on-premise agent or self-hosted runner to reach systems behind the firewall, or on building connectors from an OpenAPI description. 3 4 6 7
The Skeptic
Named connectors include Microsoft, Google, Slack, Jira, SAP, Xero and QuickBooks, webhooks are event-driven with documented trigger mechanics and variable extraction, and the REST and GraphQL APIs are described as bidirectional. The DACH depth stops at the SAP logo — no DATEV, Dynamics, ELO or d.velop appears — custom connectors are activated by the vendor's solution engineering team in days rather than buildable from an OpenAPI description, and we found no public information on an on-premise agent or self-hosted runner reaching systems behind the firewall, nor on connector maintenance ownership or rate limits. 6 7 3
Execution, error handling & monitoring
Show reasoningHide reasoning
How this is scored
What happens when a step fails at 3 a.m.: retries, error paths, alerting, an execution history someone can search, limits on runtime and throughput, and a status page that admits incidents.
0 — Nothing runs unattended: the product executes no automated workflows whose runs could fail or be monitored.
3 — Failed runs marked with a notification, and a history of recent executions.
5 — Automatic retries or an error path, an execution log with input and output per step, failure alerts by email or chat, and runtime or rate limits documented.
8 — Configurable retries with back-off and replay of a failed run from the failing step, queueing and concurrency controls, execution history retention stated per plan, monitoring exportable to the customer's own tools, and a public status page with incident history and an uptime commitment.
10 — Operations are designed for production: an SLA with service credits, horizontal scaling or high-availability setup documented for self-hosted installs, dead-letter handling, end-to-end tracing across workflows, and post-incident reports published.
The Process Owner
A full run history is documented — every step, timestamp, actor and system involved — exportable as PDF, CSV or via API into our own tooling, alongside dashboards with filters and alerts and daily backups restorable on a 14-day basis. I found no public information on automatic retries, error paths, runtime or rate limits, or a public status page with incident history. 4 8
The Integration Engineer
The trail captures inputs, outputs, timestamps and actors per step, and run diffing plus replay of a historic decision under the policy in force at the time is documented — but that is a governance replay, not replay of a failed run from the failing step. We found no public information on retries, error paths, failure alerts, execution-history retention, runtime or rate limits, or a public status page with incident history. 4 8
The Operations Analyst
Run history is documented in full — every step, timestamp, actor and system, with run-to-run diffing, replay of historic decisions and one-click export to PDF, CSV or via API — but dashboards only offer "custom tables, filters & alerts" without anything tying alerts to failed runs. We found no public information on automatic retries, error paths, failure alerts reaching a chat channel, runtime or throughput limits, execution-history retention per plan, or a public status page. 4 7 8
The Head of IT
Run history is genuinely auditable — every step with timestamp, actor and system, inputs and outputs captured immutably, with dashboards offering custom tables, filters and alerts. The overnight-failure story is thin, though: we found no public information on automatic retries or error paths, on alerting channels for failures, or on runtime, throughput and history-retention limits per plan. 4 8
The Data Protection Officer
The audit trail captures every step with timestamp, actor and system involved, inputs and outputs, historic decisions can be replayed, run history exports as PDF, CSV or via API, and data is backed up daily with a 14-day restore window. I found no public information on automatic retries or error paths, failure alerting channels, execution history retention per plan, or a public status page with incident history. 2 4 8
The Skeptic
The governance page documents a full run history — every step, timestamp, actor and system involved — plus dashboards with filters and alerts and the ability to diff runs, which is more than a bare execution list. We found no public information on automatic retries, error paths, failure notification by email or chat, runtime or throughput limits, execution history retention, monitoring export, or a status page with incident history, so what happens to a failed run overnight is not documented anywhere we read. 8 4
Governance, credentials & audit trail
Show reasoningHide reasoning
How this is scored
Keeping automation from becoming shadow IT: roles and permissions, SSO, where connection credentials are stored, separate environments with controlled publishing, an audit trail of changes and approvals, and what the execution log retains of the payload. An approval record is also a record of employees' behaviour (BetrVG § 87 (1) 6), so what the trail captures matters to a works council.
0 — No user management: one account per person or one shared login, with no team workspace.
3 — Admin and member roles with shared team folders or workspaces.
5 — Role-based permissions per workflow or folder, SSO via SAML or OIDC, credentials stored encrypted and usable without being revealed, and an audit log of workflow changes.
8 — Separate development, test and production environments with a publishing approval, SCIM provisioning, external secret stores supported, payload redaction or logging off per workflow, configurable execution data retention, and the audit trail exportable — with the fields it records about users described.
10 — Governance a works council and an auditor can both sign off: field-level masking of personal data in logs, delegated administration per department, a central inventory of every workflow and connection with its owner, certifications published (ISO 27001 or SOC 2), and documentation of what the platform records about individual users.
The Process Owner
Role-based access down to workflow and step level with SAML/OIDC single sign-on and SCIM provisioning, built-in roles such as workflow lead and task admin, maker-checker with the approver's identity captured immutably, and one-click exports of run history and approval chains with the recorded fields described down to user ID, computer and IP address. I found no public information on separate development, test and production environments with a publishing approval, or on external secret stores. 3 8 9
The Integration Engineer
Six built-in roles with per-area permission tables, custom roles on the Enterprise plan, SAML/OIDC single sign-on with SCIM 2.0 provisioning and access control down to workflow and step level are documented, and the audit trail is immutable, exportable as PDF, CSV or via API, with its recorded fields named down to approver identity and the policy in force at run time. SOC 2 Type II exists but the report is available only under NDA, and we found no public information on separate development, test and production environments with a publishing approval, external secret stores, or configurable payload retention. 2 3 8 9
The Operations Analyst
Six built-in roles plus Enterprise custom roles, SAML/OIDC with SCIM 2.0 provisioning, enforced MFA, least-privilege defaults with every access decision logged, encrypted credential storage, and an immutable trail capturing approver identity, inputs, outputs and the policy in force at run time — exportable as an evidence pack into GRC tooling, with SOC 2 Type II stated under NDA. We found no public information on separate development and production environments with a publishing approval, external secret stores, or per-workflow payload logging controls and configurable retention; the access log retention is fixed at 3 months. 2 3 5 8 9
The Head of IT
This is close to what I would sign off: SAML/OIDC single sign-on with SCIM provisioning, role-based access down to workflow and step level mapped to SSO groups, built-in roles from Task Admin to Light user with custom roles on the Enterprise plan, encrypted credential storage, a granular changelog, and an immutable audit trail exportable as PDF, CSV or via API, with the access log's fields (user ID, computer, IP address) and three-month retention described in the data processing agreement. Draft-versus-published versioning with a sandbox covers testing before release, but we found no public information on separate development, test and production environments with a publishing approval, on external secret stores, or on payload redaction configurable per workflow. 2 3 5 8 9
The Data Protection Officer
SSO via SAML and OIDC with SCIM 2.0 provisioning, enforced MFA and role-based access down to workflow and step level across six built-in roles sit on top of an immutable, tamper-evident audit trail recording inputs, outputs, model versions and approver identity — and the processing agreement even states what is logged about each user (user ID, computer, IP address), archived for three months. I found no public information on payload redaction, configurable execution-data retention, or separate development and production environments, and the SOC 2 Type II report is available only under NDA rather than published. 2 3 8 9
The Skeptic
Role-based access reaches down to workflow and step level and maps to SSO groups via SAML/OIDC with SCIM 2.0 provisioning, only admins can connect integrations or invite colleagues, and the audit trail is immutable — capturing inputs, outputs, approver identity and the policy in force at run time — and exportable as PDF, CSV or via API into GRC tooling. A SOC 2 Type II report exists but only under NDA, access logs are kept for a fixed three months, and we found no public information on separate development and production environments with publishing approval, external secret stores, payload redaction, or configurable execution-data retention. 3 8 9 2
Hosting options & portability
Show reasoningHide reasoning
How this is scored
Where the engine runs and whether the workflows can leave: cloud regions, self-hosted or on-premise editions, the licence of the engine, and export of workflow definitions in a format another tool or a later version can read.
0 — Workflows cannot be exported in any form and live only in the vendor's cloud.
3 — Cloud hosting with the region named, and workflows exportable as a file the same product can import.
5 — An EU cloud region available, workflow definitions exportable as documented JSON or BPMN 2.0, and an API to read definitions and execution history.
8 — A self-hosted or on-premise edition with its system requirements documented, workflow definitions versionable in Git, the engine's licence published, and a documented migration path between cloud and self-hosted in both directions.
10 — The customer owns its automation: an open-source or source-available engine, definitions in an open standard executable elsewhere, air-gapped installation supported, and a stated exit process that hands back definitions, credentials metadata and execution history in documented formats.
The Process Owner
Cloud regions are named — EU or US selectable, with Frankfurt on AWS eu-central-1 — and execution history is reachable via API. I found no public information on a self-hosted or on-premise edition, or on exporting workflow definitions in a documented format another tool could read. 2 3
The Integration Engineer
The captured pages document cloud hosting with the region named — Frankfurt on AWS eu-central-1 — an EU or US region choice enforced end-to-end, and dedicated infrastructure for regulated customers. We found no public information on export of workflow definitions in a documented format, on a self-hosted or on-premise edition, or on the engine's licence, so I cannot verify any portability out of the vendor's cloud. 2 3
The Operations Analyst
Hosting is the vendor's cloud with the region named — Frankfurt, AWS eu-central-1 — and an EU or US region selectable with processing enforced end-to-end, plus dedicated infrastructure for regulated customers, and run history exports via API. We found no public information on a self-hosted or on-premise edition, an export format for the workflow definitions themselves, or the engine's licence. 2 3 8
The Head of IT
Hosting is EU-capable — data stored in Frankfurt on AWS, with EU and US residency selectable and enforced end-to-end — but the exit test is what decides it here: we found no public information on export of workflow definitions as BPMN or documented JSON, on a self-hosted or on-premise edition, on the engine's licence, or on a migration path out of the vendor's cloud. The only export documented is audit evidence (run history, approval chains, policy diffs) into GRC tooling, not the definitions themselves. 2 3 8
The Data Protection Officer
Cloud hosting runs on AWS eu-central-1 in Frankfurt, with an EU or US region choice enforced end-to-end and a processing agreement that promises return or deletion of all personal data at the customer's choice when the service ends. I found no public information on exporting workflow definitions in a documented format another tool can read, a self-hosted edition, the engine's licence, or a migration path — the one-click export covers run history, approval chains and policy diffs rather than definitions. 2 3 8
The Skeptic
The cloud region is named — data stored in Frankfurt on AWS eu-central-1, with an EU or US residency choice enforced end-to-end and dedicated infrastructure available for regulated customers. We found no public information on self-hosting or on-premise editions, and nothing on exporting workflow definitions in any documented format: the one-click exports documented are run history, approval chains, policy diffs and model cards as PDF, CSV or API — audit evidence, not a process definition another tool could read or run. 2 3 8
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity is, where workflows execute and where execution logs with their payload copies are stored, and who the subprocessors are — including the AI model providers behind any AI steps. Independently sourced by the sovereignty pipeline. A self-hosted edition counts only for the data that actually stays on the customer's servers.
0 — Proven non-EU throughout: non-EU vendor and contracting entity, execution outside the EU, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, while an EU contracting entity and EU execution are not shown, or an EU region is an option under a non-EU contracting entity.
5 — EU execution and log storage stated (as standard or selectable) and an EU contracting entity or EU representative, with a data processing agreement; parts of the chain such as AI steps, support access or telemetry may run outside the EU.
8 — EU execution on named infrastructure, EU contracting entity, subprocessor list published with locations including AI providers, a DPA covering execution payloads, and a self-hosted option that sends no workflow data to the vendor.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, AI steps runnable on European or self-hosted models, certification published, and a self-hosted edition that works without any call home.
The Process Owner
The data processing agreement is concluded with Daizy NM Limited of Dublin, data can be held in Frankfurt with the chosen region enforced end to end, and a GDPR Article 28 agreement with Standard Contractual Clauses and a 30-day subprocessor change notice exists. The subprocessor list is available on request rather than published with locations, the AI steps name a model (GPT-4.1) without stating where it runs, and the captured pages name a local subsidiary without stating the parent company's seat. 2 3 8
The Integration Engineer
The processing agreement names Daizy NM Limited of Dublin as contracting entity, storage in Frankfurt with an EU region selectable end-to-end, and an Article 28 GDPR agreement with standard contractual clauses for subcontractors and 30 days' notice of subprocessor changes. The subprocessor list is available on request rather than published, the documented AI example runs on GPT-4.1, the agreement chooses the laws of England and Wales, and the parent company's seat is not stated on the captured pages. 2 3 8
The Operations Analyst
The contracting entity is Daizy NM Limited of Dublin, data is stored in Frankfurt with an EU region selectable end-to-end, and a GDPR Article 28 processing agreement with SCC-based subcontractor terms and breach notification is published. The subprocessor list is available only on request, the documented AI example runs on GPT-4.1, the parent company's seat is not stated, and the agreement is governed by the laws of England and Wales — so the chain beyond the EU region is not fully shown. 2 3 8
The Head of IT
The data processing agreement names Daizy NM Limited of Dublin, Ireland as the contracting party, data is stored in Frankfurt on AWS with EU residency selectable and enforced end-to-end, and an Art. 28 GDPR agreement with SCC-backed subcontractor terms, a DPO and breach notification is in place. The subprocessor list is available only on request, the documented AI example runs on GPT-4.1, and the agreement is governed by the laws of England and Wales, so the captured pages do not show the chain beyond the core platform as European. 2 3 8
The Data Protection Officer
The contracting entity named in the data processing agreement is Daizy NM Limited of Dublin, execution can be pinned to an EU region with data stored in Frankfurt on AWS, and an Art. 28 GDPR agreement exists with SCC-based subcontractor clauses and 30-day advance notice of subprocessor changes. However, the subprocessor list is available only on request, an example AI agent runs on GPT-4.1 with no statement of where those model calls are processed, the agreement is governed by the laws of England and Wales, and the parent company Daizy's seat is never stated. 2 3 6 8
The Skeptic
The data processing agreement names Daizy NM Limited of Dublin as the contracting entity, states data is stored in Frankfurt on AWS eu-central-1, and an EU or US residency choice is enforced end-to-end, with an Art. 28 GDPR agreement, SCC-based transfers and a 30-day notice right on subprocessor changes. The subprocessor list is available only on request rather than published with locations, the example AI step runs extraction on GPT-4.1, the DPA is governed by the laws of England and Wales, and we found no public information on the parent company's seat or a self-hosted edition — an EU-executing chain with a non-European AI model in it. 2 3 8
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the monthly cost of their own processes from public pages alone: what the billing unit is (task, operation, execution, run, user or flow) and what counts as one, the allowance per tier, overage prices, and the cost of premium connectors, self-hosting, environments and AI steps.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or one tier priced, with the rest on request.
5 — Prices public for each tier with the billing period, the billing unit named and the allowance per tier given.
8 — Every tier priced publicly with its unit defined (what counts as one task or execution), allowance and limits, overage priced per unit, premium connector and add-on prices listed, self-hosted licensing stated, minimum term and VAT treatment given.
10 — Complete price computability: the monthly cost derivable for a given number of workflows, runs and steps per run, with a published calculator or worked examples, every add-on and overage on a public page, and the effect of loops and retries on the count explained.
The Process Owner not rated — no public information
I found no public information on pricing: none of the captured pages I read — the homepage, the workflow-builder page and the integrations page — names a tier price, a billing unit, an allowance or any add-on cost. 1 4 6
The Integration Engineer not rated — no public information
We found no public information on pricing: none of the captured pages shows a tier, a price, a billing unit, an allowance or an overage rate. I read the homepage, the workflow builder page and the integrations page and found no prices there. 1 4 6
The Operations Analyst not rated — no public information
We found no public information on pricing: none of the captured pages — homepage, security, workflow builder, integrations or governance — shows a tier, a billing unit and what counts as one, an allowance per plan, an overage price, or premium-connector, environment and AI-step costs. The monthly cost of a given process, including what a loop over 5,000 rows would cost, is not computable from these pages. 1 3 4 6 8
The Head of IT not rated — no public information
We found no public information on pricing: none of the captured pages states a price, billing unit, tier allowance, minimum term or VAT treatment, and the only plan reference anywhere is an unpriced "Enterprise plan" mentioned in the permissions documentation. Every commercial question is therefore a sales conversation, and a buyer cannot compute even a rough monthly cost from the published pages we read. 1 4 9
The Data Protection Officer not rated — no public information
We found no public information on pricing transparency: the homepage, the workflow builder page, the integrations page and the other captured pages we read show no tier, price, billing unit or allowance, so a buyer cannot compute a monthly cost from them. 1 4 6
The Skeptic
Across every captured page we found no price, no billing unit and no tier allowance: the only plan named anywhere is an Enterprise plan in the permissions documentation, and it carries no price, while the route to buying on the homepage is a 'Talk to Us' link. A buyer cannot compute any monthly cost of their own processes from these public pages. 1 9
European sovereignty — proven facts
1 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Not determined
unverified
Why unverified?The vendor's pages name a local subsidiary and do not state the parent's seat. |
— | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options |
EU region selectable
unverified
Why unverified?The region choice appears only as a marketing bullet on the security page, and while no self-hosted or on-premises option is mentioned anywhere, the pages never state that self-hosting is unavailable. |
1/1 pts | 3 Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Next Matter
Is Next Matter European?
Not determined: the vendor’s pages as captured do not say where Next Matter is based.
Where does Next Matter store data?
The default storage location for customer data is not stated on the vendor’s pages as of 10 Nov 2026. The vendor’s pages mention the EU and the US as hosting locations, per the vendor’s page captured 10 Nov 2026.
Does Next Matter have a free plan?
Not stated on the vendor’s pages as of 10 Nov 2026.
What are the best alternatives to Next Matter?
As of 19 Nov 2026, the panel rates Camunda (3/5), FireStart (3/5) and Appian (3/5) highest among the other 25 Workflow Management products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Camunda (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Next Matter alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 10 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity. The vendor's pages name a local subsidiary and do not state the parent's seat.
- Weak sourcing — Hosting options. The region choice appears only as a marketing bullet on the security page, and while no self-hosted or on-premises option is mentioned anywhere, the pages never state that self-hosting is unavailable.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- We found no public information on pricing on the pages we read (nextmatter.com, nextmatter.com/data-processing-agreement, nextmatter.com/security, nextmatter.com/workflow-builder, help.nextmatter.com/docs/workflow-versions, nextmatter.com/integrations and 3 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 12 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 subprocessors fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (9)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.nextmatter.com Checked 10 Nov 2026 Details →
- 2 Data processing agreement (dpa) — found from the homepage nextmatter.com Checked 10 Nov 2026 Details →
- 3 Security / trust page — found from the homepage nextmatter.com Checked 10 Nov 2026 Details →
- 4 Process design, forms & approvals — found from sitemap nextmatter.com Checked 10 Nov 2026 Details →
- 5 Process design, forms & approvals — found from sitemap help.nextmatter.com Checked 10 Nov 2026 Details →
- 6 Connectors, API & on-premise reach — found from sitemap nextmatter.com Checked 10 Nov 2026 Details →
- 7 Connectors, API & on-premise reach — found from sitemap help.nextmatter.com Checked 10 Nov 2026 Details →
- 8 Governance, credentials & audit trail — found from sitemap nextmatter.com Checked 10 Nov 2026 Details →
- 9 Governance, credentials & audit trail — found from sitemap help.nextmatter.com Checked 10 Nov 2026 Details →