BMC Remedy Integration

Vendor Due Diligence

ZigiOps · Exalate · Unito · BMC Helix iPaaS

Zachary Fouts · 2026-04-22

Note: This deck accompanies the written due-diligence document (BMC_INTEGRATION_V2.md). Audience is technical decision-makers and procurement reviewers. The goal is to document that we genuinely evaluated the alternatives before recommending BMC Helix iPaaS — not to pitch.

The Question

> “Which platform should we use to build bi-directional integrations with BMC Remedy?”

We evaluated four options.

One of them is already our leading candidate.

Three of them deserve a look anyway.

Note: The value of the exercise is not the final pick — we already know where we are leaning. The value is being able to answer, under audit, “did you actually evaluate the alternatives?” with receipts.

TL;DR

  • Only ZigiOps and BMC Helix iPaaS ship a real, productized BMC Remedy connector.
  • Exalate and Unito do not. They are evaluated and excluded on native-connector grounds.
  • BMC Helix iPaaS (Jitterbit) is the recommended baseline — first-party, roadmap-aligned, full iPaaS.
  • ZigiOps is the qualified alternative — cheaper, narrower, on-prem-capable, faster time-to-value.
  • The recommendation is defensible and we name BMC iPaaS’s real drawbacks honestly.

Note: The headline finding — that two of three third-party vendors do not actually support BMC Remedy — is the single most important output of this diligence. It sharpens the recommendation from “BMC iPaaS is better” to “only one third-party option even qualifies for the shortlist.”

Verdict Matrix

ZigiOpsExalateUnitoBMC iPaaS
Native Remedy connector
BMC partner statusListedNoneNoneOEM
On-prem optionPartial
Pricing transparencyQuotePublicPublicQuote
Shortlist statusQualifiedRejectedRejectedBaseline

How We Verified

[VERIFIED] — confirmed against first-party vendor page, docs, or marketplace listing.

[VENDOR CLAIM] — stated in marketing; not independently corroborated.

[BIASED SOURCE] — sourced from a competitor’s comparison page. Corroborative only.

[UNVERIFIED] — could not confirm from any reliable public source. Flagged, not asserted.

Primary verification: 2026-04-22.

Note: Every factual claim in the written doc carries one of these four tags. A diligence document that claims to have verified everything is not credible. Marking our uncertainty is the rigor.

The Two Product Categories

Point-to-point sync tools — ZigiOps, Exalate, Unito

  • Keep records aligned across two systems
  • Bi-directional field mapping, conflict resolution, loop prevention

Integration Platform as a Service (iPaaS) — BMC Helix iPaaS

  • Everything above, plus ETL, API management, event orchestration
  • Full enterprise reach (ERP, HR, CRM, databases)

Different categories. Different price points. Different decisions.

ZigiOps — The Qualified Alternative

Company: ZigiWave · Sofia, Bulgaria · founded 2020 · ~30 engineers · ISO 27001 certified

BMC partner status: Listed in BMC partner locator; no Technology Alliance tier confirmed

Deployment: On-prem (Windows/Linux), SaaS (AWS), or customer-managed cloud

Architecture: Agentless, stateless, zero-data-retention for payloads

Note: ZigiOps is genuinely the only third-party vendor of the three that ships a productized BMC Remedy connector. This is confirmed by their own docs, the OpenText ITOM Marketplace listing for “ZigiOps for BMC Remedy” at the SUPPORTED tier, and the Atlassian Marketplace listing for bi-directional BMC Remedy integration for Jira.

ZigiOps — BMC Connector Coverage

Supported objects:

  • Incident [VERIFIED]
  • Change Request [VERIFIED]
  • Task, Work Order [VERIFIED / VENDOR CLAIM]
  • Problem [VENDOR CLAIM]
  • CMDB / BMC Atrium CI sync [VERIFIED]
  • Events/Alerts [VERIFIED]
  • Custom forms via schema discovery [VENDOR CLAIM]

Attachments, work notes, comments: bi-directional [VERIFIED]

Version matrix for Remedy/Helix: not publicly published [UNVERIFIED]

