BMC Remedy Integration — Vendor Due Diligence

A Comparative Due-Diligence Analysis of ZigiOps, Exalate, Unito, and BMC Helix iPaaS (Jitterbit)

Prepared: 2026-04-22 · Version 2.0 (supersedes v1)

Change Log — What Is Different From Version 1

This revision is a substantive rewrite, not a touch-up. The two most consequential changes:

1. Two of the three third-party alternatives do not actually offer a native BMC Remedy connector. Version 1 treated Exalate and Unito as viable BMC Remedy integration options. Direct verification of vendor catalogs, documentation, community forums, and BMC’s partner marketplace on 2026-04-22 shows neither vendor ships a productized BMC Remedy / BMC Helix ITSM / BMC AR System connector. Any integration is a bespoke engineering engagement, not a product purchase. This is a decisive due-diligence finding that v1 did not surface.
2. The honest case for BMC Helix iPaaS is made alongside its honest cons. Version 1 read as promotional in places. This revision adds counter-scenarios (“when NOT to choose BMC iPaaS”) and clearly flags BMC iPaaS’s real drawbacks: it is the most expensive of the four options, has a genuine learning curve (Jitterscript is a real scripting language), has no native loop-prevention for bi-directional sync, and sometimes requires BYOK and FedRAMP confirmations that should not be assumed.

Other material corrections:

• Exalate’s security posture: v1 cited SentinelOne EDR and implied SOC 2 coverage. Current Exalate public pages reference NVISO SOC + Palo Alto Cortex MDR, and publish ISO 27001:2022 only — no SOC 2 Type II report is publicly advertised. Corrected.
• Exalate pricing: v1 quoted annual-billed monthly rates ($85 / $280 / $550) without naming them as such. V2 shows both monthly-billed ($100 / $325 / $550+) and annual-billed rates, plus the free tier and explicit note that BMC Remedy is not included in any published pricing tier.
• Unito pricing: v1 missed the Business tier at $769/mo (the actual real-time-enabled tier) and conflated it with Enterprise. V2 shows the full public ladder plus the caveat that SSO/SAML, on-prem connectors, and premium connectors are Enterprise-only.
• Unito data residency: v1 did not flag that Unito is US-only (AWS US). V2 adds this as a hard constraint for multi-region enterprises.
• Claim hygiene: verification tags ([VERIFIED], [UNVERIFIED], [VENDOR CLAIM], [BIASED SOURCE]) now appear inline so the reader can distinguish product fact from marketing copy without chasing footnotes.

Line-for-line change trace between v1 and v2 is available on request.

TL;DR — Read This If You Read Nothing Else

• Of the three third-party alternatives, only ZigiOps has a real, productized BMC Remedy connector. Exalate and Unito do not. This reduces the meaningful shortlist to BMC Helix iPaaS (incumbent) vs ZigiOps.
• BMC Helix iPaaS (Jitterbit-powered) is the recommended choice because it is the only first-party, BMC-supported platform with roadmap alignment to Helix, a full iPaaS feature set (API Manager, 500+ connectors, on-prem agents), and enterprise support and compliance posture. This is a defensible recommendation in an audit or board review.
• BMC Helix iPaaS is also the most expensive of the four, has a steeper learning curve, and is overkill if the only requirement is one or two simple ticket syncs. ZigiOps is the right pick when the requirement is strictly bi-directional Remedy ↔ ServiceNow / Jira / monitoring-tool sync at lower TCO.
• Exalate is rejected on native-connector grounds. In Exalate’s own community forum, co-founder Francis Martens states BMC Remedy support is “possible as a custom project” — i.e., not productized.
• Unito is rejected on native-connector grounds. Its 67-connector catalog contains zero BMC products; Unito is not a BMC partner; Unito’s center of gravity is work-management sync (Jira↔Asana patterns), not enterprise ITSM.

The rest of this document shows the work.

How We Verified Each Claim

Every non-trivial factual claim in this document carries a verification tag:

• [VERIFIED] — confirmed against a first-party vendor page, official documentation, or regulator/marketplace listing, with a URL cited inline.
• [VENDOR CLAIM] — stated by the vendor in marketing or sales collateral but not independently corroborated. Treated as provisional.
• [BIASED SOURCE] — sourced from a competitor’s comparison page. Used only when the claim is not in dispute and no cleaner source was available.
• [UNVERIFIED] — could not be confirmed from any reliable public source; flagged explicitly rather than asserted.

A consolidated list of all items we could not verify appears in the appendix. This is deliberate — a due-diligence document that claims to have verified everything is not credible. Marking our uncertainty is the rigor.

Primary verification conducted on 2026-04-22 against vendor sites, documentation portals, BMC Marketplace, OpenText ITOM Marketplace, Atlassian Marketplace, G2, Capterra, TrustRadius, Gartner Peer Insights, and Crunchbase. Dates of subsequent re-verification, if any, should be appended here before the document is used for binding procurement.

At-A-Glance Verdict Matrix

Architectural Paradigms — What These Tools Actually Are

Before comparing vendors, distinguish the two product categories in play.

