interop.io: connected financial desktops, application workflows and AI controls

interop.io serves banks, brokers, asset managers and financial-technology firms that need existing applications to work together. A brokerage can synchronise an instrument or client across a blotter, research view, CRM and desktop tools.[1]

io.Bridge can connect native .NET, Java or C++ applications with web applications across local and remote environments, including thick-client workflows split between machines. Its name refers to application interoperability. The published product is not a liquidity aggregator, broker credit arrangement or venue-execution service.[6]

The Desktop architecture separates an Electron client from a Gateway, which uses WebSockets by default for application messages. Client APIs cover app lifecycle, windows, shared context and method invocation. Published interfaces include JavaScript/TypeScript, .NET, Java and COM/VBA. App definitions can come from local folders, a REST service or io.Manager.[3]

FDC3 support is more specific than a general claim that applications connect. The documentation describes JavaScript and .NET implementations of FDC3 2.0, conversion of FDC3 app definitions and intent handling. An application declares the action and context it can accept; another raises that intent, and the resolver can let the user choose a handler. App registration and configuration remain part of deployment.[20]

The Fidessa adapter can run locally or on a cloud server, with the same build used for Browser and Desktop but different registration/configuration. Its documented instrument-context synchronisation can also be combined with the Bloomberg adapter. That connection does not supply the underlying Fidessa or Bloomberg commercial entitlement.[18]

Code Mode runs its WebAssembly sandbox inside the customer’s browser or Node.js process. The documentation says there is no separate hosted execution service or per-execution sandbox fee. That concerns this execution component, not the price of an io.Intelligence licence, an LLM service or the customer’s own infrastructure.[9]

The public developer agreement grants internal building, testing and evaluation rights. Public, commercial or production deployment requires a separate agreement, and undocumented APIs are excluded. A production proposal must establish the licence measure, minimum term, renewal/cancellation, taxes and service commitments; the evaluation agreement does not provide that commercial schedule.[25]

A Desktop upgrade can affect the platform, custom system apps, client libraries and stored user settings. Features may require both platform and library changes. The current guide says installer upgrades preserve user data; an upgrade project should still check the intervening changelog and reapply relevant customisation. Purchased adapters have their own packages and distribution work.[12]

Professional Services covers integration strategy, custom connectors, context/symbology mapping, user experience and AI workflow design.[28]

Advanced layouts require io.Manager 4.0 and Desktop 10.5 or later. Every connected platform must use the same layout model; Browser clients currently require legacy layouts. This is a material design constraint for mixed estates, rather than a feature that can safely be switched on for one desktop in isolation.[22]

The layout migration provides a preview of owners, visibility and defaults before it runs. Successfully migrated items remain migrated if a later item fails; completed-clean migration cannot be rerun. Updates made afterwards to one model do not synchronise into the other. Preserve and verify the source records before conversion.[23]

The published trial deletion requirement applies to trial software. Production exit, assistance fees and any vendor-held data retrieval/deletion period need the signed customer contract. Customer-operated configuration and database stores remain an implementation responsibility; a technical migration guide does not itself grant post-termination software rights.[26][5]

Standard support covers documented configurations, suspected product defects and feature guidance. It excludes debugging third-party code. Remote sessions in production, UAT or development are subject to availability and fair use. The 24/7 contractual phone line confirms/escalates severe production incidents; technical telephone assistance must be arranged separately. Response clocks follow the customer SLA.[27]

io.Manager’s administrative interface can inspect sessions, logs, crash reports and feedback, and send commands to active sessions. These are operational powers within the customer’s deployment. Access should be allocated deliberately rather than giving every support user unrestricted administration.[4]

The Desktop Gateway binds to loopback by default. Its documentation warns that opening it to the network makes origin filtering insufficient because another network application can impersonate the Origin header. The shipped filters also accommodate trial/demo applications and should be adapted for production. Gateway authentication and the later user-facing SSO phase are separately configured; the latter supplies identity for remote stores and services.[14]

