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
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
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Boomi's case rests on integration depth. Integrations and connectors scores run 6-8, the strongest criterion, on an SAP connector documented down to IDocs in both directions, table and function-module services, BW extractors and event-subscription listening, plus 1000+ prebuilt connectors and an execution-query API. Process design is the contested weak point, 2-4: lower scores hold that the documented approvals govern API Developer Portal subscriptions rather than human steps inside a process, while higher scores credit point-in-time packaged versions and in-flight executions completing on their original version. Sovereignty scores sit at 3 with no spread — the contracting entity is Boomi, LP of Conshohocken, Pennsylvania, transfers rest on the EU-US Data Privacy Framework with standard contractual clauses where no adequacy decision applies, and judges found no public information on where workflows execute or logs are stored. Run reliability spans 5-7 and governance and audit holds at 6, crediting disciplined retries but noting audit logs kept 30 days for Enterprise-plan customers only. The self-hosted runtime is Early Access 'as is'. Judges found no public prices; a free trial and the Enterprise plan appear.
Speaks for it
- The SAP connector is documented in depth, covering IDocs in both directions, table and function-module services, BW extractors and event-subscription listening
- Integrations and connectors scores reach 8, the highest score on the bench
- Failed documents rerun automatically under retry schedules with a configurable maximum, each retry kept as a separate execution linked to its failed original
- Deployments create point-in-time packaged versions, and in-flight executions complete on the version they started with
- Secrets can be held in AWS, Azure Key Vault or GCP and referenced rather than revealed
Held against it
- Sovereignty scores sit at 3 with no spread
- Audit logs are kept for 30 days and are available to Enterprise-plan customers only
- The documented approvals govern API Developer Portal subscriptions, and we found no public information on forms, task inboxes, deadlines or escalation inside processes
- The self-hosted Kubernetes runtime is an Early Access program offered 'as is' with no warranties and needs outbound HTTPS to platform.boomi.com and ghcr.io
- We found no public information on exporting workflow definitions, the engine's licence, or a migration path between cloud and self-hosted
Best for
- You run a SAP-centric estate and need documented IDoc, function-module, table-service and BW-extractor connectivity
- Your team builds machine-to-machine integrations and needs versioning where in-flight executions complete on their original version
- You need execution behind your own firewall and can accept a runtime that still calls platform.boomi.com for registration and lifecycle
- Your security posture requires secrets held in your own AWS, Azure Key Vault or GCP stores
Avoid if
- Your workflows need participant-facing approval steps — the documented approvals instead govern API Developer Portal subscriptions, with no public information on forms, task inboxes or escalation
- You must evidence EU execution and EU log storage — the contracting entity is Boomi, LP of Pennsylvania and we found no public information on where workflows or logs are stored
- You need a production-grade self-hosted exit — ask the vendor: the public pages we read do not show it
- You need an audit trail beyond 30 days — audit logs are kept 30 days and are available to Enterprise-plan customers only
The scores
| Criterion | Panel median |
|---|---|
| Process design, forms & approvals | 2 of 5 |
| Connectors, API & on-premise reach | 3.5 of 5 |
| Execution, error handling & monitoring | 3 of 5 |
| Governance, credentials & audit trail | 3 of 5 |
| Hosting options & portability | 3 of 5 |
| European sovereignty | 1.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
The only human approvals documented are developer-portal API subscriptions — publishers approve or reject subscription requests under modes such as ALL or RESTRICTED — and I found no public information on forms, approvers assigned by role, substitutes, deadlines or escalation chains. What won me partway over is deployment versioning: packaged point-in-time versions, and when a new version is deployed, in-progress executions complete on the previous version, so a change would not break the requests I already have running. Test execution types appear in the API, but nothing on a task inbox for participants. 3 4 12 8
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
The Operations Analyst
The approvals captured govern API subscriptions in a developer portal — who may subscribe and whether an administrator signs off — not approval steps inside a running workflow. Deployment itself is documented well: a new version replaces the old while executions in flight finish on the version they started with, and packaged versions stay isolated from later build changes. We found no public information on forms, deadlines, escalation chains or a task inbox for participants. 3 4 12
The Head of IT
Point-in-time packaged versions, deliberate deployment to test or production, in-flight executions finishing on their original version and an audit history of versioning are exactly what I want to see. The documented approvals, however, gate API Developer Portal subscriptions rather than steps inside a process, and I found no public information on forms, a participant task inbox, deadlines, substitutes or BPMN modelling. 3 4 12
The Data Protection Officer
The documentation shows a configurable approval workflow for API subscription requests — four approval modes, automatic-approval options for requests from inside the organisation, and a screen where publishers approve or reject — and process versions deployed as point-in-time packages whose in-flight executions complete on the original version. As a record of who requested and who granted access that trail exists, but we found no public information on participant-facing forms, a task inbox, deadlines, substitutes or escalation chains, or a notation such as BPMN. 3 4 12
The Skeptic
The approvals documented are API subscription approvals — admin-configurable modes and an approve/reject screen for Developer Portal requests — not human approval steps with forms, roles, substitutes, deadlines or escalation inside a running process. Process versioning is genuinely handled: deployments create point-in-time packaged versions and in-flight executions complete on the original version. We found no public information on process forms, reminders or a task inbox for participants. 3 4 12
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
SAP is documented in real depth — table services, function-module CRUD, IDocs in both directions, and event-driven listening via SAP event subscriptions — alongside named connectors for Salesforce, NetSuite, ServiceNow and AWS, Postgres among the data targets, and a runtime that runs behind the firewall. The platform API can query execution records, and API usage is governed by a license and rate limits. I found no public information on DATEV, SOAP steps, connector changelogs or who maintains each connector. 1 5 6 8
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
The Operations Analyst
The SAP connector is documented down to operations — IDocs in, function modules, table and BW extracts, and event-based listening on SAP subscriptions — with named connectors to Salesforce, NetSuite, ServiceNow and AWS and data targets from Postgres to Snowflake. A runtime behind the customer firewall is offered, and the platform API lets me query execution records and page through results. Rate limits are only referenced by name, and we found no public information on connector maintenance ownership or DACH accounting connectors such as DATEV. 1 5 6 8
The Head of IT
The SAP connector is documented at the depth I need for a DACH estate — IDocs in and out, table and function-module services, BW extractors, event-based Listen on SAP event subscriptions and OpenAPI-generated interfaces — alongside named connectors for Salesforce, NetSuite, ServiceNow and AWS, database targets, and a self-hosted Kubernetes runtime behind the firewall. I found no public information on SOAP steps, DATEV, ELO or d.velop connectors, or who maintains each connector. 1 5 6 11
The Data Protection Officer
The SAP connector is documented in depth — table services, function module services, IDocs in both directions, BW extractors and event subscriptions through a web server — alongside Salesforce, NetSuite, ServiceNow and AWS among 1000+ prebuilt connectors, an execution-query API with paging, authenticated web-service run requests, and the vendor's statement that you can run anywhere, including behind your firewall, with a locally installed runtime implied by an installation directory holding error files. We found no public information on connectors to Microsoft 365 or Google Workspace, DATEV, ELO or d.velop, on connector changelogs, rate limits per connector, a deprecation policy, or who maintains each connector. 1 5 6 7 8
The Skeptic
The SAP connector is documented in real depth — IDocs, Table Services, Function Module Services, BW Extractors and event listeners against NetWeaver 7.31+ — alongside named connectors and an execution-query API with paging, async polling and referenced rate limits. Reaching behind the firewall is claimed, and a self-hosted Kubernetes runtime is documented, but it sits in an Early Access program 'as is' with no warranties and must call platform.boomi.com for registration and lifecycle. We found no public information on DATEV connectors, connector maintenance ownership, or a generic HTTP step. 1 5 6 8 11
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
Retries are documented properly: automatic retry schedules with a maximum retry count, failed documents rerun even from past executions, a separate retry execution per failed run, and the original run stays marked as failed even when the retry succeeds. The execution record exposes status, duration in milliseconds, error messages and document counts through a query API, and a system status page exists. I found no public information on failure alerts by email or chat, retry back-off, or how long execution history is retained per plan. 7 8 6
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
The Operations Analyst
Retry schedules are documented properly: failed documents rerun automatically with a configurable maximum, each failed run gets its own retry, and the original stays red with an icon linking to the retry — exactly what I want after a bad month-end. The execution-record API exposes status, duration in milliseconds and document counts including errors, queryable and paged, and a status page exists. We found no public information on failure alerting to email or chat, on runtime or throughput limits, or on execution-history retention. 6 7 8
The Head of IT
Retry schedules with a configurable maximum, one retry execution per failed original, tracking fields linking retries to their parent, and a documented Execution Record API with statuses, durations and error counts are solid. But the status page is only named with no incident history or uptime commitment shown, and I found no public information on failure alerting by email or chat, retry back-off, retention per plan, or queueing and concurrency controls. 6 7 8
The Data Protection Officer
Failed documents rerun automatically under retry schedules with a configurable maximum, each retry kept as a separate execution linked back to an original that stays marked as failed, and an execution-record API exposes status, duration in milliseconds, inbound and outbound document counts and error messages, with paging and a documented API rate-limit policy. A status page is linked, but we found no public information on retry back-off, execution-data retention, queueing and concurrency controls, an uptime commitment or incident history — the only retention figure we found anywhere is 30 days, and it applies to audit logs. 6 7 8 9
The Skeptic
Retries are properly engineered: maximum retries configurable, failed documents rerun even from past executions, one retry execution per original, the original stays marked failed, and linking back to it is visible in process reporting. An execution-record API exposes statuses including ERROR and ABORTED with durations and per-document error counts, and a system status page exists. We found no public information on failure alerts, back-off between retries, execution-history retention per plan, or an uptime commitment. 6 7 8
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
Deployments are assigned to test or production environments, audit logs record who did what with filters by user, event type and entity type, and secrets can be held in AWS, Azure Key Vault or GCP and referenced rather than revealed. As someone who answers to a works council, I note the audit trail is kept for 30 days and is available to customers on the Enterprise plan only. I found no public information on single sign-on, SCIM provisioning, a publishing approval step, or certifications such as ISO 27001. 9 10 12 3
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
The Operations Analyst
Audit logs record who performed an action, what it was and how the system responded, filterable by user, event, entity and date — but only on the Enterprise plan, held 30 days, and we found no export option. Credentials can be referenced from AWS, Azure Key Vault or GCP without exposure, privileges such as viewing execution results indicate role-based control, and test and production environments with packaged deployments are documented. We found no public information on SSO, SCIM, payload redaction or configurable execution-data retention. 8 9 10 12
The Head of IT
Separate test and production environments with deliberate packaged deployments, audit logs attributing who did what with a stated 30-day retention, and secrets held in AWS, Azure Key Vault or GCP rather than with the vendor cover most of my checklist. The audit log sits behind the Enterprise plan, and I found no public information on single sign-on, SCIM provisioning, an exportable audit trail, or payload redaction — points a works council will raise. 8 9 10 12
The Data Protection Officer
Audit logs record who performed an action, what action and how the system responded, filterable by user, date range, event type and object type including user-management events such as deleted users — but they are kept for 30 days and only for Enterprise-plan customers, which is thin for an approval trail that doubles as a record of employees' behaviour before a works council. Secrets can live in external stores (AWS, Azure Key Vault, GCP) and be referenced rather than revealed, and processes run in test or production environments with audit history for versioning and deployments; we found no public information on single sign-on, SCIM provisioning, masking or redaction of payloads in logs, configurable execution-data retention, or export of the audit trail. 8 9 10 12
The Skeptic
Audit logs filter by user, event type, entity type and date range, track user-management activity, keep 30 days, and require the Enterprise plan; secrets can live in external stores (AWS, Azure Key Vault, GCP) referenced from the platform. Deployment to test or production through packaged point-in-time versions is documented with full audit history for versioning and deployments. We found no public information on SSO, SCIM provisioning, audit-trail export or payload redaction. 8 9 10 12
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
A self-hosted runtime is documented down to Kubernetes version, node architecture and NFS storage requirements, runs on any conformant cluster including bare metal, pulls public images from GitHub, and no private key is ever handed to Boomi — but it is explicitly an Early Access program offered as-is with no warranties. The cluster still needs outbound HTTPS to the vendor's platform and to ghcr.io. I found no public information on an EU cloud region, export of workflow definitions in a documented format, the engine's licence, or a migration path between cloud and self-hosted. 11 12 8 1
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
The Operations Analyst
Flex Runtime is documented to run on any conformant Kubernetes — cloud-managed, self-managed or bare metal — with node architecture, storage, ingress and TLS requirements spelled out, non-root pods, and public images needing no registry credentials. Two caveats bite: it is an Early Access offering explicitly not for production use, and the cluster must open an outbound line to platform.boomi.com for registration and lifecycle commands. We found no public information on Git versioning of workflow definitions, the engine's licence, or a documented migration path between cloud and self-hosted. 1 11 12
The Head of IT
A self-hosted runtime with documented Kubernetes requirements that runs self-managed or on bare metal, behind our firewall, with publicly pullable images and no private key handed over is the right direction. But it is an Early Access program explicitly not for production use, it still calls out to platform.boomi.com for registration and lifecycle, and I found no public information on exporting definitions as BPMN or documented JSON, Git versioning, the engine's licence, or a cloud-to-self-hosted migration path — the exit I need is not evidenced. 1 8 11 12
The Data Protection Officer
A Kubernetes-based runtime can run on any conformant cluster — self-managed, bare metal or any cloud — with documented system requirements, public images, non-root pods, end-to-end TLS options and no private key handed to the vendor, though it is Early Access with no warranties and still requires outbound calls to the vendor's platform for registration, configuration and lifecycle commands. We found no public information on export formats for workflow definitions, the engine's licence, version control integration, or a documented migration path between cloud and self-hosted in either direction. 1 7 8 11 12
The Skeptic
A self-hosted Kubernetes runtime is documented down to storage class, node architecture and non-root pods, with publicly pullable images — but it is Early Access 'as is' with no warranties, and the cluster must reach platform.boomi.com for runtime registration and lifecycle commands. Execution history is queryable by API, yet we found no public information on exporting workflow definitions as JSON or BPMN, Git versioning of definitions, the engine's licence, or a documented migration path between cloud and self-hosted. 8 11 12
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 contracting entity is Boomi, LP of Conshohocken, Pennsylvania, certified under the EU-US Data Privacy Framework and committing to standard contractual clauses where no adequacy decision applies, with an EU representative (Boomi BeNeLux B.V.) and a published sub-processor list URL. I found no public information on where workflows execute or where execution logs with their payloads are stored. Even the self-hosted runtime reports to the vendor's platform for registration and lifecycle commands. 2 11
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
The Operations Analyst
The contracting entity is Boomi, LP of Conshohocken, Pennsylvania, with an EU representative appointed, a published subprocessor-list address, and transfers carried by the Data Privacy Framework with standard contractual clauses as fallback. EU execution and EU log storage are not shown on the captured pages. The self-hosted runtime keeps private keys on the customer side but still calls the vendor's platform for registration, configuration and lifecycle commands. 2 11
The Head of IT
The contracting entity is Boomi, LP of Conshohocken, Pennsylvania, under FTC enforcement, with an EU representative in Boomi BeNeLux B.V., Data Privacy Framework certification and standard contractual clauses where no adequacy decision applies — a US-first posture with an EU touchpoint, not EU execution. The captured pages give no location for execution or log storage beyond a published subprocessor list address, and the self-hosted runtime still reaches platform.boomi.com outbound. 2 11
The Data Protection Officer
The contracting entity is Boomi, LP of Conshohocken, Pennsylvania, with an EU representative appointed (Boomi BeNeLux B.V.), standard contractual clauses for transfers without an adequacy decision, Data Privacy Framework certification, and a subprocessor list published at a named web address. We found no public information on where workflows execute or where execution logs and their payload copies are stored, on subprocessor locations including any AI model providers, or on a data processing agreement covering execution payloads — and the self-hosted runtime still calls home to the vendor's platform for registration and lifecycle commands. 2 11
The Skeptic
The contracting entity is Boomi, LP of Conshohocken, Pennsylvania, relying on the EU-US Data Privacy Framework and standard contractual clauses, with a US-based dispute-resolution provider and FTC enforcement; Boomi BeNeLux B.V. is appointed EU representative and a subprocessor list URL is published. We found no public information on where workflows execute or execution logs are stored, and no data processing agreement on the captured pages. The self-hosted runtime still calls home to the vendor's platform, though the vendor states no customer private key is ever handed over. 2 11
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
I found no public prices at all — the captured pages offer a free trial and mention that audit logs require the Enterprise plan, but no tier is priced, no billing unit is named, and no allowance or overage is stated. A buyer cannot begin to compute a monthly cost for their own processes from these pages. 1 6 9
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
The Operations Analyst
We found no public prices in anything captured — no tier prices, no billing unit, no allowance per plan, no overage. The only pricing-adjacent facts are a free trial and that audit logs require the Enterprise plan, which reveals a plan structure but not what anything costs. A buyer cannot compute a monthly cost from these pages. 1 9
The Head of IT
The captured pages name a free trial and an Enterprise plan — audit logs are gated to it — but show no price, billing unit, allowance or overage for any tier. I cannot compute our monthly cost from what is public here. 1 6 9
The Data Protection Officer
The captured pages offer a free trial and name an Enterprise plan only indirectly through feature gating, but we found no public information on prices for any tier, on the billing unit and what counts as one, on allowances, or on overage and add-on figures. A buyer cannot compute a monthly cost from public pages alone. 1 6 9
European sovereignty — proven facts
0 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 | — | uncited Report an error |
|---|---|---|---|
| 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
- 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.
- 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.
- 2 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
- 2 support 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 compliance 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 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 legal 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 (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.boomi.com Checked 10 Nov 2026 Details →
- 2 Privacy policy — found from the homepage boomi.com Checked 10 Nov 2026 Details →
- 3 Process design, forms & approvals — found from sitemap help.boomi.com Checked 10 Nov 2026 Details →
- 4 Process design, forms & approvals — found from sitemap help.boomi.com Checked 10 Nov 2026 Details →
- 5 Connectors, API & on-premise reach — found from sitemap help.boomi.com Checked 10 Nov 2026 Details →
- 6 Connectors, API & on-premise reach — found from sitemap boomi.com Checked 10 Nov 2026 Details →
- 7 Execution, error handling & monitoring — found from sitemap help.boomi.com Checked 10 Nov 2026 Details →
- 8 Execution, error handling & monitoring — found from sitemap developer.boomi.com Checked 10 Nov 2026 Details →
- 9 Governance, credentials & audit trail — found from sitemap help.boomi.com Checked 10 Nov 2026 Details →
- 10 Governance, credentials & audit trail — found from sitemap help.boomi.com Checked 10 Nov 2026 Details →
- 11 Hosting options & portability — found from sitemap help.boomi.com Checked 10 Nov 2026 Details →
- 12 Hosting options & portability — found from sitemap help.boomi.com Checked 10 Nov 2026 Details →