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.
> “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.
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.”
| ZigiOps | Exalate | Unito | BMC iPaaS | |
|---|---|---|---|---|
| Native Remedy connector | ✅ | ❌ | ❌ | ✅ |
| BMC partner status | Listed | None | None | OEM |
| On-prem option | ✅ | Partial | ❌ | ✅ |
| Pricing transparency | Quote | Public | Public | Quote |
| Shortlist status | Qualified | Rejected | Rejected | Baseline |
[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.
Point-to-point sync tools — ZigiOps, Exalate, Unito
Integration Platform as a Service (iPaaS) — BMC Helix iPaaS
Different categories. Different price points. Different decisions.
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.
Supported objects:
[VERIFIED][VERIFIED][VERIFIED / VENDOR CLAIM][VENDOR CLAIM][VERIFIED][VERIFIED][VENDOR CLAIM]Attachments, work notes, comments: bi-directional [VERIFIED]
Version matrix for Remedy/Helix: not publicly published [UNVERIFIED]
Exalate does not ship a native BMC Remedy connector.
Three signals confirm it.
Exalate’s own integrations page and supported-connectors documentation list no BMC product.
[VERIFIED 2026-04-22]
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’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]
Three paths. None are a product purchase.
All three reduce to bespoke engineering.
[VERIFIED][UNVERIFIED][VERIFIED]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 does not ship a native BMC Remedy connector.
Verified on 2026-04-22 against Unito’s own 67-connector catalog.
| Source | Finding |
|---|---|
| unito.io/connectors/ | 67 connectors. Zero BMC products. |
| unito.io/integrations/ | No BMC. No “upcoming” BMC. |
| guide.unito.io/integration-documentation | No BMC docs exist. |
| bmc.com/partners/bmc-integrations.html | Unito not listed. |
Unito is not a BMC partner.
Positioning: “No-code, 2-way sync in minutes” for cross-SaaS work-management
True strengths:
Not positioned as an enterprise ITSM integrator.
Deployment: SaaS only. AWS US only. No self-hosted, no on-prem, no EU residency.
| Plan | Price | Update frequency | Gating |
|---|---|---|---|
| Basic | $99/mo | 15-min polling | Single-hub constraint |
| Pro | $299/mo | 15-min polling | Custom fields |
| Business | $769/mo | Real-time | Any-to-any |
| Enterprise | Custom | Real-time | SSO, premium connectors |
Real-time sync is gated at $769/mo. SSO, Salesforce, ServiceNow, and on-prem connectors are Enterprise-only.
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.
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.
First-class objects:
Pre-built templates (BMC Marketplace):
[VERIFY current cycle]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.
| Option | Directional 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.
| ZigiOps | Exalate | Unito | BMC iPaaS | |
|---|---|---|---|---|
| Native BMC connector | ✅ | ❌ | ❌ | ✅ |
| Config approach | No-code + JS | Groovy + AI | No-code | Low-code + Jitterscript |
| Deployment | Cloud/on-prem | Cloud/DC nodes | SaaS only | Cloud/Private Agents |
| API Management | — | — | — | Full suite |
| Real-time sync | ✅ | ✅ | $769/mo tier | ✅ |
| CMDB first-class | ✅ (Atrium) | — | — | ✅ |
| ZigiOps | Exalate | Unito | BMC iPaaS | |
|---|---|---|---|---|
| ISO 27001 | ✅ | ✅ | ❓ | ✅ |
| SOC 2 Type II | ❓ | ❓ | ✅ | ✅ |
| HIPAA BAA | ❓ | ❓ | ❓ | ✅ (eligible tiers) |
| FedRAMP | ❓ | ❓ | ❓ | Verify current |
| Data residency | On-prem or SaaS | EU/US clusters | US only | Multi-region |
| SSO | SAML 2.0 | Limited public docs | Enterprise tier only | SAML / OIDC |
| ZigiOps | Exalate | Unito | BMC iPaaS | |
|---|---|---|---|---|
| Pricing transparency | Quote | Public | Public | Quote |
| Model | Per system-pair | Per active items | Items + features | Enterprise capacity |
| Free tier | Trial + PoC | ✅ | ❌ | ❌ |
| PS engagement | Bundled | Separate | Enterprise-only | Separate (4–12 wks) |
| BMC Remedy in pricing? | ✅ | ❌ (Enterprise + custom) | ❌ (custom build) | ✅ |
Primary: BMC Helix iPaaS (Jitterbit-powered)
Stating these makes the recommendation deliberate, not default.
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.
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.
Before signing for BMC iPaaS:
If ZigiOps is the serious alternative:
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.
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.