# Next Matter — Workflow Management

Next Matter by Next Matter GmbH holds a panel rating of 2.5/5 from 6 AI judges (category median 2.5/5), as of 2026-11-11. Provenance: provenance unknown; sovereignty: 1 of 6 dimensions proven.

- Vendor: Next Matter GmbH (https://www.nextmatter.com)
- Category: [Workflow Management](https://whats-best.ai/software/workflow-management.md)
- Provenance (editorial classification): provenance unknown
- Canonical page: https://whats-best.ai/software/workflow-management/next-matter
- Alternatives: https://whats-best.ai/software/workflow-management/next-matter/alternatives ([markdown](https://whats-best.ai/software/workflow-management/next-matter/alternatives.md))
- Data as of: 2026-11-21 · evaluated 2026-11-11 · oldest source captured 2026-11-10

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## 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 [S3]
- Free plan: Not stated on the vendor’s pages as of 10 Nov 2026

## 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

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v2). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The Process Owner | The Integration Engineer | The Operations Analyst | The Head of IT | The Data Protection Officer | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| Process design, forms & approvals | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Connectors, API & on-premise reach | 3.5/5 | 3.5/5 | 3/5 | 3/5 | 3.5/5 | 3/5 |
| Execution, error handling & monitoring | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 |
| Governance, credentials & audit trail | 4/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Hosting options & portability | 2/5 | 1/5 | 2/5 | 2/5 | 1.5/5 | 1/5 |
| European sovereignty | 3/5 | 3/5 | 2.5/5 | 2.5/5 | 2.5/5 | 2.5/5 |
| Pricing transparency | n/r | n/r | n/r | n/r | n/r | n/r |
| **Weighted verdict** | **3/5** | **2.5/5** | **2.5/5** | **2.5/5** | **2.5/5** | **2.5/5** |

### The judges

- **The Process Owner** (v1.0): Runs purchase approvals and invoice release for a 400-person Mittelstand company. Wants approvers set by role rather than by name, a substitute when someone is on holiday, deadlines that escalate, and a process change that does not break the forty requests already in flight.
- **The Integration Engineer** (v1.0): Wires the ERP to the shop, the shop to DATEV and the CRM to everything else. Wants connectors documented by action rather than counted in logos, a generic HTTP step for the rest, an on-premise agent that reaches the SQL server without a hole in the firewall, and a failed run replayable from the step that failed.
- **The Operations Analyst** (v1.0): Is asked every Monday why invoices took eleven days. Wants a searchable execution history, cycle times per step, alerts that reach a channel rather than an unread mailbox, runtime and throughput limits published before the month-end run hits them — and to know what a loop over 5,000 rows costs in tasks.
- **The Head of IT** (v1.0): Answers for every automation a department builds without asking. Wants SSO, separate test and production, an inventory of workflows with their owners — and an exit: definitions exportable as BPMN or documented JSON, a self-hosted edition, and an engine licence that will still apply in five years.
- **The Data Protection Officer** (v1.0): Reads every workflow as a chain of transfers. Asks where the execution log keeps its copy of the payload and for how long, which subprocessors and AI model providers a step sends data to, whether payloads can be masked, and what the approval trail records about employees before the works council asks.
- **The Skeptic** (v1.0): Knows that "7,000 integrations" counts connectors nobody maintains, that "unlimited workflows" says nothing about the tasks each run consumes, and that "no-code" ends at the first API without a connector. Reads for what counts as a task, how long failed runs are kept, which model an "AI agent" step sends data to, and whether the workflows can leave the platform at all.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: 1 of 6 dimensions proven.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Not determined | — | — |
| Hosting location | Not determined | — | — |
| Hosting options | EU region selectable | 1/1 | [S3] |
| Open source | Not determined | — | — |
| Data processing agreement | Not determined | — | — |
| Transfer impact assessment | Not determined | — | — |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Compliance**
- Audit rights: yes · not more than once a year · yes [S2]
- Certifications: Site displays 'CERTIFIED SECURE' label without naming certifications [S8]
- DPA: yes [S4]
- DPA GDPR art28: yes [S2]
- DPA updated: 2026-08-13 [S2]
- EU scc transfer: yes [S2]
- GDPR DPA: yes · on request [S3]
- GDPR scope: GDPR · Irish Data Protection Act 2018 · ePrivacy Directive 2002/58/EC · Irish DPC guidance [S2]
- Governing law: England and Wales [S2]
- Security review materials: yes [S3]
- SOC 2 type2: yes · under NDA · annual [S3]
- Subprocessor contract flowdown: yes [S2]
- Toms art32: yes · Confidentiality · Integrity · Availability · Other [S2]

**Data**
- Access log retention: 3 [S2]
- Access termination check: yes [S2]
- Backup retention: daily · 14 [S2]
- Breach notification: yes [S2]
- Erasure return: yes [S2]
- Special categories: yes [S2]

**Hosting**
- Data residency: EU · US · yes [S3]
- Primary region: eu-central-1 · Frankfurt, Germany · AWS [S2]
- Tenant isolation: logical isolation · yes [S3]

**Integrations**
- API rest: yes [S4]
- API webhooks: REST · GraphQL · event-driven · yes [S3]
- Bi etl pipeline: BI/ETL pipeline integration into warehouse or data lake [S6]
- Custom: yes [S4]
- Custom API: Custom integrations to anything with an API [S6]
- Custom auth example: Custom connector auth example: OAuth2.0 with read:data and write:audit scopes [S6]
- Custom connector lead time: Custom API connectors activated in a matter of days [S6]
- Data pipeline: yes [S4]
- Docusign: yes [S6]
- Evidence pack export: GRC tooling · PDF · CSV · API [S8]
- Fund admin fin serv: Fund admin & fin-serv integrations: eFront, Paxus, Canoe, OCR, Plaid, Mercury [S6]
- Integration surface: Airtable · Amazon Redshift · Asana · Azure Event Hubs · Box · DHL · Docusign · Front · Freshdesk · GIPHY · Google · HubSpot · Intercom · Jira · Mailchimp · Microsoft · Notion · Nutshell · PostgreSQL · Sendgrid · Slack · Smartsheet · Twilio… [S7]
- Microsoft teams: yes [S6]
- Native app count: 72+ · 1,000+ [S6]
- New shipments cadence: New integrations shipped every month [S6]
- No code: No-code integrations via predefined templates [S6]
- Power automate: yes [S6]
- Quickbooks: yes [S6]
- Redshift: yes [S6]
- Salesforce: yes [S6]
- Sap ERP: yes [S6]
- Secure API bridge encryption: Secure API Bridge with enterprise-grade encryption for all data transit [S6]
- Slack: yes [S6]
- Triggers: Webhook, recurring, and more [S4]
- Webhook dynamic list: use webhook list variables as dynamic dropdown source using [*] syntax [S7]
- Webhook payload method: POST call to Next Matter webhook URL [S7]
- Workday: yes [S6]
- Xero: yes [S6]
- Zapier: yes [S6]
- Zendesk: yes [S6]

**Legal**
- Copyright entity: Daizy NM Ltd, a Daizy company [S6]
- DPA: yes [S8]
- DPA contact: responsible sales or success manager · yes [S2]
- DPA entity: Daizy NM Limited · 6 Mount Street Upper, Dublin D02 VF44, Ireland [S2]
- DPA link: Terms of Service · Privacy Policy · Data Processing Agreement [S3]
- Entity: Daizy · Daizy NM Ltd [S3]
- Entity: Daizy · Daizy NM Ltd [S4]
- Entity: Daizy · Daizy NM Ltd [S8]
- Entity name: Daizy NM Limited [S1]
- Entity name: Daizy NM Limited [S2]
- Entity name: Daizy NM Limited [S3]
- Entity name: Daizy NM Limited [S4]
- Entity name: Daizy NM Limited [S6]
- Entity name: Daizy NM Limited [S8]
- No retention right: yes [S2]

**Product**
- AI agents: AI agents are part of the governed execution layer [S1]
- AI builder: yes [S4]
- AI model integration: AI models, custom apps, tools and databases integrated directly into workflows [S6]
- AI models used: Example uses GPT-4.1 for extraction [S8]
- Approvals four eyes: Maker-checker, four-eyes and delegated approvals per step [S8]
- Audit logs: yes [S3]
- Audit pack contents: run history · approval chains · policy diffs · model & prompt cards · data lineage [S8]
- Automation templates: yes [S4]
- Batch launch: yes [S4]
- Branching nesting: yes [S4]
- Builder assistant: yes [S4]
- Built in roles: Task Admin · Workflow lead · Instance lead · Team lead · Colleague · Light user [S9]
- Changelog: yes [S4]
- Changelog granularity: Changelog records each individual change as a line [S5]
- Changelog tab: yes [S5]
- Conditional logic: yes [S4]
- Conversations widget: yes [S9]
- Custom roles enterprise: Enterprise · yes [S9]
- Custom roles nav hiding: yes [S9]
- Dashboards: yes [S4]
- Data model lineage: Data and model lineage tracing AI outputs to inputs, sources, model version and prompt [S8]
- Delete version limits: yes · no [S5]
- Discard changes: yes [S5]
- Drag drop builder: Drag-and-drop workflow builder combining human tasks, system automations and database interactions [S4]
- Dual authorization: yes [S3]
- Duplicate version control: no [S5]
- Encrypted payload handling: yes [S3]
- External workspaces: yes [S3]
- Forms: yes [S4]
- Governance audit: yes [S4]
- Guest interfaces: yes [S4]
- Human in the loop example: AI-driven capital call example shows two-step maker-checker human sign-off with full logging [S8]
- Immutable audit trail: Immutable/tamper-evident audit trail capturing inputs, outputs, model versions, approver identity and run-time policy [S8]
- Integration permission: Only Task Admin can connect and disconnect an integration [S9]
- Integration stack: yes [S1]
- Invite colleagues permission: Only Task Admin can invite colleagues [S9]
- Lead change limitation: New workflow lead cannot stop or delete pre-existing instances [S9]
- MFA: yes [S3]
- Permission group mapping: Company > Roles [S9]
- Platforms: Web [S1]
- Portals: yes [S4]
- Public forms: yes [S4]
- Published version instance behavior: Instances started after publication use the new version; earlier instances keep the previous version [S5]
- Rbac SSO: Fine-grained RBAC mapped to SSO groups, least-privilege default, access decisions logged [S8]
- Reviews approvals: yes [S4]
- Role page controls nav: yes [S9]
- Roles page URL: Company > Roles [S9]
- Rollback interrupts instances: no [S5]
- Routing: yes [S4]
- Salesforce integration: yes [S4]
- Sandbox: yes [S4]
- Security controls page: Separate security controls page offered [S8]
- Self demotion warning: Admin demotion is irreversible without help [S9]
- Shared view: One shared view for ops, compliance and IT [S1]
- SSO SCIM rbac: SAML · OIDC · 2.0 · workflow and step level [S3]
- Team interfaces: yes [S4]
- Team lead assignment permission: Only Task Admin can assign or remove team lead status [S9]
- Team permissions location: Company > Teams [S9]
- Version control: yes [S4]
- Version control permissions: admin · workflow lead [S5]
- Versioned workflows: Versioned workflows, policies and prompts; run diffing and historic replay [S8]
- Webhook disable data deletion: deletes all webhook data; dependent variables show as broken [S7]
- Webhook test: test webhook to populate response body and variables dropdown [S7]
- Webhook triggers: Start a workflow based on triggers from external apps via webhook [S7]
- Webhook variable custom: yes [S7]
- Webhook variable extraction: extract variables from webhook response payload for use in later workflow steps [S7]
- Workflow leads change permission: Only Task Admin can change workflow leads [S9]
- Workflow versioning: yes [S5]
- Zendesk integration: yes [S4]

**Subprocessors**
- Change notice: yes · 30 · 90 · yes [S2]

**Support**
- Certified partners: yes [S4]
- Expert onboarding: yes [S4]

## Questions

### 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](https://whats-best.ai/evidence/23794).

### 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)](https://whats-best.ai/software/workflow-management/camunda), [FireStart (3/5)](https://whats-best.ai/software/workflow-management/firestart) and [Appian (3/5)](https://whats-best.ai/software/workflow-management/appian) 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](https://whats-best.ai/software/workflow-management/camunda) (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [Next Matter alternatives](https://whats-best.ai/software/workflow-management/next-matter/alternatives).

## What this page leaves out

- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.

## Sources

- [S1] Vendor page: https://www.nextmatter.com (checked 2026-11-10)
- [S2] Data processing agreement (dpa) — found from the homepage: https://nextmatter.com/data-processing-agreement (checked 2026-11-10)
- [S3] Security / trust page — found from the homepage: https://nextmatter.com/security (checked 2026-11-10)
- [S4] Process design, forms & approvals — found from sitemap: https://nextmatter.com/workflow-builder (checked 2026-11-10)
- [S5] Process design, forms & approvals — found from sitemap: https://help.nextmatter.com/docs/workflow-versions (checked 2026-11-10)
- [S6] Connectors, API & on-premise reach — found from sitemap: https://nextmatter.com/integrations (checked 2026-11-10)
- [S7] Connectors, API & on-premise reach — found from sitemap: https://help.nextmatter.com/docs/webhook-triggers (checked 2026-11-10)
- [S8] Governance, credentials & audit trail — found from sitemap: https://nextmatter.com/governance-and-audit (checked 2026-11-10)
- [S9] Governance, credentials & audit trail — found from sitemap: https://help.nextmatter.com/docs/team-permissions (checked 2026-11-10)

---

Cite as: whats-best.ai, "Next Matter — Workflow Management", AI panel analysis, as of 2026-11-21. https://whats-best.ai/software/workflow-management/next-matter

Corrections: https://whats-best.ai/correct/1899?target=page
