Skip to content

Modernise the
TIBCO landscape
you already run —
and make it AI-ready

BusinessWorks  5 and 6 (BW5/BW6), EMS, the TIBCO Platform and Flogo. We start with a read-only audit of what you have, get it onto supported versions and the platform where it pays, keep the rest in one view, and expose the services you already own to your AI applications within your governance framework.

Request a read-only landscape audit
The audit needs read-only permissions,
and nothing in your environment is changed.
Talk to a TIBCO expert
Home
TIBCO
15+ years of TIBCO partnership
TIBCO Gold Partner
Partner of the Year, three times
300+ TIBCO certifications
24X7 managed services

Four steps, in the order that suits your landscape

The same path we walk with every TIBCO customer — each step stands on its own.

Step 1

Know it

A read-only audit through the tooling you already run to create an inventory, a risk register, a version map.

Step 2

Get It supported

First, upgrade your existing applications and engines to supported releases (BW5 to 5.16.1, BW6 to 6.12, and EMS to 10.4). Next, transition to containers managed by the TIBCO Platform Control Plane, backed by built-in rollback support.

Step 3

Unified visibility across your estate

Through Control Tower, host-level metrics seamlessly integrate into the shared Control Plane, delivering unified core inventories, alerts, and dashboards across both host and container environments.

Step 4

Make It AI-ready

By leveraging Flogo, your existing services can be securely exposed as governed Model Context Protocol (MCP) tools. You maintain strict control by initially limiting exposure to selected services and fields with read-only permissions, bridging your core services with your AI applications, API gateway, and agent platforms.

Where to start

Three entry points. Each stands on its own; each makes the next one smaller.

Landscape audit

Start here if nobody owns the inventory.

WHAT IT IS

Read-only collection (broad permissions only; nothing changed): exact BW5, BusinessWorks, EMS, Hawk and Kubernetes inventories, plus your architecture and operations map.

YOU LEAVE WITH

Inventory and risk workbook, a version map against the LTS line, candidates and sizing.

Request the audit

LTS and Platform wave

Start here if the audit already exists.

WHAT IT IS

Upgrade factory to the LTS line; first wave under the Control Plane or Control Tower; then run non-critical workloads through it.

YOU LEAVE WITH

Upgraded and containerised applications, observability, run-books, pipelines, your team trained.

Plan the wave

AI-ready exposure

Start here if an AI team is already waiting for integration data or actions.

WHAT IT IS

One business capability exposed as governed MCP tools on Flogo, with the gateway or agent platform.

YOU LEAVE WITH

An exposure policy (service, fields, scopes), MCP tools with traces, a trained team.

Scope one capability

What we do on TIBCO

KNOW WHAT YOU RUN

iSteer Audit Suite

Read-only collection through Pivotal, lightweight, for EKS/enterprise estate — the hosts, and the TIBCO runtime estate — giving you an inventory, a risk register plus status, version map and dependencies.

One inventory: each application, memory process, sub-process ports that are run, containers without hints of process; a version map with the 30 November 2026 date applied to every BW5 instance; candidates with sizing.

GET IT SUPPORTED

Implementation: LTS upgrades and migrations

BusinessWorks 5.x to 5.16.1 (June 17, 2026), BusinessWorks 6.5.1 for the TCP Control Plane, BusinessWorks 6.5? for the Control Plane? EMS to 10.4, Hawk 7.5 — each supported to 2030. Environment study, regression packs from the existing app process toolkits, done by wave, with your operations team from the first week.

GET IT SUPPORTED

TIBCO Platform adoption

BW5, BW6 and EMS in containers under the Control Plane — TIBCO-managed SaaS or deployed and managed by you — on any cloud or premise. In your cloud at the edge, TIBCO’s own workload order for BW5: on day one, one dashboard for logs, metrics and traces, rolling upgrades, staging and maintenance as policy.

ONE VIEW

Control Tower and one operating model

Nothing has to move on day one. Born, schedulers, Renderers-board fees, BW5 AppServices, EMS, adapters and Hawk are observed and managed through the Control Tower.

Your work rules keep running; the platform CLI remains available and the deployments are PREVIEW enabled on your own tenancy.

AI-READY

AI-ready integration with TIBCO Flogo

Flogo MCP Server can expose any BW5, BW6 or REST/SOAP service as MCP tools — tightly scoped routes and tools, policy points for app, security and run with your team.

Your gateway keeps policy and logs; your event platform keeps orchestration.

RUN

TIBCO managed services

BW5, BW6 and EMS in containers under the Control Plane — TIBCO-managed SaaS or deployed and managed by you — on any cloud or premise. In your cloud at the edge, TIBCO’s own workload order for BW5: on day one, one dashboard for logs, metrics and traces, rolling upgrades, staging and maintenance as policy.

Data and analytics on TIBCO

Three entry points. Each stands on its own; each makes the next one smaller.

TIBCO EBX

Master data management, governed and clean the critical data your integrations carry.

TIBCO Data Virtualization

Access and analyse data across sources without duplicating it.

TIBCO Spotfire

Visual analytics and data science on your integration data — implementation, upgrades and managed services.

Why iSteer for TIBCO

A focused TIBCO practice

One of the few leading partners with BusinessWorks, EMS, BusinessEvents, Flogo and the Platform under one roof — Gold Partner, 15+ years in TIBCO, 300+ certifications.

Fixed-scope first steps

The audit, the wave, one capability — each starts after a short scoping call, each standing on its own.

With TIBCO, in your environment

Alongside the TIBCO account and product teams; product questions go to them, delivery support comes to us. Your identity provider, your operations team, your rules — we work with them.

Everything handed over

Workbooks, run-books, pipelines, policies, training. Managed services only if you would rather we keep running it.

Questions we hear first

Do we have to move to Kubernetes to stay supported?

No. BW 5.16.1, BW 6.12 and EMS 10.4 are LTS releases supported to 2030 on hosts. Control Tower brings host-based installations into the TIBCO Platform view without containers; containers come later, workload by workload, when the audit says it pays.

No — TIBCO-operated SaaS or deployed and managed by you; data planes run on-premises, in your cloud or at the edge.

Runtime, deployment configuration, messaging and host facts through your existing tooling — Hawk, AppManage, the EMS admin tools, the hosts, the clusters — read-only. It does not change anything in your environment.

Your identity provider issues the token; each MCP tool carries a scope and unscoped tools are not listed; only the selected fields cross; read-only first; an OpenTelemetry trace on every call; it sits behind your AI gateway.

Yours. The Flogo layer is provider-agnostic, including private models

No. BW 5.16.1 runs in containers under the Platform; a BW6 migration is a separate decision, made per domain.