ZigiOps — Pros

  • Genuinely no-code for standard ITSM-to-ITSM patterns
  • On-prem install keeps data in customer perimeter — material for regulated industries
  • Flat per-pair pricing, unlimited data volume within a pair
  • Implementation bundled — no separate PS engagement
  • Deep monitoring/AIOps connector coverage (Datadog, Dynatrace, Splunk, OpsBridge…)
  • Short time-to-first-sync for standard patterns

ZigiOps — Cons

  • Opaque Remedy/Helix version support matrix — must be pinned down contractually
  • Thin review corpus — ~13 G2, ~10 Capterra, 2 Gartner Peer Insights
  • Europe-centric support despite 24/7 marketing
  • Limited developer extensibility — no Groovy engine, no public SDK, no script versioning
  • No public throughput SLA or horizontal scale-out architecture
  • No verified BMC Technology Alliance Partner tier — third-party ISV, not OEM
  • Documentation thin beyond Incident/Change flows

Exalate — Evaluated and Excluded

Exalate does not ship a native BMC Remedy connector.

Three signals confirm it.

Exalate — Signal 1

Exalate’s own integrations page and supported-connectors documentation list no BMC product.

[VERIFIED 2026-04-22]

Exalate — Signal 2

Exalate’s own community forum. A user asked:

> “Any plans to integrate with BMC Remedy?”

Response from Francis Martens, Exalate co-founder:

> “This is possible as a custom project — please contact our sales directly for more details.”

[VERIFIED] via https://community.exalate.com/t/any-plans-to-integrate-with-bmc-remedy/4313

No roadmap commitment. The vendor’s own public guidance is: it’s a custom build.

Exalate — Signal 3

Exalate’s own competitive comparison with ZigiOps credits ZigiOps with BMC Helix/Remedy support.

It does not claim equivalent coverage for itself.

[VERIFIED] via exalate.com/blog/zigiops · [BIASED SOURCE — used only to corroborate]

Exalate — What an Engagement Would Actually Look Like

Three paths. None are a product purchase.

  1. Enterprise tier + custom-connector engagement. Pricing, timeline, SLAs unpublished.
  2. Generic HTTP client in Groovy scripts. One-sided adapter, not a peer-to-peer Exalate connection. No Exalate presence on the BMC side — no queue, no retry UI, no replica audit.
  3. Partner-built. No partner publicly advertises a productized BMC Remedy connector.

All three reduce to bespoke engineering.

Exalate — The Rest, Briefly

  • ISO 27001:2022 certified. [VERIFIED]
  • No public SOC 2 Type II report. [UNVERIFIED]
  • Pricing (public): Free · Starter $100/mo · Scale $325/mo · Pro from $550/mo · Enterprise custom
  • BMC Remedy is not included in any published tier. [VERIFIED]
  • Real strengths are Jira↔Jira cross-company and Jira↔ServiceNow. Not this use case.

Note: Exalate is a legitimate and well-built product in its actual market — cross-company Jira integration with asymmetric trust boundaries. It is simply not the product this requirement calls for.

Unito — Evaluated and Excluded

Unito does not ship a native BMC Remedy connector.

Verified on 2026-04-22 against Unito’s own 67-connector catalog.

Unito — The Verification

SourceFinding
unito.io/connectors/67 connectors. Zero BMC products.
unito.io/integrations/No BMC. No “upcoming” BMC.
guide.unito.io/integration-documentationNo BMC docs exist.
bmc.com/partners/bmc-integrations.htmlUnito not listed.

Unito is not a BMC partner.

Unito — What They Actually Do

Positioning: “No-code, 2-way sync in minutes” for cross-SaaS work-management

True strengths:

  • Jira ↔ Asana
  • Trello ↔ GitHub
  • Salesforce ↔ HubSpot
  • ServiceNow ↔ Jira

Not positioned as an enterprise ITSM integrator.

Deployment: SaaS only. AWS US only. No self-hosted, no on-prem, no EU residency.

Unito — Pricing Ladder

