Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Boomi · www.boomi.com

Report an error on this page Is this your product? →

Link to this page

Boomi: AI-assisted analysis on whats-best.ai Boomi: AI-assisted analysis on whats-best.ai (dark)

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.

Boomi at a glance

Vendor
Boomi
Headquarters
Not stated on the vendor’s pages as of 10 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 10 Nov 2026
Free plan
Not stated on the vendor’s pages as of 10 Nov 2026
Panel verdict
The AI panel rates Boomi 2.5/5, the mean of 6 judges. Boomi's case rests on integration depth. how scores are made
As of
Vendor pages captured 10 Nov 2026; evaluated by the panel 11 Nov 2026. all sources

Boomi alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The Integration Engineer

Weighted verdict

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.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Integration Engineer

Panel median The Integration Engineer This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Integration Engineer
Process design, forms & approvals 2 of 5 1 of 5
Connectors, API & on-premise reach 3.5 of 5 3.5 of 5
Execution, error handling & monitoring 3 of 5 3 of 5
Governance, credentials & audit trail 3 of 5 3 of 5
Hosting options & portability 3 of 5 2.5 of 5
European sovereignty 1.5 of 5 1.5 of 5

Process design, forms & approvals

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.

Report an error

The Integration Engineer

The approvals I can find are API-portal subscription approvals — a screen where publishers approve or reject developer access requests, with configurable approval modes — not human steps inside a designed process. What is documented is machine-to-machine integration with disciplined versioning: point-in-time packaged versions, and in-flight executions finishing on their original version after a new deploy. I found no public information on forms, task inboxes, substitutes or escalation for process participants. 3 4 12

Report an error

Connectors, API & on-premise reach

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.

Report an error

The Integration Engineer

This is where an integration shop breathes: the SAP connector is documented operation by operation — function module create/read/update/delete, IDocs in and out, BW extractors, table and view queries, and a listener on SAP event subscriptions rather than polling — with prerequisites stated. Execution runs on a runtime that sits behind your firewall, including on any conformant Kubernetes distribution or bare metal, and the execution query API is paged with rate-limit governance. I found no public information on a DATEV or other German-market connector, or on who maintains which connector. 1 5 6 8 11

Report an error

Execution, error handling & monitoring

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.

Report an error

The Integration Engineer

Retry behaviour is documented in detail: a retry schedule per process, a maximum-retry setting, failed documents rerunning until they succeed, and each retry execution traceable back to its original, which stays marked red. The execution record API exposes status, duration in milliseconds, per-document counts including errors, and error messages with paging, and a status page is available. I found no public information on back-off behaviour, failure alerts by email or chat, or execution history retention per plan. 6 7 8

Report an error

Governance, credentials & audit trail

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.

Report an error

The Integration Engineer

Audit logs record who did what to which entity, filterable by user, event type, entity type and date range, with a stated 30-day retention — gated to the Enterprise plan. Secrets can live in external stores (AWS, Azure Key Vault, GCP) and environments carry point-in-time packaged versions with audit history for versioning and deployments. I found no public information on SSO, SCIM provisioning, payload redaction, or export of the audit trail. 8 9 10 12

Report an error

Hosting options & portability

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.

Report an error

The Integration Engineer

Execution can genuinely run on the customer's side: behind the firewall on locally installed runtimes, plus a Kubernetes runtime documented to run on managed clusters, self-managed or bare metal with full system requirements — though the captured pages flag that Kubernetes runtime as early access, beta, with no warranties. Packaged point-in-time versions can be shared in the process library or integration packs, and the runtime images are public with no pull credentials. I found no public information on exporting definitions in a documented open format, the engine's licence, or a named cloud region. 1 7 11 12

Report an error

European sovereignty

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.

Report an error

The Integration Engineer

The contracting entity is Boomi, LP in Pennsylvania, USA, subject to FTC enforcement, relying on the Data Privacy Framework certifications with standard contractual clauses as the fallback for transfers; an EU representative in Boomi BeNeLux B.V. and a sub-processor list of affiliates are published. The captured pages give no statement of where workflows execute or where execution logs and their payload copies are stored. 2

Report an error

Pricing transparency not rated — the vendor publishes no price

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.

Report an error

The Integration Engineer

No captured page carries a price: no figures, no billing unit, no allowances, no overage or add-on costs. The only pricing-adjacent facts are a free trial and audit logs being restricted to the Enterprise plan — a buyer cannot compute a monthly cost from the public pages I read. 1 6 9

Report an error

European sovereignty — proven facts

0 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined — uncited Report an error
Hosting options Not determined — uncited 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 Boomi

Is Boomi European?

Not determined: the vendor’s pages as captured do not say where Boomi is based.

Where does Boomi store data?

Not stated on the vendor’s pages as of 10 Nov 2026.

Does Boomi have a free plan?

Not stated on the vendor’s pages as of 10 Nov 2026.

What are the best alternatives to Boomi?

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: Boomi alternatives.

Where this could be wrong

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.

Sources (12)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor page www.boomi.com Checked 10 Nov 2026 Details →
  2. 2 Privacy policy — found from the homepage boomi.com Checked 10 Nov 2026 Details →
  3. 3 Process design, forms & approvals — found from sitemap help.boomi.com Checked 10 Nov 2026 Details →
  4. 4 Process design, forms & approvals — found from sitemap help.boomi.com Checked 10 Nov 2026 Details →
  5. 5 Connectors, API & on-premise reach — found from sitemap help.boomi.com Checked 10 Nov 2026 Details →
  6. 6 Connectors, API & on-premise reach — found from sitemap boomi.com Checked 10 Nov 2026 Details →
  7. 7 Execution, error handling & monitoring — found from sitemap help.boomi.com Checked 10 Nov 2026 Details →
  8. 8 Execution, error handling & monitoring — found from sitemap developer.boomi.com Checked 10 Nov 2026 Details →
  9. 9 Governance, credentials & audit trail — found from sitemap help.boomi.com Checked 10 Nov 2026 Details →
  10. 10 Governance, credentials & audit trail — found from sitemap help.boomi.com Checked 10 Nov 2026 Details →
  11. 11 Hosting options & portability — found from sitemap help.boomi.com Checked 10 Nov 2026 Details →
  12. 12 Hosting options & portability — found from sitemap help.boomi.com Checked 10 Nov 2026 Details →