Point-to-point synchronization platforms — ZigiOps, Exalate, Unito — are designed to keep records aligned across two systems. Their primary job is bi-directional field mapping, conflict resolution, and loop prevention. They excel at “Incident 1234 in Remedy mirrors Ticket INC-567 in ServiceNow” patterns. They are not general-purpose orchestration tools and they do not ship API management, ETL tooling, or event-stream processing.

Integration Platform as a Service (iPaaS) — BMC Helix iPaaS (Jitterbit), MuleSoft, Workato — are full integration platforms. They do bi-directional sync, but they also do ETL, API management, event-driven orchestration, hybrid SaaS-plus-on-prem bridging, and broad application coverage (ERP, HR, finance, CRM). The tradeoff is complexity and cost: iPaaS platforms are more capable and more expensive.

Pick a point-to-point tool if the integration requirement is narrow, well-defined, and unlikely to expand. Pick an iPaaS if you anticipate integration surface growth beyond ITSM — HR-to-AD provisioning, CMDB-to-asset-system federation, ERP bridging, API-led architecture for new services.

ZigiOps (ZigiWave) — The Qualified Alternative

Headline: ZigiOps is the only third-party vendor of the three that genuinely ships a productized BMC Remedy connector. It is a credible, narrower, and cheaper alternative to BMC Helix iPaaS for narrow bi-directional sync use cases.

Company and Product

• Company: ZigiWave (Sofia, Bulgaria), founded 2020. [VERIFIED] via Crunchbase; earlier Gartner listing shows 2019 — minor discrepancy.
• Leadership: Mariya Zasheva (CEO), Idan Harel (Co-founder/Chairman), Avi Koren (Co-founder/CTO). [VERIFIED] via https://zigiwave.com/company
• Scale claims: 30+ engineers, 100+ customers, “60+ Fortune 500 customers.” [VENDOR CLAIM] Named customers include NASDAQ, FedEx, Delta Dental, TELUS, Vodafone, Schlumberger, Cambia Health, Singtel. [VERIFIED via customers page]
• Certifications: ISO/IEC 27001 certified October 2022. [VERIFIED] via https://www.zigiwave.com/resources/zigiwave-iso-27001. FIPS 140-2 alignment claimed for config-data encryption; no CMVP certificate number cited. [VENDOR CLAIM]
• BMC partnership: Appears in BMC’s partner locator historically; does not visibly appear on the current https://www.bmc.com/partners/bmc-integrations.html page. No evidence of BMC Technology Alliance Partner tier. Listed as OpenText ITOM Marketplace partner at “SUPPORTED” tier with a dedicated “ZigiOps for BMC Remedy” listing. [VERIFIED at OpenText] BMC tier status is [UNVERIFIED].

Deployment and Architecture

• Deployment models: On-prem (Windows/Linux; Java-based installer requiring Oracle Java 17 or OpenJDK 17), SaaS on AWS, or customer-managed cloud. [VERIFIED] via install docs.
• Architecture: Agentless, stateless, standalone. Outbound API calls only; no agents inside source/target systems. Zero-data-retention for transaction payloads (config data is persisted and encrypted); operates as webhook listener or poller. [VENDOR CLAIM — consistent with public architecture docs]
• HA: Standby-server model claimed, no published SLA. [UNVERIFIED] for specific uptime guarantees.

BMC Remedy Connector Specifics

• Authentication: Username/password against Remedy AR user; no public mention of Remedy SSO, Kerberos, or OAuth. [VERIFIED via docs] [GAP: modern SSO patterns unconfirmed]
• Objects supported: Incident [VERIFIED via docs], Change Request [VERIFIED via docs], Problem [VENDOR CLAIM], Work Order [VENDOR CLAIM], Task [VERIFIED via apps page], CMDB / BMC Atrium CI sync [VERIFIED via ServiceNow integration page], Events/Alerts [VERIFIED], Custom forms [VENDOR CLAIM] via schema discovery on the AR System Metadata ARSchema surface.
• Fields and data types: Text, numeric, date, dropdown, multi-select, checkbox, user/assignee, attachment, custom. Bi-directional. [VERIFIED via apps/integrations pages]
• Attachments and work notes: Supported, bi-directional. [VERIFIED]
• Dynamic schema discovery: ZigiOps reads Remedy schemas on connect, so custom fields surface in the mapper without manual scripting. [VENDOR CLAIM — consistent with docs screenshots]
• Loop prevention: Implemented via correlation fields (e.g., a Jira custom field holding the Remedy request ID). [VERIFIED]
• Remedy version matrix: Not publicly published. FAQ states only “supports latest versions.” This is a material gap — a Remedy estate on 9.1, 19.x, 20.x, or 22.x should confirm version coverage contractually before signing. [UNVERIFIED]

Sync Features

Real-time (webhook listener) and scheduled polling modes [VERIFIED]. Conditional field mapping and UI-built filters, with optional JS Mapping Expression as the scripting escape hatch [VERIFIED]. No Groovy engine, no public custom-connector SDK, no published script versioning, no dedicated staging/test environment flagged in public docs. These are real limitations relative to Exalate’s scripting engine or Jitterbit’s Cloud Studio — [BIASED SOURCE] Exalate’s competitive comparison flags the same gaps, which corroborates the absence of public developer docs.