PlanPriceUpdate frequencyGating
Basic$99/mo15-min pollingSingle-hub constraint
Pro$299/mo15-min pollingCustom fields
Business$769/moReal-timeAny-to-any
EnterpriseCustomReal-timeSSO, premium connectors

Real-time sync is gated at $769/mo. SSO, Salesforce, ServiceNow, and on-prem connectors are Enterprise-only.

Unito — The Paths, None Good

  1. Commission Unito PS to build a custom connector. Pricing and timeline unpublished.
  2. Build on Unito’s Developer Platform (early access as of Aug 2024). Customer engineering capacity + Remedy REST/AR API knowledge required. Inverts Unito’s “no-code” positioning.
  3. Broker through a middle tool. Architecturally brittle. Defeats the point.

Note: The v1 draft of our due-diligence document spent significant space on Unito’s 15-minute polling delays, hub-tool constraints, and pricing tiers — effectively arguing against a product that doesn’t offer the integration in the first place. The v2 finding is more fundamental and more defensible.

What it is: Jitterbit Harmony, sold and supported by BMC, with BMC-authored Helix connectors and templates.

Relationship: OEM partnership announced in 2021. Same runtime as standard Jitterbit Harmony — Cloud Studio, Jitterscript, API Manager.

Accountability: BMC is the contract party, first-line support, and roadmap owner for BMC-specific content.

BMC iPaaS — Architecture

Cloud Agents — managed by Jitterbit; cloud-to-cloud integrations.

Private Agents — customer-deployed inside the firewall. Outbound-only to Harmony. Required pattern for on-prem BMC Remedy. Clusterable for HA.

Data residency — NA, EMEA, APAC regions.

BMC iPaaS — BMC Connector Coverage

First-class objects:

  • HPD:Help Desk (Incident), CHG:Infrastructure Change, PBM:Problem, SRM, WOI:WorkOrder, AST:Asset, BMC_BaseElement (CMDB), RKM (Knowledge), HPD:WorkLog
  • Attachments via AR System REST
  • Any AR System form via dynamic metadata discovery

Pre-built templates (BMC Marketplace):

  • Helix ↔ ServiceNow / Jira / Salesforce / Azure DevOps
  • Helix Discovery ↔ CMDB federation
  • Helix ↔ Teams / Slack

BMC iPaaS — Pros

  • First-party BMC accountability. Single contract, single roadmap owner.
  • Roadmap alignment. Connector tracks Helix releases contractually.
  • Pre-built Helix templates — genuine accelerators.
  • Full iPaaS, not just ticket sync — same platform handles ERP, HR, CRM, databases.
  • API Manager included. Expose integrations as managed APIs with keys and throttling.
  • CMDB as a first-class citizen — real differentiator for BMC shops.
  • Gartner-recognized iPaaS (Jitterbit Harmony leadership position). [VERIFY current cycle]
  • Private Agents for behind-firewall Remedy.

BMC iPaaS — Cons (Named Honestly)

  • Cost. Highest TCO of the four. Directional: $30K–$250K+/year.
  • Learning curve. Jitterscript is a real scripting language. Not no-code.
  • Implementation effort. 4–12 weeks typical with BMC PS or partner.
  • Overkill for simple Helix↔Jira ticket sync.
  • Quote-based pricing. No transparency. Complicates budgeting.
  • No native loop-prevention — must be engineered.
  • DLQ and replay patterns are custom builds, not turnkey.
  • BYOK may be tier-restricted. Confirm.
  • FedRAMP status — do not assume. Verify.
  • Vendor concentration risk (BMC + Jitterbit).

Note: Stating these plainly is what makes the recommendation credible. A diligence document that lists only pros for the recommended option is a sales pitch, not diligence.

Cost Reality Check

OptionDirectional annual cost (enterprise scope)
Unito Basic / Pro$1.2K – $3.6K
Exalate Starter / Scale$1.2K – $3.4K
Unito Business~$9.2K
Exalate Pro+$6.6K+
ZigiOps (low-five-figures per pair)$12K – $40K
BMC Helix iPaaS$30K – $250K+

BMC iPaaS costs more. Be candid about it.