Browser deployment leaves browser policy and user authentication to the customer. The guide recommends authenticating before platform initialisation. Licence keys are bound to an origin, but that is not user authorisation. Connected client apps gain broad interoperability features, so origin controls matter. A Main app opened by another can fall back to client mode and inherit that parent’s settings unless the documented fallback controls prevent it.[15]

The AI documentation explicitly separates sandbox isolation from authorisation: application tools still validate requests and enforce permissions. Generated code can orchestrate several tool calls, so read-only assistance and a workflow that changes business records are different configurations. The broker controls which callable functions expose consequential actions.[10]

The privacy policy is dated 27 June 2023 and expressly covers the website, including contact, navigation and marketing information. It should not be treated as a full processing or retention agreement for a customer’s connected application estate. Data flows, telemetry collection and any externally hosted AI backend require their own deployment and contractual assessment.[29]

The public developer licence names Interop.io, Inc. as the contracting software company. It reserves ownership of the supplied software while stating that interop.io acquires no ownership of applications the developer creates under that agreement.[25]

interop.io was formed in 2023 from Glue42 and Finsemble. The merger account also brought Tick42 Professional Services into the business as interop.io PS and identified Citi as a strategic investor.[30][1]

ChartIQ is a separate ownership boundary. S&P Global’s official announcement says it acquired ChartIQ from Cosaic, closing on 1 January 2023, and placed it in Market Intelligence while continuing standalone licensing. ChartIQ therefore should not be treated as a product acquired through the later Glue42/Finsemble combination or as another name for interop.io.[31]

Operator

Interop.io, Inc.

Service scope

Application interoperability, coordinated desktops/browser workflows and optional management, telemetry and AI integration.

Customer types

Banks; Brokers; Asset managers; Financial-technology providers

Delivery

On premises; API; Hybrid

Pricing publication

Quote only

Platforms

io.Connect Browser; io.Connect Desktop; io.Manager; io.Bridge; io.Insights; io.Intelligence

Pricing scope

Production licence pricing is enquiry-based; a 30-day nonproduction trial and a scoped Finsemble migration offer are published.

Implementation

Customer-configured Browser/Desktop deployments, optional io.Manager and distributed io.Bridge; adapters and versions have individual prerequisites.

Support

Product support within documented scope; severe-production notification line 24/7, technical calls by prior arrangement.

Permissions and regulatory scope

Software/workflow integration; connected trading applications and third-party data retain their own permissions and entitlements.

Provider metadata checked 20 Oct 2026Source 1Source 25Source 32Source 24Source 2Source 33Source 6Source 26Source 28Source 27Source 17Source 30Source 21

The 19 October 2026 Desktop 10.5.1 release adds saving and restoring windows of native applications that do not use io.Connect APIs. It is Windows-only, requires an EXE-type app with process tracking, and must be enabled. These tracked windows cannot participate in window groups or Workspaces. Stopping the app closes its window rather than forcibly terminating the process; a save prompt can leave the process running after tracking ends.[24]

The two Excel adapter versions can coexist on one machine. The vendor recommends version 2 but still labels it experimental, with features subject to change; version 1 is described as legacy and due for deprecation. That makes an adapter-specific acceptance test and migration plan more useful than assuming every named integration has the same maturity.[19]

io.Insights’ current OpenTelemetry implementation publishes signals; it does not itself provide the storage or dashboard backend. Applications can contribute their own telemetry, and traces can be correlated with metrics. The customer therefore controls the collection infrastructure, retention and visualisation design. Legacy io.Insights documentation describes a different implementation and should not be mixed into the current setup.[7]

The currently documented ready-made assistant is io.Assist NG for Angular; AI Web supports custom web interfaces, and AI Mastra Bridge connects a Mastra backend to the frontend agent protocol. References to additional framework variants are expansion possibilities. These modules do not remove the need to supply or integrate the underlying agent backend and its model service.[8]