Security and Compliance

• ISO 27001 certified. [VERIFIED]
• Encryption: TLS 1.3 in transit, FIPS 140-2-aligned at rest for config data. [VENDOR CLAIM]
• SSO: SAML 2.0 with documented Okta integration. [VERIFIED via docs]
• SOC 2 Type II: Positioned as a tool that enables customer compliance rather than as a directly audited entity. Not advertised as holding a SOC 2 Type II report. [UNVERIFIED — confirm in procurement]
• HIPAA: Not advertised as HIPAA-ready with BAA. [UNVERIFIED]
• Data residency: SaaS region not publicly specified. [UNVERIFIED]
• Customer data flow: On-prem install keeps all payload data inside customer perimeter. SaaS transits ZigiOps AWS infrastructure but is not persisted. [VERIFIED architecture]

Pricing

• Model: Annual subscription per system pair (e.g., Remedy ↔ ServiceNow is one pair), not per user or per record. Unlimited data volume within a licensed pair.
• Bundled: Implementation and support included in the subscription — no separate PS line item. [VERIFIED via FAQ and reseller listings]
• Quotes only on the website. Indicative floor from SourceForge listing: $500/month ($6K/year) per pair. SaaSworthy references “~$300/month” for a Basic package. [UNVERIFIED for specific scope]
• Typical enterprise ACV per pair: Low five figures per pair per year, with multi-pair and partner/reseller discounts (20–50%). [ESTIMATE — triangulated from reseller data, not a vendor quote]

Pros

1. Genuinely no-code for standard ITSM-to-ITSM patterns; short time-to-first-sync.
2. On-prem deployment keeps data inside customer perimeter — material for regulated-industry Remedy shops.
3. Flat per-pair pricing avoids per-transaction metering that bites Workato and MuleSoft for high-volume ITSM flows.
4. Broad monitoring/AIOps connector coverage (Datadog, Dynatrace, Splunk, Prometheus, OpsBridge, AppDynamics, New Relic) is deeper than Jitterbit’s stock library for observability-to-ITSM use cases.
5. Bundled implementation and support — no separate PS engagement needed for standard patterns.
6. ISO 27001 certified.

Cons

1. Opaque Remedy/Helix version support matrix — “latest version” is the only public stance.
2. Thin review corpus (~13 on G2, ~10 on Capterra, 2 on Gartner Peer Insights) — ratings are positive but statistically weak.
3. Europe-centric support reality despite 24/7 marketing claim; follow-the-sun coverage [UNVERIFIED].
4. Limited developer extensibility — no Groovy, no public SDK, no script versioning, no explicit staging/test environment in public docs.
5. No public throughput SLA, concurrency benchmark, or horizontal scale-out architecture.
6. Documentation depth is thin for BMC-specific topics beyond Incident and Change. Work Order, Task, Problem, and CMDB flows are marketing-mentioned but not step-by-step-documented.
7. No verified BMC Technology Alliance Partner tier — third-party ISV, not OEM.
8. Jira Marketplace listing caps Jira Server at 8.5.5; newer Jira DC 9.x/10.x coverage is unverified in the listing.

ZigiOps Verdict

Qualified alternative to BMC Helix iPaaS if the integration requirement is narrow (e.g., strictly Remedy ↔ ServiceNow plus a couple of monitoring tool side-channels) and the primary decision driver is TCO. ZigiOps is materially cheaper than BMC Helix iPaaS and its on-prem, zero-data-retention architecture is attractive for regulated Remedy estates. It does not replace a true iPaaS for broader enterprise integration needs and it does not offer the first-party BMC accountability that BMC Helix iPaaS provides.

Exalate — Evaluated and Excluded (No Native BMC Connector)

Headline: Exalate does not ship a native connector for BMC Remedy, BMC Helix ITSM, or BMC AR System. This is the dispositive finding and it is confirmed by three independent signals.

The Three Signals

1. Exalate’s integrations page and supported-connectors documentation list no BMC product. [VERIFIED 2026-04-22] via https://exalate.com/integrations/ and https://docs.exalate.com/docs/exalate-supported-integrations.
2. Exalate’s own community forum contains a single public thread asking “Any plans to integrate with BMC Remedy?” The response, from co-founder Francis Martens: “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 exists.
3. Exalate’s own competitive comparison with ZigiOps credits ZigiOps with BMC Helix/Remedy support and does not claim equivalent coverage for itself. [VERIFIED] via https://exalate.com/blog/zigiops/ [BIASED SOURCE — self-declared competitor comparison, used here only to corroborate the non-support finding].

Company and Product Background

