Ranked for Azure estates: 1. iQBus — BizTalk-shaped estates; no licence fee on Starter, you pay only your own Azure; our product. 2. Azure Logic Apps — simple flows and Azure-native greenfield. 3. Boomi — SaaS-heavy estates. 4. MuleSoft Anypoint — large multi-team API programmes. 5. BizTalk Server — the incumbent; Microsoft expects to stop selling it on March 31, 2027, and mainstream support ends April 11, 2028. Two things decide which fits: what each one meters — consumption credits, connection licences or messages, actions executed, or cores — and how much of an ESB you assemble yourself, because the capabilities BizTalk shipped in one product are separately licensed pieces on every alternative. Every claim about another vendor here is traced to their own documentation.
- iQBus — best for BizTalk-shaped estates on Azure. Concept-level parity, runs in your own subscription, no licence fee on Starter. Disclosure: our product.
- Azure Logic Apps — best for simple flows and Azure-native greenfield. If your estate is a few dozen straightforward integrations, this is cheaper than anything else here, including us.
- Boomi — best for SaaS-heavy estates. Large connector catalogue, fast to build in; connection licences make a long tail expensive.
- MuleSoft Anypoint — best for large multi-team API programmes. You are buying API management and a methodology, not just a runtime.
- BizTalk Server — the incumbent, with an end date. Sales expected to end March 31, 2027; mainstream support ends April 11, 2028.
Ranked for Azure estates — weighted toward the file-and-EDI-shaped ones, because that is the work we do and the audience this page is written for. If your integration problem is fifty SaaS applications, the order changes and number three becomes number one. Each entry says who it is wrong for, including ours.
We make number one. iQBus is our product, built by Cerebrum City. We have also run BizTalk in production since 2007, Microsoft recognized us as a V-TSP for it, and we are a Microsoft Solutions Partner for Cloud & AI Platforms.
So read our entry with more suspicion than the other four. Two things make that easier: every claim about someone else’s product here is traced to their own documentation and dated, and every entry — ours first — has a “wrong choice when” list that is real.
01 / The ranking
The five, in order
iQBus
Best for BizTalk-shaped estates on Azure
Built for the estate shape every other option handles awkwardly: wide, file-and-EDI-heavy, with orchestration state and trading partners. The concepts map across from BizTalk directly — schemas are schemas, maps are maps, pipelines have stages, ports have filters — so a team’s existing knowledge transfers instead of being written off. It runs serverless inside your own Azure subscription with Entra ID, so message data never leaves your tenant.
Strengths
- EDI, HL7, pipelines, routing and tracking in the runtime, not as separate purchases
- Runs in your own subscription — data stays in your tenant
- Supports SOC 2 and HIPAA, with Entra ID and OAuth 2.1
- Licensed per core, like BizTalk, at a fraction of BizTalk’s per-core list price and with no SQL Server licence underneath; the Starter licence is free, forever — you pay only your Azure
- Scales to zero; a flow moving four files a day costs what four files cost
- Config changes go live on save — no build, no MSI, no host restart
- AI Accelerator drafts pipeline components, custom functions and maps for your team to review
- MCP Server — Claude, Copilot, VS Code or any MCP client builds the whole integration on iQBus — ports, pipelines, components, maps, promoted properties — under three access levels you set per environment (Grow and Enterprise)
- The only one of the five whose AI runs entirely inside your own tenant — prompts, drafts and agent actions never leave your Azure subscription
Wrong choice when
- Your problem is connecting fifty SaaS apps — Boomi and MuleSoft have far bigger catalogues
- You have a few dozen simple flows — Logic Apps alone is cheaper
- You depend on ordered delivery or convoy-style correlation today — neither is available yet
- You are not on Azure, or standardised on another cloud
- You need an on-premises runtime — we are Azure only
Meters: cores of the infrastructure it runs on — the same meter as BizTalk, at a fraction of BizTalk’s per-core list price, with no SQL Server licence underneath and no per-message, per-integration or per-partner fees — plus the Azure it consumes in your own subscription. Grow and Enterprise are priced by core. Entry: $0 licence on Starter; Microsoft bills the Azure, estimated at about $73/month.
Azure Logic Apps
Best for simple flows and Azure-native greenfield
Microsoft’s designated successor path for BizTalk, and for a large number of estates the right answer. It is also the option most often misjudged, because “Logic Apps” is two different products: Consumption is multitenant and billed per action executed, with no virtual-network isolation at all since the Integration Service Environment was retired in August 2024. Standard is single-tenant, billed as a hosting plan, and supports private endpoints, VNet integration and built-in connectors that run in-process. Most BizTalk-shaped estates that succeed here are on Standard.
Strengths
- First-party and native — no third-party licence anywhere in the stack
- Genuinely cheapest for a few dozen straightforward flows
- Composes with Service Bus, API Management, Event Grid and Functions
- Standard supports hybrid deployment on Arc-enabled Kubernetes
- Fast-moving roadmap — Build 2026 added a scale-to-zero Automation SKU and a C# SDK
Wrong choice when
- EDI is central — trading partners still need a separate Integration Account resource
- You need pub/sub filters or ordered delivery — both come from Service Bus, not Logic Apps
- You want tracking out of the box — that is Application Insights plus Log Analytics
- You need network isolation on Consumption — it has none
Meters: actions executed (Consumption) or a hosting plan by tier plus an Azure Storage account for stateful run history (Standard).
Boomi
Best for SaaS-heavy estates
A long-established iPaaS with a very large connector catalogue and a genuinely fast low-code build experience. If your integration problem is “connect fifty SaaS applications”, Boomi gets you there quickly and the catalogue does real work. Runtime placement is flexible — Boomi-hosted clouds or your own Atoms, including on-premises. Boomi now sells two different meters: its annual editions price connections, and a self-service Pay-As-You-Go plan prices messages instead.
Strengths
- Very large connector catalogue across applications and technologies
- Fast to build in; low-code experience is a real productivity advantage
- Self-hosted runtimes — Atoms, Molecules, Private Runtime Cloud
- Observability included via OpenTelemetry, no separate licence
- Trading partner support covers X12, EDIFACT, HL7 and more
Wrong choice when
- You have a long tail of low-volume endpoints on an edition — every deployed connection consumes a licence
- You move high document volumes on Pay-As-You-Go — every document in or out is billed
- You need content-based subscription filters — not documented; filtering happens in-process
- You need durable mid-execution resume on integration processes — not documented
- You need edition pricing to plan against — editions are quote-only
Meters: on annual editions, connection licences — counted per unique connection component deployed per runtime and priced by connector class (Small Business, Standard, Enterprise, Trading Partner) — with Flow launches priced additionally. On Pay-As-You-Go, the Boomi Message: $99/month plus $0.05 per document sent or received, with unlimited connections.
MuleSoft Anypoint Platform
Best for large multi-team API programmes
The heavyweight, with a matching methodology and price point. API-led architecture done properly, with API management, governance and a design catalogue in one platform. For a large organisation standardising integration across many teams — particularly a Salesforce-centric one — what comes with it is a genuine asset rather than overhead.
Strengths
- API management, governance and design catalogue in one platform
- Strong alignment if the business is already Salesforce-centric
- Flexible deployment — CloudHub, your own cloud, or on-premises
- Mature private networking via CloudHub 2.0 private spaces
- An integration methodology, not just a runtime
- One credit pool now spans API, AI-agent, application and document workloads
Wrong choice when
- Your estate is file-and-EDI-shaped rather than API-shaped
- You need ordered delivery and content-based routing on one destination — they are mutually exclusive
- You need to model cost before signing — per-credit rates are not published
- You need long-lived process state — no durable workflow engine is documented, and Object Store v2 data expires 30 days after creation unless it is read again
Meters: Mule Credits — a shared unit of consumption, with a separate credit rate for each usage type — sold in five use-case packages starting at $2,000/month, billed annually. Credits are pre-purchased, pre-committed (a $50K annual minimum), or bought as a custom unlimited contract.
BizTalk Server
The incumbent, with a date on it
A platform with an end-of-support date belongs on this list for one reason: doing nothing is always an option, and it deserves to be priced honestly rather than dismissed. Twenty-year-old orchestrations still run, the capabilities are complete and coherent in one product, and your team knows it.
Strengths
- EDI, pub/sub, pipelines, tracking and adapters in one coherent product
- It works, and your team already knows it
- Mainstream support to April 11, 2028; extended support to April 2030
- Cheaper this month than most alternatives if you fit inside Standard edition
Wrong choice when
- You are planning past 2028 — 2020 is the last and final version, and Microsoft expects to stop selling it on March 31, 2027
- You are on BizTalk Server 2016 — its extended support ends January 11, 2027
- You rely on BAM, the ESB Toolkit or the HL7 accelerator — Microsoft says they will not be serviced under its planned paid bridge from 2028 to 2030
- You want a small production footprint — four-core licensing floor, plus SQL Server
- Your dependency floors have expired — several Windows and SQL Server dates have already landed
- Your team is shrinking — the real deadline is when nobody can safely change an orchestration
Meters: cores, with a four-core minimum, plus SQL Server licensed separately under the same floor.
The cheapest way to test any of this is to stop reading comparisons. The iQBus Starter licence is free, forever, and it is the same runtime as every other tier. It installs from Azure Marketplace into your own subscription, so the running cost — Azure, billed by Microsoft, estimated at about $73 a month — is a number you check on your own bill rather than take from a table written by one of the five vendors in it. If you would rather start from your estate than from the product, talk to one of our integration architects first.
02 / What it costs
The meter, not the rate
Only two of these five publish rates you can fully look up: Azure and iQBus. MuleSoft now publishes a starting point — packages from $2,000 a month — but not its per-credit rates. Boomi publishes its Pay-As-You-Go plan but not its editions. Microsoft has never published a BizTalk price list. So the question that actually predicts your bill is not what it costs today — it is what the meter does as the estate grows.
Picture your estate in three years. You have added a hundred small interfaces — the nightly export to a logistics partner, the weekly feed to a broker, the thing a department asked for and still needs. Each moves a handful of files a day. Now ask what each meter does with that.
Twenty years of integration work does not produce twenty large interfaces. It produces a long tail. That shape is the single most important input into which of these platforms suits you, and it is the one most evaluations never measure.
They change which platform is cheapest for you
03 / What you assemble
Eight capabilities, and who makes you buy them separately
BizTalk’s genuine achievement — easy to miss until you leave — is that EDI, durable orchestration, publish-subscribe with filters, ordered delivery and tracking all lived in one product, under one licence, in one console.
Every platform here can do most of those things. None of the alternatives does all of them in one product — and that includes ours: iQBus has EDI, filtered subscriptions and tracking in the runtime, but not ordered delivery or convoy-style correlation yet, and the table says so. That is the trade you are actually making, and it is invisible in a feature checklist, because a checklist answers “can it?” and the question that matters is “what else do I have to buy, run and monitor to get it?”
| Platform | EDI / trading partners | Durable orchestration | Pub/sub content filters | Ordered delivery |
|---|---|---|---|---|
| BizTalk Server | In the product | In the product | In the product — subscription filters | In the product — ordered delivery ports |
| MuleSoft | Anypoint Partner Manager — a separate entitlement, plus per-standard connector entitlements for AS2, X12, EDIFACT | No durable workflow engine documented. Batch jobs resume after a crash; longer-lived state uses Object Store v2, where data expires 30 days after creation unless it is read again (rolling TTL) | Anypoint MQ add-on — routing rules on exchange bindings, one property per rule | Anypoint MQ FIFO queues |
| Boomi | Trading Partner components — their own connection-licence class, and editions are quote-only | Flow has durable states and Wait steps. For Integration processes, durable mid-execution resume is not documented | Event Streams add-on, licensed by annual message volume. Content-based subscription filters are not documented — filtering is done in-process | Event Streams Exclusive or Failover subscriptions with transacted acknowledgement |
| Azure Logic Apps | Needs an Integration Account resource for partners, agreements and certificates — in Consumption and Standard. Standard only relaxes it for schemas and maps | Stateful workflows, state in a required Azure Storage account. Max run 90 days. Stateless workflows default to 5 minutes | Not a Logic Apps feature — Azure Service Bus topic subscription rules (SQL, correlation, boolean filters). Needs Standard or Premium tier | Not a Logic Apps feature — Service Bus message sessions. Basic tier does not support them |
| iQBus ours | In the runtime — EDI and HL7 in use today | Failed runs are held as Suspended in Tracking and resumed in one click. Convoy-style correlation is not available yet | In the runtime — send-port subscriptions on message type and promoted values | Not available yet |
| Platform | Network isolation | On-premises runtime | Connector catalogue | Observability |
|---|---|---|---|---|
| BizTalk Server | It is your network | That is where it runs | Adapters, incl. paid third-party ones | BAM and HAT, in the product |
| MuleSoft | CloudHub 2.0 Private Spaces — VPN, Transit Gateway, outbound PrivateLink | Yes — standalone runtime, Runtime Fabric, or Private Cloud Edition | Large. Premium connectors are licensed separately, per environment | Anypoint Monitoring, included but tier-gated — alerts, custom dashboards and telemetry export are not in the entry tier. Traces are Beta |
| Boomi | Private Runtime Cloud; Dedicated and Managed Cloud Services are separately contracted | Yes — Atoms, Molecules, Private Runtime Cloud | Large. Tiered by licence class: Small Business, Standard, Enterprise, Trading Partner | Runtime Observability via OpenTelemetry, included. Boomi’s own docs say it is not intended for critical business transaction tracing |
| Azure Logic Apps | Standard only — VNet integration and private endpoints. Consumption has none: the Integration Service Environment was retired in August 2024 | Standard only, via the hybrid deployment model on Arc-enabled Kubernetes — which also needs a SQL database and an SMB file share, and is region-limited | Large managed catalogue; Standard adds in-process built-in connectors. Enterprise connectors — SAP, IBM MQ, IBM 3270 — cost extra | Run history native. Enhanced telemetry needs Application Insights; log queries need Log Analytics. B2B transaction tracking in Standard needs a Premium integration account and an Azure Data Explorer cluster, and is preview, X12 and AS2 only |
| iQBus ours | Runs in your own Azure subscription with Entra ID. Supports SOC 2 and HIPAA | No — Azure only | Smaller than Boomi’s or MuleSoft’s — API, Service Bus, SFTP, SQL, MQ Series, SAP, Salesforce and more. Our adapter library grows every week | Built in: a flow tracking dashboard, search by tracking ID, date and message type, one-click resume, email alerts |
Both tables scroll sideways on a narrow screen. Competitor cells are from each vendor’s own current documentation and pricing pages, re-checked on 28 October 2026, and say “not documented” rather than “not supported” where the docs are silent — those are different claims. Vendor documentation changes; verify anything decisive before you sign. Our own column is our own documentation, and you should treat it with exactly the same suspicion.
A ninth, new this quarter: where the AI runs, and what an agent may do
Every platform on this page now ships some form of AI. The questions that matter are the same two a security team asks about anything else: where does it run, and what can it touch. Two different things hide under the word “MCP” here. Exposing your deployed integrations as tools an agent can call is one capability. Letting an outside agent operate the platform — design and build the integration — is another.
| Platform | Built-in AI | Where that AI runs | MCP | What an outside agent can do |
|---|---|---|---|---|
| BizTalk Server | None | — | None | Nothing |
| MuleSoft | Agentforce and Einstein features across Anypoint | Salesforce’s platform, not your tenant | GA since July 2025: Mule apps and APIs exposed as MCP servers through the MCP Connector; Flex Gateway applies policies to MCP endpoints | Call your published APIs and integrations as tools. Building integrations with AI happens in Salesforce-hosted tooling |
| Boomi | Boomi AI agents and Agentstudio | The Boomi platform, not your tenant | APIs exposed as hosted MCP servers in API Control Plane; an MCP Server tech preview in the Boomi runtime turns deployed processes into tools | Call deployed processes and APIs as tools. Building with AI (Boomi GPT, Agentstudio) runs on Boomi’s platform |
| Azure Logic Apps | Copilot in the designer; agent-loop workflows (Standard, and Consumption in preview) | Microsoft’s service. For agent loops Microsoft’s own docs say the model “can originate from any region, so data residency for a specific region isn’t guaranteed” | Logic Apps Standard can act as a remote MCP server, exposing connector actions as agent tools (preview) | Call workflows and connectors as tools. The designer Copilot drafts workflows inside Microsoft’s service |
| iQBus ours | AI Accelerator — drafts components, functions and maps | Inside your own Azure subscription, with the rest of iQBus | Built-in MCP Server, Grow and Enterprise; sign-in through Entra ID with OAuth 2.1 | Build the whole integration — ports, pipelines, components, maps, promoted properties — and monitor it, under three access levels per environment: Off, Structure (never reads message content) or Full access. Credentials stay with people; every action is written to iQBus Auditing |
Competitor cells from each vendor’s own MCP and AI documentation, checked on 29 October 2026 — Boomi’s MCP overview and Agentstudio pages, MuleSoft’s MCP announcement, and Microsoft’s Logic Apps agent-workflow docs. “Not your tenant” means the vendor runs the AI on its own platform; it does not say anything about how that vendor protects your data there. Our own cells describe our own product, and deserve the same suspicion.
Three details that decide real evaluations
On MuleSoft, ordered delivery and content-based routing are mutually exclusive
Anypoint MQ’s documentation states that FIFO exchanges do not support routing rules, and that only standard queues bind to standard exchanges while only FIFO queues bind to FIFO exchanges. So on a single destination you can have guaranteed ordering or content-based subscription filtering — not both. If your BizTalk estate uses ordered delivery on a filtered subscription, that pattern does not port directly, and it is not the kind of thing a feature checklist surfaces.
Logic Apps Standard did not remove the Integration Account
A widespread assumption is that Logic Apps Standard made B2B native. It made schemas and maps native — you upload those to the logic app resource. Trading partners, agreements and certificates still live in an Integration Account, a separate billed resource with Free, Basic, Standard and Premium tiers. If EDI is your estate, that resource and its tier limits belong in your cost model from day one.
Nobody replaces BAM and HAT with one thing
BizTalk’s tracking was ordinary but it was there. On Logic Apps you get run history natively, then add Application Insights for telemetry, Log Analytics for queries, and — for B2B transaction tracking in Standard — a Premium integration account plus an Azure Data Explorer cluster, currently in preview and limited to X12 and AS2. On MuleSoft, alerts and custom dashboards sit above the entry monitoring tier. On Boomi, observability is included and their docs caution it is not intended for critical business transaction tracing. Whichever you choose, budget for assembling observability rather than inheriting it.
A feature checklist asks “can it?”. The question that decides the project is “what else do I have to buy, run and monitor to get it?”
Why this section exists instead of a matrix of ticks
04 / Choosing
Match the platform to the shape of the estate
| If your estate is… | Look first at | Because |
|---|---|---|
| A few dozen simple flows, no orchestration state, no EDI | Azure Logic Apps alone | Cheapest credible answer. You do not need an ESB and should not buy one. |
| Wide and file/EDI-shaped — many partners, many low-volume feeds, X12 or EDIFACT | iQBus, or Logic Apps Standard with a B2B resource | Breadth-tolerant metering matters here, and EDI capability should be your first filter rather than your last. |
| Fifty-plus SaaS applications, API-centric, little or no EDI | Boomi or MuleSoft | The connector catalogue and the low-code build experience are the actual value, and they are strong. |
| Large, multi-team, API-led with governance and an API programme | MuleSoft Anypoint | You are buying API management and a methodology, not just a runtime. |
| Salesforce-centric across the business | MuleSoft Anypoint | Same vendor, aligned roadmap, and the commercial conversation is one you are already having. |
| Built on strict ordered delivery or convoys | Logic Apps with Service Bus sessions, or MuleSoft FIFO queues | Both document ordering today. iQBus does not have it yet, so do not pick us for this workload until it does. |
| Regulated with on-premises processing requirements | Boomi or MuleSoft self-hosted runtimes, or staying put | Both support running the runtime in your own environment. Constrain the shortlist on this before anything else. |
| AI-first — you want the assistant your teams already run to build and watch integrations, without prompts or messages leaving your tenant | iQBus | The MCP Server lets Claude, Copilot or any MCP client build the integration end to end, and the AI stays inside your subscription. Elsewhere, MCP exposes what you have already built as tools, and the building AI runs on the vendor’s platform. |
| BizTalk today, and you have not started | An inventory, before any vendor call | Nothing on this page can be chosen sensibly until you know how many artifacts you have and which ones still carry traffic. |
That last row is the one we would push hardest, and it sells nothing. Most estates we assess are running artifacts nobody has touched in years. Until you know which those are, every quote you receive is priced against an estate larger than the one you actually need — and on connection-licensed and consumption-metered platforms, that difference is money every month for the life of the contract.
If you want the category-level version of this decision — including the destinations that are not on this page, such as rehosting to another cloud — we have written that up separately.
We will tell you when the answer is not us. Cerebrum City is an Atlanta-based Microsoft Solutions Partner for Cloud & AI Platforms, Microsoft V-TSP recognized for BizTalk Server, and has run enterprise integration in production since 2007. Our assessment produces an artifact inventory, a target-state map and a wave plan — and it names the platform that fits, including when that platform is one of the other four.
Call (678) 203-0800.
Frequently asked questions
What are the main integration platforms for Azure estates in 2026?
The five most commonly evaluated are MuleSoft Anypoint Platform, Boomi, Azure Logic Apps, BizTalk Server as the incumbent, and iQBus. They differ less in what they can do — all of them can receive, transform and route a message — than in what they bill you for: consumption credits, connection licences or messages, executed actions, or cores.
How is MuleSoft priced?
MuleSoft now prices on Mule Credits, a shared unit of consumption across its capabilities, with a separate credit rate for each usage type that falls as usage rises. Credits come in five use-case packages — Govern APIs and AI, Manage Agents, Connect Apps, Process Documents and Access Everything — starting at $2,000 a month billed annually. You can pre-purchase credits, pre-commit to an annual baseline with a $50,000 minimum, or negotiate an unlimited contract. Per-credit rates are not published.
How does Boomi count connections for licensing?
Boomi licenses connections per unique connection component deployed per runtime, identified by component ID rather than by endpoint. Reusing one connection component across many processes consumes a single licence, while two identical connections with different component IDs consume two. Licences fall into classes — Small Business, Standard, Enterprise and Trading Partner — and some connectors, including the AS2 Shared Server and Web Services Server, do not consume a licence at all. Boomi’s Pay-As-You-Go plan works differently: $99 a month plus $0.05 per Boomi Message, meaning each document sent or received, with unlimited connections.
What is the difference between Logic Apps Consumption and Standard?
Consumption is multitenant and billed per action executed, with one workflow per resource and limited virtual-network support. Standard is single-tenant and billed as a hosting plan by tier, supports many stateful and stateless workflows in one resource, offers full virtual-network integration with private endpoints and a dedicated static outbound IP, and runs built-in connectors in-process with the workflow for higher throughput. Most BizTalk-shaped estates that succeed on Logic Apps are on Standard.
Is Azure Logic Apps enough to replace BizTalk?
For estates that are mostly straightforward flows, often yes, and it will be cheaper than any licensed ESB. The gaps are the BizTalk capabilities that were never workflows: publish-subscribe with subscription filters, convoys, ordered delivery, pipeline disassemble-and-validate stages, and trading-partner agreement management. Those are assembled from Azure primitives rather than ported, and B2B/EDI capability is an additional resource you add rather than part of the base runtime.
Does Azure Logic Apps Standard still need an Integration Account for EDI?
Yes, for trading partners, agreements and certificates — in both Consumption and Standard. What Logic Apps Standard changed is that schemas and maps can be uploaded directly to the logic app resource and used across its workflows, along with built-in AS2, X12, EDIFACT and RosettaNet operations. The Integration Account itself remains a separate billed resource with Free, Basic, Standard and Premium tiers, so if EDI is central to your estate it belongs in the cost model from the start.
Which integration platforms include EDI without a separate purchase?
Of the five compared here, BizTalk Server and iQBus include it in the product. MuleSoft requires an Anypoint Partner Manager entitlement plus per-standard connector entitlements for AS2, X12 and EDIFACT. Boomi’s trading partners are their own connection-licence class with quote-only editions. Azure Logic Apps requires an Integration Account resource. Every platform can do EDI; the difference is whether it arrives as part of the platform or as another thing to license, deploy and monitor.
What did BizTalk have in one product that alternatives make you assemble?
EDI and trading-partner management, durable orchestration, publish-subscribe with content-based filters, ordered delivery, and tracking. On Azure Logic Apps, for instance, content filtering and ordered delivery come from Azure Service Bus topic subscription rules and message sessions rather than from Logic Apps itself, durable state requires an Azure Storage account, and observability beyond run history requires Application Insights and Log Analytics. The capability exists on every platform; what differs is how many separately licensed and separately monitored pieces it takes.
Why does the pricing model matter more than the price?
Because mature integration estates grow in breadth rather than volume. Twenty years of work produces a long tail of low-volume interfaces, and the meters treat that tail very differently: per-core models absorb it at near-zero marginal cost, while connection-licensed models charge for each addition regardless of how little it carries, and credit-based consumption models charge at rates you only learn from a quote. The rate tells you this month’s bill; the meter tells you what the estate costs in three years.
What should I do before contacting any integration vendor?
Count two things: how many distinct endpoints you actually have, and how many of them moved a message in the last ninety days. The second number is almost always much smaller. Decommissioning dead interfaces before you buy is the cheapest cost optimisation available on any connection-licensed or consumption-metered platform, and no vendor will suggest it to you because it reduces the size of the deal.
Which integration platform lets my own AI agent build integrations?
iQBus, through its built-in MCP Server (Grow and Enterprise plans). Any MCP client — Claude, Microsoft Copilot, an agent in VS Code or one you build — can create a complete integration on iQBus: ports, pipelines, pipeline components, maps and promoted properties. Three access levels, set per environment, decide what the agent sees; credentials are always added by a person and nothing runs until your team reviews it. MuleSoft, Boomi and Azure Logic Apps also support MCP, but there it exposes your already-built APIs and processes as tools for agents to call, and their AI assistants run on the vendor’s platform rather than in your tenant.
Which platform does Cerebrum City recommend?
It depends on the shape of the estate, and we publish the cases where the answer is not our product. A few dozen simple flows should use Azure Logic Apps alone. Fifty-plus SaaS applications with little EDI are better served by Boomi or MuleSoft’s connector catalogues. Large multi-team API programmes suit MuleSoft. iQBus is built for wide, file-and-EDI-shaped estates that are BizTalk-shaped today, where concept-level parity means existing team knowledge transfers rather than being written off.
Jorge Pastorini · Cerebrum City
Cerebrum City is a Microsoft V‑TSP–recognized BizTalk specialist in Atlanta, Georgia, with two decades running BizTalk Server in enterprise production for clients including Humana, Deloitte, JetBlue, and U‑Haul.
Want this mapped against your BizTalk estate?
We inventory your ports, orchestrations, maps, and adapters, flag the interfaces most likely to break, and hand back a staged Azure roadmap. No obligation.