Note: This slide is the honesty moment. If the integration requirement is narrow, BMC iPaaS is 3–10x more expensive than ZigiOps. The recommendation relies on non-cost factors — accountability, roadmap alignment, platform reusability — actually being worth that premium.

Architecture Comparison

ZigiOpsExalateUnitoBMC iPaaS
Native BMC connector
Config approachNo-code + JSGroovy + AINo-codeLow-code + Jitterscript
DeploymentCloud/on-premCloud/DC nodesSaaS onlyCloud/Private Agents
API ManagementFull suite
Real-time sync$769/mo tier
CMDB first-class✅ (Atrium)

Security Comparison

ZigiOpsExalateUnitoBMC iPaaS
ISO 27001
SOC 2 Type II
HIPAA BAA✅ (eligible tiers)
FedRAMPVerify current
Data residencyOn-prem or SaaSEU/US clustersUS onlyMulti-region
SSOSAML 2.0Limited public docsEnterprise tier onlySAML / OIDC

Commercial Comparison

ZigiOpsExalateUnitoBMC iPaaS
Pricing transparencyQuotePublicPublicQuote
ModelPer system-pairPer active itemsItems + featuresEnterprise capacity
Free tierTrial + PoC
PS engagementBundledSeparateEnterprise-onlySeparate (4–12 wks)
BMC Remedy in pricing?❌ (Enterprise + custom)❌ (custom build)

Recommendation

Primary: BMC Helix iPaaS (Jitterbit-powered)

  1. Only first-party, BMC-accountable option
  2. Roadmap alignment with Helix releases
  3. Platform reusability beyond ticket sync
  4. Enterprise-grade support and compliance
  5. Defensible in audit or board review

When NOT to Pick BMC iPaaS

Stating these makes the recommendation deliberate, not default.

  • Narrow Helix↔one-system requirement with no broader integration roadmapZigiOps
  • Budget is the binding constraintZigiOps
  • Regulated Remedy estate requiring on-prem with zero payload transitZigiOps on-prem install

Note: The counter-scenarios section is important. It shows we considered the opposing case. If the actual scope is narrow ticket sync with no integration growth planned, ZigiOps is genuinely the better call — and the diligence document should say so rather than defaulting to the incumbent.

Explicitly Excluded

Exalate — no native BMC Remedy connector. Vendor’s own public guidance: “custom project.” Strong fit for Jira↔ServiceNow and Jira↔Jira. Not this requirement.

Unito — no native BMC Remedy connector. Work-management sync tool, not an enterprise ITSM integrator. Also US-only data residency is disqualifying for multi-region.

Pre-Purchase Validation

Before signing for BMC iPaaS:

  1. Formal quote against specific scope
  2. Current Gartner MQ placement for Jitterbit
  3. FedRAMP status if federal workload in scope
  4. BYOK availability on intended tier
  5. Reference customer in same vertical and scale

If ZigiOps is the serious alternative:

  1. Explicit Remedy version support matrix in writing
  2. Formal BMC partnership tier
  3. SOC 2 Type II report under NDA
  4. Published uptime SLA for SaaS + on-prem HA
  5. Throughput benchmarks at expected ticket volumes
  6. Per-pair list price, multi-pair discount, renewal uplift cap

Appendix: What We Couldn’t Verify

ZigiOps: BMC partnership tier · SOC 2 Type II · HIPAA BAA · SaaS residency · uptime SLA · version matrix · per-pair pricing

Exalate: SOC 2 Type II · admin SSO · cluster regions · throughput SLA · BMC-specific partner

Unito: ISO 27001 · HIPAA · items-in-sync caps per tier · Enterprise SLA · PS rate card

BMC iPaaS: Current Gartner MQ placement · current FedRAMP status · BYOK tier · throughput benchmarks · current Jitterbit ownership

Stating uncertainty explicitly is the diligence. Documents that claim to verify everything are not credible.

Thanks

Questions?

Full written report: /reports/bmc-integration/

Note: The written report is the source of truth. This deck is a navigation aid. Every claim in the deck is backed by a citation in the written doc.