• Origin: Originally built inside iDalko (Antwerp, Belgium) beginning around 2015; Exalate and iDalko split into independent entities in May 2023, with Exalate becoming a pure-play integration software company. [VERIFIED] via https://siliconcanals.com/ and https://exalate.com/who-we-are/.
• HQ: Antwerp, Belgium.
• Leadership: Francis Martens (CEO), Hilde Van Brempt (COO), Bruno Dauwe (Head of Product).
• Scale claims: 2,500+ customers, 8,000+ active installs, “30% of Fortune Top 50.” [VENDOR CLAIM]
• Center of gravity: Jira-centric (Jira↔Jira cross-company, Jira↔ServiceNow, Jira↔Azure DevOps). ServiceNow is the most mature non-Jira connector.
• BMC partner status: None. Not listed on BMC’s integration partner page. No BMC Technology Alliance Partnership. No BMC-focused implementation partners surfaced in Exalate’s 200+ partner network. [VERIFIED absent]

What an Exalate-Based BMC Integration Would Actually Look Like

Because no native connector exists, the only paths are:

1. Exalate Enterprise tier + custom-connector engagement. This is the vendor’s officially acknowledged route per the community forum response. Pricing, timeline, and SLAs are unpublished. [UNVERIFIED]
2. Generic HTTP client from within Groovy sync scripts. Exalate’s httpClient inside script rules can call arbitrary REST APIs. In practice this means one Exalate node on a supported system (e.g., Jira) with custom Groovy scripts calling Remedy’s REST API. The BMC side has no Exalate presence — no queue, no error retry UI, no replica auditing on the Remedy end. This is a one-sided adapter, not a peer-to-peer Exalate connection.
3. Partner-built integration. Exalate references 200+ certified partners; none publicly advertise a productized BMC Remedy connector. [UNVERIFIED]

All three paths reduce to bespoke engineering — the opposite of purchasing a productized integration.

Security and Pricing (For Completeness)

• Certifications: ISO/IEC 27001:2022 [VERIFIED]. No public SOC 2 Type II report advertised on exalate.com/security or the Trust Center. [UNVERIFIED]
• Architecture: Decentralized node-to-node with single-tenant Exalate Cloud nodes and JWT-signed peer-to-peer messages. This is a genuine differentiator for Jira↔Jira cross-company scenarios where neither side trusts the other with config. It is irrelevant for a BMC Remedy scenario where no Exalate node exists on the Remedy side.
• Security monitoring: NVISO SOC + Palo Alto Cortex MDR EDR [VERIFIED on current security page]. Note: v1 of this document referenced SentinelOne — that was a legacy reference; the current vendor security page lists Cortex MDR.
• Pricing ladder (public): Free ($0, 1,000 entities/month, 4 fields) · Starter ($100/mo monthly or $85/mo annual, 25 active items) · Scale ($325/mo monthly or $280/mo annual, 100 active items) · Pro (from $550/mo annual only) · Enterprise (custom). [VERIFIED] via https://exalate.com/pricing/.
• BMC Remedy is not included in any published tier. Custom-connector engagement requires Enterprise tier. [VERIFIED via comparison of tier connector lists]

Exalate Verdict

Evaluated and excluded as a primary BMC Remedy integration platform. The product does not address the requirement natively and the vendor’s own public guidance is to treat it as a custom-build engagement. Exalate remains a legitimate choice for Jira↔ServiceNow or Jira↔Jira cross-company synchronization — its decentralized architecture and scripting flexibility are genuinely strong in those scenarios — but that is not the requirement here.

Unito — Evaluated and Excluded (No Native BMC Connector)

Headline: Unito does not ship a native BMC Remedy or BMC Helix ITSM connector. Verified against Unito’s own 67-connector catalog on 2026-04-22. Unito is not a BMC partner. Unito’s product is work-management sync (Jira↔Asana patterns), not enterprise ITSM integration.

The Verification

[VERIFIED 2026-04-22]

Company and Product Background

• Company: Unito Inc., Montreal, Canada. Founded 2015 (Crunchbase) or 2016 (About Us page) — minor discrepancy. [UNVERIFIED which is incorporation vs product launch]
• Funding: ~$33.1M total across pre-seed, seed, Series A, and a $20M Series B in October 2022 led by CDPQ’s Equity 253 fund. [VERIFIED]
• Customers: HubSpot, HP, Wix, Warner Bros, Logitech, EY, Cornell, MIT, Stanford. [VERIFIED via case studies and about page]
• Deployment: SaaS only, AWS US regions. No self-hosted, on-prem, or customer-VPC option. [VERIFIED]
• Positioning: “No-code, 2-way sync in minutes” for cross-SaaS work-management scenarios. True strengths are Jira↔Asana, Trello↔GitHub, Salesforce↔HubSpot, ServiceNow↔Jira, and similar work-management-to-work-management patterns. Not positioned as an enterprise ITSM integration platform.

Paths to a Unito-Based Remedy Integration (None Are Good)

1. Commission a custom connector from Unito Professional Services. Pricing and timeline are unpublished. [UNVERIFIED]
2. Build a private connector on Unito’s Developer Platform (in early access as of August 2024). Requires the customer to have engineering capacity and Remedy REST/AR API knowledge. This inverts Unito’s entire “no-code, minutes-to-value” positioning.
3. Broker through a middle tool (e.g., Remedy → ServiceNow via some other mechanism, then ServiceNow ↔ Unito). Architecturally brittle, adds a failure surface, defeats the purpose.

