Boomi Integration editions and connection licensing are the rules under which Boomi sells its integration platform as a service (iPaaS), formerly branded AtomSphere. A customer subscribes to an Integration edition. The edition sets the features and includes a number of connection licences, and more licences can be bought by connector class.[1] A connection licence is consumed when a process is deployed to a runtime, not when it is built. The general rule is “one license per unique connection per runtime”.[2] Processes on Boomi-hosted public runtime clouds also use a monthly data volume allowance.[8]
The Service Description defines a Connection as “one connection end-point to a database, application, or API for use in an integration process created within the Boomi Integration Platform”. It defines a Connector as the code that connects to “one instance of an application, database or file format”.[8]
Editions
Boomi describes its subscription tiers as Integration Editions: a Personal Edition for the 30-day trial, then Base, Professional, Professional Plus, Enterprise and Enterprise Plus.[1] The Personal Edition can build and test any number of processes and connections. Scheduling, deployment to basic runtimes, execution history and access to clouds are locked, and a test-mode execution is limited to 100 documents or 10 MB.[1]
The editions page publishes this matrix. In the connector rows the figures are production/test. A ”($)” marks a feature available at extra cost.[1]
| Feature | Base | Professional | Professional Plus | Enterprise | Enterprise Plus |
|---|---|---|---|---|---|
| Standard connectors | 2 / none | 5 / 5 | 7 / 7 | 10 / 20 | 15 / 30 |
| Enterprise connectors | No | ($) | ($) | 1 / 2 | 2 / 4 |
| Runtime clusters | No | ($) | ($) | 2 | 2 |
| Runtime cloud attachments | No | 1 / 1 | 1 / 1 | 2 / 2 | 2 / 2 |
| Execution workers | No | ($) | 1 / 1 | 2 / 2 | 2 / 2 |
| Advanced Workflow | No | Yes | Yes | Yes | Yes |
| Services Enablement | No | ($) | Yes | Yes | Yes |
| Parallel processing, advanced security | No | ($) | ($) | Yes | Yes |
| Message queuing | No | ($) | ($) | ($) | Yes |
| Enhanced Support | No | ($) | ($) | ($) | ($) |
All editions include the standard features, the Boomi AI Starter Pack and Basic Support. Base Edition includes “only Production environments”.[1] The public pricing page groups the same tiers. It describes Professional as “Eligible for enterprise connectors (extra cost)” and Enterprise as including “More connections including enterprise connections” and clustered runtime support.[9] Boomi also offers editions for the Trading Partner step, EDI and B2B through the account representative.[1] No edition price is published.
Metrics
- Connection: “Each license represents one unique connection per runtime, identified by its component ID.”[2]
- Connector classes: licences are “organized and provisioned by connector classes: Small Business, Standard, Enterprise, and Trading Partner”.[2] The Standard class covers most connectors, for example SFTP, Disk, Mail, Salesforce, NetSuite, HTTP Client and Oracle Database. The Enterprise class covers a small set such as SAP, Oracle E-Business Suite, SAP JCo, ServiceNow REST and Workday. QuickBooks and Sage 50 are Small Business connectors. Each trading partner component counts as one Trading Partner licence, “regardless of how many communication types it includes”.[2]
- Test connection: a separate licence pool for each class, used by processes in test environments.[3]
- Runtime cloud data volume: the data processed on Boomi public runtime clouds, measured in GB per month.[8]
The class decides which pool a licence is counted in, not how it works. With five Standard licences a customer could deploy “three Salesforce, one Disk, and one FTP connection”.[2]
Counting / floors
The Licensing page sets out the counting rules with worked examples.[2]
| Scenario (from Boomi’s examples) | Licences |
|---|---|
| One process, 2 unique connections, environment with 1 basic runtime | 2 |
| Two processes sharing the same 2 connections, 1 basic runtime | 2 |
| One process, 2 unique connections, environment with 2 basic runtimes | 4 |
| One process, 2 unique connections, runtime cluster of 3 nodes | 2 |
| Fifty processes using 3 unique connections, 1 basic runtime | 3 |
| Process with 2 connections plus a test copy whose connections got new component IDs, 1 runtime cluster | 4 |
Connections in the Build tab are not counted, because “License calculation only occurs upon deployment.”[2] The most common cause of over-deployment in these examples is copying a process together with its connections. The copies receive new component IDs and count as new licences, unless the copied process is pointed back at the original connection components.[2]
Some connectors never use a licence. They can be deployed “an unlimited number of times across different runtimes and environments”. The list includes the AS2 Shared Server, AtomSphere API, AtomSphere Partner API, Atom Queue, Boomi for SAP, Boomi Data Hub, Master Data Hub, Boomi MFT, Event Streams, Flow Services Server, MLLP Server, OFTP2 Server and Web Services Server connectors.[2]
Enforcement and reporting
The License Enforcement account feature lets an administrator “Enable or disable deployment locking when your account has met the available connection count limit.”[4] When enforcement is on, a deployment that needs more licences than are available does not finish.[2] When it is off, the Licensing page shows the shortfall as negative numbers (-1, -2, and so on) in the Available column.[3] Those deployments still count as use above the Order, and the MSA lets Boomi bill the difference at its then-current rates.[12]
The Connections tab lists deployed and available connections by class and can export a CSV report per class. The Deployments table lists every connection per process and per runtime, but Boomi notes that it “does not reflect the actual billable connection count”.[3] The newer Usage tab shows purchased against deployed connectors by class, with a table of deployments by runtime.[11]
Test connections
Production connection licences come with every edition. Test connection licences exist only in accounts with environments and test connections enabled. “Environments are available in the Professional, Professional Plus, Enterprise, and Enterprise Plus Editions.”[3] Base Edition customers can test only in Test mode, which limits data size and document count.[3] Accounts created before January 2014 must ask Boomi to enable test connections. Environments created before then are production environments and cannot be reclassified.[3]
Test licences and Test runtimes “should be used for functional testing of processes only” and not for performance testing or benchmarking.[3]
Data volume on Boomi public runtime clouds
Where Boomi hosts the runtime in its public runtime cloud, the platform fees include up to 1 GB “of data processed per Boomi Runtime per month”. Each further GB or fraction is invoiced at USD 117 per month.[8] Usage on the Cloud Usage tab is calculated as “(data in + data out) / 2”. Documents through connector steps count, as do web services listen and return document steps. Connector call lookups inside maps do not count.[2] Executions are not blocked when the allowance is exceeded. Test cloud overage is billed at half the production rate, and the tab does not show dedicated clouds.[2]
Virtualization & partitioning
Integration processes run on runtimes. Boomi’s documentation now uses the terms basic runtime, runtime cluster and runtime cloud for what were called the Atom, Molecule and Atom Cloud. The URLs and installer pages still use the older names.[5]
| Runtime | Description in Boomi documentation | Licence effect |
|---|---|---|
| Basic runtime (Atom) | “A single-tenant, single-node runtime engine.” | Each basic runtime in an environment counts the connections again |
| Runtime cluster (Molecule) | “A single-tenant, multiple-node runtime engine.” | Counted once whatever the number of nodes |
| Runtime cloud (Atom Cloud) | “A multiple-tenant, multiple-node runtime engine.” | Counted per cloud; classified Production or Test when added |
Runtime descriptions are quoted from the Integration runtimes page.[5] Licence effects follow the Licensing page[2] and the Runtime clouds page.[7]
Licensing ignores the machines, CPUs or cores under a runtime. The Licensing page counts “each basic runtime, runtime cluster, or cloud”, so adding nodes to a cluster does not change the licence count.[2] Runtime clusters are an extra-cost option in Professional and Professional Plus and are included in the Enterprise editions.[1]
A private runtime cloud is multi-tenant. A typical use is a Boomi partner sharing it across customer accounts.[7] Its Production or Test classification is set when it is added and cannot be changed later. “The classification also determines which license to use when deploying a process to an environment attached to this runtime cloud.”[7]
Cloud / BYOL
Boomi offers three hosted runtime options. Public Cloud service is multi-tenant “with various tiers to choose from”. Dedicated Cloud service is single-tenant. Managed Cloud service is single-tenant “with custom scaling/sizing and dedicated monitoring and advisory services”.[5] “All accounts include at least one attachment to a Public Cloud (base tier)”. Other hosted options are priced by the account representative.[5] Boomi limits simultaneous executions per account on its runtime clouds and applies further limits on the Test runtime clouds. The number of deployed processes is not limited, “however, cloud usage limits for an account do apply”.[6]
Managed Cloud Services is a subscription under which Boomi builds and runs a private runtime cloud on AWS or Azure across three availability zones. Optional cross-region Disaster Recovery and a Hosted API Gateway Service are available.[10] Customer-hosted runtimes can run in any public cloud or on premises under the same edition, and their traffic does not count toward cloud volume.[2][5]
Programs
Partners who already have “development” or “test” runtimes can ask their partner manager to move them to test connection licences.[3] Edition upgrades are possible at any time, according to the pricing FAQ.[9] Commercial programmes are covered in Boomi licensing.
Out of scope
This article does not cover the usage-based Pay-As-You-Go edition, which has unlimited connections and is metered per message. It also does not cover the AI Platform, Event Streams, Connect and Data Integration metrics. All of these are described in Boomi consumption metering and message tiers.