Two decades of enterprise integration, distilled into straight answers: who we are, how we work, what it costs, and how your data is protected. Looking for BizTalk lifecycle dates or EDI migration mechanics? Those live on their own pages, linked below.
Cerebrum City is a US systems-integration company founded in Atlanta in 2007. We are a Microsoft Solutions Partner for Cloud & AI Platforms, and our team holds Microsoft’s V-TSP recognition for BizTalk Server after two decades running the platform in enterprise production. We deliver system integration, EDI, HL7/FHIR and BizTalk-to-Azure migration, and we build iQBus, an Azure-native enterprise service bus.
Cerebrum City is a US systems-integration company founded in Atlanta in 2007. We are a Microsoft Solutions Partner for Cloud & AI Platforms, and our team holds Microsoft's V-TSP recognition for BizTalk Server after two decades running the platform in enterprise production.
We deliver system integration, EDI, HL7/FHIR and BizTalk-to-Azure migration, and we build iQBus, an Azure-native enterprise service bus.
Two decades of advanced custom software and cloud delivery for mid-market and enterprise clients. The distinction that matters in this niche: we did not read about BizTalk Server; we architected, ran and upgraded it in production for twenty years, which is why Microsoft extended V-TSP recognition to our team for the platform.
That means we build your migration plan already knowing which orchestrations will fight us, rather than working it out from a feature matrix.
V-TSP, Virtual Technology Solutions Professional, is a designation Microsoft extends to a small number of outside specialists it will route customers to on a specific product. Ours is for BizTalk Server.
Practically, it means Microsoft treated our team as a reference point on the platform rather than as one more partner in a directory. It is separate from, and additional to, our Solutions Partner designation for Cloud & AI Platforms.
Our head office is at 730 Peachtree Street NE, Atlanta, GA 30308. The work itself is delivered remotely.
We work with enterprises across the United States and internationally, and we adapt our working hours to your time zone.
Enterprise integration, end to end, from architecture through managed run:
Five sectors, all chosen because integration is load-bearing rather than convenient:
Yes, and we assume it. Our deepest expertise is Azure, but almost no enterprise estate is single-cloud; we routinely engineer integrations spanning Azure, AWS and on-premise systems, connected through a message broker rather than point-to-point.
Hybrid is the steady state for most of our clients, not a transitional phase, and we design for it accordingly.
Yes, inherited platforms are a large share of our work. The first step is an architecture review: what is actually deployed, what is documented, what is undocumented but load-bearing, and where the operational risk sits.
You get a written map of your own estate out of that, which is useful whether or not we go further together.
Call (678) 203-0800 or use the contact form. From there the path is short:
You can stop after the assessment and keep the findings.
Case by case. Every integration estate is different enough that a published rate card would mislead more than it helps, so we price each engagement on what it actually involves and walk you through the numbers after the architecture assessment.
That assessment comes first and is complimentary for qualified enterprise engagements, so you reach a real number before you have spent anything.
Yes. The architecture assessment is free, and there is no catch and no obligation.
You keep everything it produces: the findings, the risk list and the recommended sequence. No commitment to proceed, no licence to buy, and no invoice for the assessment itself.
The architect on your discovery call stays on your engagement. Team composition, named roles and working hours are set out in the engagement schedule before you sign anything.
Every engagement is built to defence-in-depth principles, and the integration layer is treated as production infrastructure rather than plumbing:
Yes. We have run protected health information through production interfaces across payer, provider, HIE and pharmacy systems, and we execute Business Associate Agreements as a matter of course before any PHI is in scope.
Where we build to a compliance regime, we build to your certification scope: your auditors assess the resulting system, and we produce the evidence they ask for.
You do. Bespoke integrations, maps, schemas, pipelines and documentation built for your engagement are your deliverables, handed over in your own repository and your own Azure tenant.
The one line to draw: our pre-existing platform components and the iQBus product remain ours and are licensed to you. That boundary is written into the engagement terms, not left to be discovered later.
Yes, and most clients take it. An integration estate is not a project that ends: trading partners change formats, clinical systems get upgraded, and volumes grow. Managed run covers monitoring, incident response, partner and interface onboarding, and continuous improvement.
Response commitments and coverage hours are agreed in the service schedule and sized to your availability requirement rather than sold as fixed tiers.
Yes. Supporting and extending BizTalk in production is what we did for twenty years, and we still do it, including on versions past their support date, where the risk profile is exactly what you would expect and worth being explicit about.
Keeping BizTalk running well and planning your eventual exit are not in conflict. We will do the first without pushing you into the second before you are ready.
Managed-run clients get monitored interfaces with alerting on message failure, latency and queue depth, and an on-call escalation path agreed in the service schedule. It reaches an engineer who knows your estate, not a first-line queue reading a script.
Every incident closes with a written root cause and the change that prevents a repeat.
iQBus is our Azure-native enterprise service bus, built and sold by Cerebrum City, with its own site, documentation and pricing at iqbus.io.
No. The services and the product are separate purchases, and your architecture assessment decides which one your estate calls for: some engagements are best served by iQBus, others by native Azure services alone. We make that call on the merits of your environment and tell you which way we think it goes.
Two answers, depending on whether you mean the product or the services.
iQBus runs on Azure only. There is no on-premise edition and no AWS edition. It is built on Azure services by design, not ported onto them.
Our services are not Azure-only. Azure is where we are deepest and where most of our clients are heading, but we are integration engineers before we are Azure specialists: we build on native Azure services, on integration platforms already in your estate, and against systems running on AWS or in your own data centre. The destination should follow your estate and your team's skills, not our preference.
If you don't see your question above, you're probably asking something specific to your environment. That's exactly the conversation we're best at: no sales script, no commitment.
From integration pioneers to cloud-native experts — start with a courtesy assessment and we’ll map the fastest path to a modern architecture.