Public Pricing Ladder (Third-Party-Aggregated)

[VERIFIED] via Capterra/GetApp aggregators. Unito’s own pricing page does not publish dollar amounts.

Notable commercial facts:

• No free tier. 14-day free trial only.
• Real-time sync is gated to Business tier ($769/mo) and above. Basic and Pro are 15-minute polling — operationally unacceptable for P1 ITSM escalation.
• ServiceNow, Salesforce, Jira On-Prem, Jira Data Center, Eloqua are Enterprise-only connectors. A hypothetical BMC connector, if ever built, would almost certainly be Enterprise-only as well.
• Items-in-sync caps per tier are visible only in-app or via sales, not public.

Security and Compliance

• SOC 2 Type II certified. [VERIFIED]
• GDPR compliant; SCCs for EU→US transfer; DPA available. [VERIFIED]
• Data residency: AWS US only. No EU, Canadian, or APAC residency option. Hard constraint for customers with residency obligations in those regions. [VERIFIED]
• HIPAA: Not advertised. [UNVERIFIED] — relevant if Remedy workflows touch PHI.
• ISO 27001: Not advertised on security page. [UNVERIFIED]
• SSO/SAML: Enterprise tier only. [VERIFIED]

Unito Verdict

Evaluated and excluded on native-connector grounds. Unito is a credible and competent product in its actual market — cross-SaaS work-management sync — but that is not this use case. The premise of Unito as a BMC Remedy integration tool does not hold up to primary-source verification.

For documentation-audit purposes: the v1 draft’s detailed discussion of Unito’s 15-minute polling delays, hub-tool constraints, and $30/user Team tier was arguing against a product that does not offer the integration in the first place. The v2 finding is more fundamental and more defensible.

BMC Helix iPaaS (Powered by Jitterbit) — The Recommended Baseline

Headline: BMC Helix iPaaS is Jitterbit Harmony, sold and supported by BMC, pre-packaged with BMC-authored connectors and templates for Helix ITSM, Remedy, Discovery, and CMDB. It is the only first-party, BMC-accountable option and it is the recommended baseline — with clear cons that we name honestly.

What It Is

• Relationship: OEM partnership between BMC and Jitterbit announced in 2021. BMC Helix iPaaS is not a fork — customers receive the same underlying runtime (Cloud Studio, Jitterscript, API Manager, connector catalog) as standard Jitterbit Harmony customers, plus BMC-authored Helix-specific templates and connectors. [VERIFIED]
• BMC as contracting party: BMC owns the contract, first-line support, and roadmap responsibility for the BMC-specific content. Jitterbit is the runtime provider behind the scenes.

Architecture

• Platform: Jitterbit Harmony, multi-tenant cloud iPaaS on AWS.
• Cloud Agents: Managed by Jitterbit, used for cloud-to-cloud integrations (Helix SaaS ↔ ServiceNow, Helix SaaS ↔ Salesforce).
• Private Agents: Customer-deployed (Windows/Linux/Docker) inside the customer network. Outbound-only to Harmony. Required pattern for on-premise BMC Remedy. Can be clustered for HA.
• Data residency: Multi-region — NA (US), EMEA (EU), APAC. Customers typically provisioned in the region matching their Helix tenant. [VERIFY current region list for EMEA/APAC specifics]

BMC Connector Specifics

• Native BMC Helix / Remedy connector. [VERIFIED]
• Objects supported: HPD:Help Desk (Incident), CHG:Infrastructure Change, PBM:Problem, SRM (service requests), WOI:WorkOrder, AST:Asset, BMC_BaseElement (CMDB CIs via Atrium), RKM (Knowledge), HPD:WorkLog (worklogs), attachments via AR System REST.
• Custom form support: Any AR System form — connector uses dynamic metadata discovery in Cloud Studio.
• Bi-directional mapping: Supported, configured as independent inbound/outbound flows. This is more flexible than a single two-way “sync object” but requires more explicit configuration.
• Attachments: Supported. Large-attachment handling depends on Private Agent memory sizing.
• Worklog sync: Supported; multiple BMC-authored templates include worklog propagation.
• CMDB: CMDB federation and CI sync via Atrium CMDB / Helix CMDB REST. First-class capability — ZigiOps, Exalate, and Unito do not treat CMDB as a first-class object catalog.
• Helix SaaS vs on-prem Remedy: Connector supports both. On-prem Remedy requires Private Agent deployment inside the customer network; authentication via Remedy credentials or RSSO.

Pre-Built BMC Templates (Published on BMC Marketplace)

Common reference templates:

• BMC Helix ITSM ↔ ServiceNow (incident bridging)
• BMC Helix ITSM ↔ Jira (Software and JSM)
• BMC Helix ITSM ↔ Salesforce Service Cloud
• BMC Helix ITSM ↔ Microsoft Azure DevOps
• BMC Helix Discovery ↔ BMC Helix CMDB
• BMC Helix ITSM ↔ Teams / Slack (notifications)
• BMC Helix ITSM ↔ SAP (typically custom-extended)

Exact current template catalog changes; verify at https://marketplace.bmc.com.

