First-generation hubs
On-premises servers brought structure to enterprise messaging.
The Azure-native enterprise service bus: the integration platform you trust, reimagined for the cloud and accelerated by AI.

Trusted by enterprise integration teams
Routing, transformation and message flow, native to your Azure tenant and governed by the controls you already run.
Azure-native runtime
iQBus runs in your own Azure tenant, on Microsoft Entra ID and Azure Service Bus, from day one. Nothing new to stand up, staff or pay for separately.
If your team knows BizTalk, it already knows iQBus: ports, pipelines, maps and subscriptions work the way they expect.
Explore the platformZero-deploy changes
Adjust routing, mapping and validation through configuration, not code. Changes go live in real time: no builds, no restarts, no deployment windows.
See how configuration worksEnd-to-end visibility
Built-in tracking follows each message through every port and pipeline. A failed run is suspended, not lost: fix the cause and resume it with one click. Audit-ready telemetry is part of the runtime.
Explore trackingAdapters
Receive and send through the adapters enterprise estates depend on, with EDI and HL7 handled in the pipeline. When an engagement needs a transport that is not in the box, our team builds it.
See all integrationsSkills you can hire
BizTalk expertise is retiring. iQBus runs on the Azure and .NET skills your team already has, and the market can supply.
Read the documentationFrom on-premises hubs to cloud-native runtimes, iQBus is the natural next step: purpose-built for Azure and accelerated by AI.
On-premises servers brought structure to enterprise messaging.
iPaaS extended integration into the cloud, but governance and depth often lagged.
An Azure-native runtime, enterprise-grade governance and a built-in AI Accelerator.
Cerebrum City moved Novelty, Inc.'s retail-partner EDI off end-of-life BizTalk Server to iQBus on Azure, carrying 50–70% of the existing artifacts forward with no downtime at cutover.
iQBus has been a real asset to the business. Its intuitive interface allowed us to implement EDI effortlessly, and the built-in transaction tracking gives us the visibility to manage operations with confidence.
Retail-partner EDI
BizTalk Server → iQBus on Azure
BizTalk Server 2020 is the final release. Mainstream support ends April 11, 2028, and paid extended support runs until April 9, 2030. The three realistic paths differ sharply on what a board weighs: migration, transaction visibility, governance, disaster recovery and future support.
Extend the investment · end of life 2030
Protect the BizTalk investment through the Microsoft support deadline.
Microsoft’s cloud path
Rewrite onto Azure-native services, with composition split across two of them.
Carry your BizTalk work forward
Bring your BizTalk maps and flows onto an Azure-native runtime.
| Decision factor | Stay on BizTalk | Logic Apps + Functions | iQBus |
|---|---|---|---|
| Migration | Not required | Full rebuild required | 50–70% carried forward |
| Transaction visibility | Custom BAM build | Fragmented · custom build | Built in, end to end |
| Governance & audit | Partial compliance | Custom build required | Built-in controls |
| Disaster recovery | Complex to configure | Custom configuration | Streamlined, built in |
| Future support | Mainstream ends Apr 2028, extended Apr 2030 | Indefinite | Indefinite |
Comparison reflects generally available capabilities at the time of publication. Microsoft, BizTalk Server, Azure Logic Apps and Azure Functions are trademarks of Microsoft Corporation.
iQBus is built by Cerebrum City, a Microsoft Solutions Partner. Install it from Azure Marketplace into your own subscription and govern it with the identity, keys and networking you already run.
Tell the AI Accelerator what the integration needs. It drafts the pipeline components, custom functions and maps; your team reviews the draft and puts it to work.
Try a prompt
Every result is a first draft for your engineers to review before it runs.
Explore the AI Acceleratorpublic sealed class Hl7LabOrderSplitter : PipelineComponentBase<Hl7Config>{ public override string Name => "fnHl7LabOrderSplitter"; // Disassemble the HL7 batch, then split per order protected override async Task<PipelineComponentOutput> ExecuteAsync( PipelineComponentInput input, Hl7Config config, CancellationToken ct) { var json = Hl7.Disassemble(input.Body, config.CanonicalSchema); var orders = json.SelectTokens("$.orders[*]"); return PipelineComponentOutput.Split(orders); }}
public sealed class EdiDebatcher : PipelineComponentBase<EdiConfig>{ public override string Name => "fnEdiDebatcher"; // Decode, debatch the interchange, disassemble by EDI type protected override async Task<PipelineComponentOutput> ExecuteAsync( PipelineComponentInput input, EdiConfig config, CancellationToken ct) { var raw = Convert.FromBase64String(input.AsString()); var interchange = Edi.Debatch(raw); var messages = interchange.Select(tx => Edi.Disassemble(tx, tx.DetectType())); return PipelineComponentOutput.Many(messages); }}
public sealed class BankWireGate : PipelineComponentBase<WireConfig>{ public override string Name => "fnBankWireGate"; // Decrypt with the key parameter, validate, forward or throw protected override async Task<PipelineComponentOutput> ExecuteAsync( PipelineComponentInput input, WireConfig config, CancellationToken ct) { var wire = Crypto.Decrypt(input.Body, config.DecryptionKey); if (!Wire.IsValid(wire, out var error)) throw new PipelineException(error); return PipelineComponentOutput.Single(wire); }}
iQBus comes from the integration architects and engineers behind some of the largest BizTalk deployments in the world. When Microsoft signaled the end of BizTalk Server's evolution, we built its Azure-native successor. Today iQBus is published on Azure Marketplace and trusted across healthcare, financial services, logistics and the public sector.
About usBook a 30-minute discovery session. We'll look at your landscape and send a tailored roadmap within a week.