Development Model

• Cloud Studio: Browser-based visual designer. Not a desktop IDE (replaces legacy Design Studio).
• Jitterscript: Jitterbit’s proprietary transformation language. Required for any non-trivial transform — conditionals, array manipulation, caching, sub-operation calls, DB lookups. It is a real scripting language with a real learning curve. Developers with JavaScript/PL-SQL backgrounds pick it up quickly, but this is not no-code. Plan for dedicated integration developers or Jitterbit-trained partners.
• API Manager: Built-in API gateway — exposes integrations as managed REST APIs with keys, throttling, and developer portal. Enables “integration-as-an-API” patterns. None of the three alternatives offer comparable capability.
• Connector catalog: Hundreds of pre-built connectors across ERP, CRM, HR, databases, cloud platforms. Commonly marketed as “500+” though the exact number varies by source and date. [VENDOR CLAIM — directional, not audited]

Security and Compliance

• SOC 2 Type II: Maintained (Jitterbit). [VERIFIED via trust.jitterbit.com]
• ISO/IEC 27001: Maintained. [VERIFIED]
• HIPAA: BAA available for eligible plans. Verify tier eligibility at procurement. [VERIFIED availability; tier dependencies exist]
• GDPR: Compliant, EU DPA available.
• FedRAMP: Do not assume. Status changes over time; verify at https://marketplace.fedramp.gov before relying on it for regulated federal workloads. [UNVERIFIED for current cycle]
• SSO: SAML 2.0 and OIDC. RBAC on projects, environments, and agents.
• Encryption: TLS 1.2+ in transit; AES-256 at rest for Harmony-stored metadata and logs.
• Customer-managed keys (BYOK): Historically tier-restricted or limited. [UNVERIFIED for current cycle — a frequent enterprise due-diligence ask]

Scalability

Harmony scales horizontally by adding Private Agent Groups and via Harmony auto-scaling for Cloud Agent workloads. Real throughput depends on endpoint API limits (Remedy REST rate limits, Helix SaaS throttles), record size, transformation complexity, and agent sizing. Jitterbit publishes directional throughput claims; they are not independently benchmarked. [VENDOR CLAIM] Standard platform SLA is 99.9% uptime; higher tiers available.

Pricing (Directional, Not Quoted)

• Model: Quote-based. No list prices published.
• Directional ranges from historical anecdotes (Gartner Peer Insights, reseller listings):
  • Entry: $30K–$50K/year for small deployments
  • Mid-market: $50K–$100K/year
  • Enterprise: $100K–$250K+/year with multi-region, premium support, high message volume
• BMC Helix iPaaS bundling: Can be an add-on to an existing Helix ELA; the incremental cost depends on the overall BMC commitment.

This is the most expensive of the four options in virtually all realistic scenarios. Do not oversell this in the recommendation.

Pros

1. First-party BMC accountability. Single contract, single support path, single roadmap owner. When a Helix upgrade breaks an integration, BMC owns the fix — not a third-party ISV wearing a user hat in a support ticket.
2. Roadmap alignment. BMC-authored connectors and templates track Helix ITSM releases. Contractual incentive to keep the connector current.
3. Pre-built Helix templates — genuine accelerators for ServiceNow, Jira, Salesforce, Azure DevOps, CMDB federation.
4. Full iPaaS, not just ticket sync. Same platform can handle Workday → AD provisioning, SAP → CMDB asset sync, Salesforce → Helix case federation. If the enterprise has integration needs beyond Helix ticket sync, the TCO gap to the alternatives narrows or reverses.
5. Gartner-recognized iPaaS. Jitterbit Harmony has been positioned as a Leader in recent Gartner Magic Quadrants for Enterprise iPaaS. [VERIFY current cycle before relying]
6. Enterprise support options — 24/7 Premier, named TAMs on higher tiers.
7. Private Agent architecture — genuine support for behind-firewall Remedy, on-prem databases, SAP, mainframe adapters.
8. API Manager included — capability that ZigiOps, Exalate, and Unito do not meaningfully offer.
9. CMDB as a first-class citizen — real differentiator for BMC shops.

Cons (Named Honestly)

1. Cost. Highest TCO of the four candidates. For simple bi-directional ticket sync between Helix and one other system, BMC Helix iPaaS is overkill and expensive.
2. Learning curve. Cloud Studio is visual but not trivial. Jitterscript is a real scripting language. Non-trivial transforms require developer skills. ZigiOps (no-code) is meaningfully easier for business-admin owners of simple flows.
3. Implementation effort. Typical initial deployment is 4–12 weeks with BMC PS or a partner. ZigiOps deployments can be days to weeks for the same scope.
4. Overkill for narrow use cases. If the requirement is strictly “sync incidents between Helix and Jira,” ZigiOps typically delivers the same outcome faster and cheaper.
5. Quote-based pricing. Reduces transparency. Complicates budget planning and vendor comparison.
6. Vendor concentration risk. Customers sign with BMC but depend on Jitterbit for the runtime. Any friction in the BMC↔Jitterbit commercial relationship is a customer risk. Historically low-risk, but real.
7. No native loop-prevention for bi-directional ticket sync. Must be engineered — typically via marker fields, external-reference-ID checks, timestamp watermarks. Unito offers this natively. Exalate has structured two-way semantics built in. Jitterbit requires developer-authored loop guards.
8. Dead-letter queue and replay patterns are custom. Not turnkey.
9. Customer-managed keys / BYOK may be tier-restricted. Confirm.
10. FedRAMP status should not be assumed. Confirm for regulated workloads.
11. Jitterbit ownership/M&A context. Jitterbit has had private-equity ownership changes (notably Vista Equity Partners). Normal for the category, but worth flagging as a minor strategic-risk factor. [VERIFY current ownership]

Comparison Matrices

Matrix 1: Architecture and Capability

Matrix 2: Security, Governance, Control

Matrix 3: Commercial and TCO

Strategic Recommendation

Primary Recommendation: BMC Helix iPaaS (Jitterbit-Powered)

For an enterprise standardized on BMC Helix ITSM or BMC Remedy with enterprise procurement, security, and compliance standards, BMC Helix iPaaS is the recommended baseline. The justification is defensible without oversell:

1. Only first-party, BMC-accountable option. When a Helix upgrade breaks an integration, BMC owns the fix. Third-party ISVs have commercial incentives but not contractual obligations tied to BMC release cycles.
2. Roadmap alignment. BMC’s connector and template maintenance tracks Helix releases.
3. Platform reusability beyond Remedy sync. ZigiOps, Exalate, and Unito are narrow-scope ticket-sync tools. BMC Helix iPaaS is a general-purpose iPaaS — the same platform handles HR-to-AD provisioning, ERP-to-CMDB federation, and arbitrary future integrations. If the enterprise integration surface will grow, the TCO gap to alternatives narrows or reverses.
4. Enterprise-grade support and SLA — 24/7 Premier, named TAMs, BMC’s global footprint.
5. Security/compliance posture — SOC 2 Type II, ISO 27001, HIPAA availability generally meet or exceed the specialized competitors.
6. Defensibility. “We chose the BMC-recommended, Gartner-Leader-backed platform with single-vendor accountability” is easier to defend in an audit than “we chose a best-of-breed third-party sync tool,” even when the third-party tool is functionally adequate.

When NOT to Choose BMC Helix iPaaS (Counter-Scenarios)

Stating these plainly strengthens the recommendation by showing it is deliberate, not default:

• Scope is strictly Helix ↔ one or two SaaS systems with no broader integration roadmap → ZigiOps likely delivers faster and at materially lower cost. The bundled implementation and per-pair pricing are materially advantageous here.
• Budget is the binding constraint and ticket sync is the only requirement → ZigiOps.
• Regulated-industry Remedy estate requiring on-prem deployment with zero payload transit to an iPaaS vendor’s cloud → ZigiOps on-prem install, subject to confirming their SaaS-vs-on-prem feature parity in the specific scope.

Explicitly Excluded

• Exalate — no native BMC Remedy connector. Any engagement is a custom-build project wearing a vendor wrapper. Vendor’s own community-forum position is “custom project” only. Strong fit for Jira↔ServiceNow and Jira↔Jira cross-company, but that is not this requirement.
• Unito — no native BMC Remedy connector. Product is a work-management sync tool, not an enterprise ITSM integrator. Also carries a US-only data residency constraint that is disqualifying for multi-region enterprises.

Pre-Purchase Validation Checklist

Before signing for BMC Helix iPaaS:

1. Obtain a formal BMC quote against the specific scope (endpoints, environments, message volume).
2. Confirm current Gartner MQ placement for Jitterbit.
3. Verify FedRAMP authorization status at marketplace.fedramp.gov if any federal workload is in scope.
4. Confirm customer-managed key (BYOK) availability on the intended tier.
5. Request a reference customer in the same vertical and roughly the same scale.
6. Pull 10–20 recent Gartner Peer Insights reviews of Jitterbit Harmony and summarize top praise and top complaints into procurement.

If ZigiOps is being seriously considered as the alternative:

1. Explicit Remedy ITSM version support matrix — AR System 9.x/18.x/19.x/20.x/21.x/22.x/23.x, Helix ITSM 20.x+.
2. Formal BMC partnership tier confirmation in writing.
3. SOC 2 Type II report availability under NDA.
4. HIPAA BAA willingness if PHI is in scope.
5. SaaS data residency options (US vs EU region pinning).
6. Published uptime SLA for both SaaS and on-prem HA claim.
7. Throughput benchmarks for Remedy ↔ ServiceNow at the relevant ticket volumes.
8. Horizontal scale-out architecture for the on-prem edition — or confirmation that it is vertical-only.
9. Per-pair list price, multi-pair discount schedule, renewal uplift cap.
10. Custom-form / custom-AR-workflow support depth beyond Incident/Change masters.
11. CMDB reconciliation depth against BMC Atrium (CDM classes, normalization, federation tokens).
12. Published support SLAs (P1/P2/P3 response and resolution targets); true follow-the-sun coverage map.

Appendix: Items We Could Not Verify

Stated explicitly so a reader can see the edges of our diligence. None of these are disqualifying; they are simply open questions that should be closed in procurement.

ZigiOps: formal BMC partnership tier; SOC 2 Type II report; HIPAA BAA; SaaS data residency; uptime SLA; horizontal scale-out; true 24/7 support; Remedy/Helix version matrix; published per-pair pricing; custom-form depth beyond Incident/Change; CMDB reconciliation depth.

Exalate: exact current headcount; SOC 2 Type II; HIPAA/PCI posture; SAML/OIDC for Exalate admin console; Cloud cluster regions; throughput SLA; bulk portability tooling; any partner specializing in BMC Remedy; current Atlassian Marketplace Partner level post-July-2025 restructuring.

Unito: ISO 27001 status; HIPAA status; exact annual-discount percentages; per-tier items-in-sync caps (visible only in-app); Enterprise SLA terms; PS rate card for custom connectors; exact customer count; 2015-vs-2016 founding-year discrepancy.

BMC Helix iPaaS: exact GA launch month; current Gartner MQ placement; current FedRAMP authorization status; current pricing ranges (directional only); current BMC Marketplace template list; BYOK availability by tier; specific throughput/TPS benchmarks; current Jitterbit corporate ownership.

Sources

ZigiOps

• https://zigiwave.com/company, /customers, /partners
• https://www.zigiwave.com/zigiops-integration-platform, /zigiops-security, /zigiops-pricing, /frequently-asked-questions
• https://www.zigiwave.com/apps/bmc-remedy-integrations
• https://www.zigiwave.com/integrations/bmc-remedy-servicenow-integration, /jira-bmc-remedy-integration
• https://www.zigiwave.com/resources/zigiwave-iso-27001
• https://docs.zigiwave.com/zigiops/ (full docs portal including install, remedy-incidents-to-jira-tasks, remedy-change-requests-to-jira-tasks, general-settings)
• https://marketplace.atlassian.com/apps/1221587/bi-directional-bmc-remedy-integration-for-jira-by-zigiops
• https://marketplace.opentext.com/itom/content/zigiops-for-bmc-remedy, /partner/zigiwave
• https://www.capterra.com/p/189181/ZigiOps/, https://www.getapp.com/it-management-software/a/zigiops/
• https://sourceforge.net/software/product/ZigiOps/, https://reviews.financesonline.com/p/zigiops/
• https://www.trustradius.com/products/zigiops/reviews, https://www.g2.com/products/zigiops/reviews

Exalate

• https://exalate.com/ (homepage, how-exalate-works, integrations, pricing, security, who-we-are, case-studies, partners, support-plans)
• https://docs.exalate.com/ (overview-what-is-exalate, exalate-supported-integrations, sync-rules, scripts, error-handling, what-is-exalate-cloud, exalate-subscription-plans, service-level-agreement)
• https://community.exalate.com/t/any-plans-to-integrate-with-bmc-remedy/4313 (critical source — co-founder’s statement on no native Remedy support)
• https://trust.exalate.com/
• https://www.g2.com/products/exalate-exalate/reviews, https://marketplace.atlassian.com/apps/1213645/
• https://siliconcanals.com/idalko-and-exalate-to-operate-independently/

Unito

• https://unito.io/connectors/ (critical source — 67-connector catalog with zero BMC products)
• https://unito.io/integrations/, /pricing/, /platform-overview/, /security/, /about-us/, /case-studies/
• https://guide.unito.io/integration-documentation, /how-secure-is-unito, /unito-speed-explained, /how-does-unitos-pricing-work
• https://unito.io/blog/unito-announces-series-b/, /unito-soc-2-type-ii/
• https://www.crunchbase.com/organization/unito
• https://www.g2.com/products/unito/reviews, https://www.capterra.com/p/147319/Unito/, https://www.trustradius.com/products/unito/reviews, https://www.getapp.com/it-management-software/a/unito/

BMC Helix iPaaS (Jitterbit)

• https://www.bmc.com/it-solutions/bmc-helix-ipaas.html
• https://www.jitterbit.com/partners/bmc/, /application/bmc-helix/
• https://marketplace.bmc.com (template catalog)
• https://www.jitterbit.com/connectors/
• https://success.jitterbit.com/ (Harmony architecture, Private Agents, Jitterscript)
• https://trust.jitterbit.com/ (SOC 2, ISO 27001, HIPAA)
• https://docs.bmc.com/xwiki/bin/view/Helix-Common-Services/iPaaS/BMC-Helix-iPaaS/
• https://docs.jitterbit.com/integration-studio/design/connectors/bmc-helix-itsm/connection/
• https://www.gartner.com/reviews/market/enterprise-integration-platform-as-a-service (Peer Insights)
• https://www.g2.com/products/jitterbit-harmony/reviews
• https://www.trustradius.com/products/jitterbit-harmony/reviews
• https://marketplace.fedramp.gov (verify FedRAMP status)

Cross-Vendor

• https://www.bmc.com/partners/bmc-integrations.html (Unito and Exalate absence verified)

End of document. Revisions should be tracked in the Change Log section above.