TIBCO alternative — TIBCO Integration vs Skippr
TIBCO Integration is process middleware. BusinessWorks is the visual model: activities, mappings, and 300-plus connectors, deployed as ActiveMatrix processes or BusinessWorks Container Edition apps. Flogo is the lighter flow designer for APIs and events. BusinessConnect is the B2B mailbox. Managed File Transfer is the file plane. Cloud Software Group still sells those on-prem and container SKUs. TIBCO Cloud Integration (TCI), including the Integrate / BusinessWorks cloud SKUs, shut down at 23:59 Pacific on 31 October 2025. Remaining cloud paths named in that notice are TIBCO Platform and Scribe Online. Packs still meter on-prem: one Pack is one processor of ActiveMatrix BusinessWorks, or one processor / 25 application instances of Container Edition, or 100 Flogo instances (4,000 concurrent on Lambda or IoT in the Integration 2.6 pack definition). AWS Marketplace Flexible Consumption Pricing bills 5 consumption units per Container Edition container-hour and 2 per plug-in-hour. BusinessWorks 5.15 support ends 30 November 2026; 5.16.1 is sold through 2030. Data Virtualization is a different product, now Spotfire Data Virtualization on a Spotfire Platform subscription (from 1 December 2025). This is not a Streamhouse. There is no Iceberg ∪ WAL.
Skippr is an open Streamhouse you run as one Rust binary. Write skippr.yml (or the same thing in Python), discover, sync. You query live state over Iceberg ∪ WAL, and the history is ordinary Iceberg in your bucket. No Pack. ELT into a warehouse is one path, not the product.
| Feature | Skippr | TIBCO Integration |
|---|---|---|
| Deploy | Single Rust binary, your VPC or on-prem | BusinessWorks / Flogo on-prem or containers. TCI is gone |
| Schema | In-stream evolution, sibling columns | Process mapping. Scribe for SaaS objects |
| Storage | Open Iceberg on Parquet you own | Target system. No Iceberg destination in BW |
| CDC | Log-based; fails closed if the dest cannot honour | Messaging and process events. Not log CDC |
| Query | skipprd query on Iceberg ∪ WAL; history in any Iceberg engine | Downstream after the process. DV is a Spotfire SKU |
| Pricing | Free self-hosted engine | Quote. Packs (processors / instances). AWS FCP is unit-hours. |
What TIBCO Integration is good at
A process that already talks EMS, a mainframe adapter, and a SOAP partner. That is the product. BusinessConnect plus MFT is why some B2B estates still run it. Flogo is the smaller binary when the job is an API at the edge. If the job is "keep the BW5 process through 2030," that is a real (time-boxed) product.
Where the job is wider
BusinessWorks is an integration server. It is not a Streamhouse. There is no Iceberg ∪ WAL. There is no skipprd query on in-flight rows. The process ends; then you query the next system.
TCI is the ops. The SaaS SKU is gone. Data on that service was deleted after 31 October 2025 unless you asked Support 30 days prior. Platform and Scribe are the named successors, not a BW import. Pack math is processors or container instances, not rows. A DV query is a Spotfire subscription, not a BW activity.
Skippr will not run a BusinessWorks process. Skippr also will not replace EMS or BusinessConnect. If the job is "process integration we already staff," TIBCO is the narrower tool. If the job is live SQL on Iceberg you run, TIBCO was never that.
Getting started
Install skipprd from the install guide, or pip install skippr. The three tabs write the same skippr.yml. Then discover, sync, and query.
skippr:
workspace: analytics
skipprd_el_storage_mode: local
pipelines:
orders:
data_source: data_sources.app_db
data_sink: data_sinks.lake
data_sources:
app_db:
Postgres:
host: db.internal
user: skippr_reader
password: ${APP_DB_PASSWORD}
database: app
tables: [orders, customers]
cdc_mode: snapshot_then_cdc
data_sinks:
lake:
AthenaIceberg:
warehouse: s3://my-iceberg-warehouse/
glue_database_name: analytics
athena_workgroup_name: primary
athena_results_s3_bucket: my-athena-results
region: us-east-1
schema_sink: schema_sinks.lake_schema
schema_sinks:
lake_schema:
AthenaIceberg:
warehouse: s3://my-iceberg-warehouse/
glue_database_name: analytics
athena_workgroup_name: primary
athena_results_s3_bucket: my-athena-results
region: us-east-1skipprd --workspace analytics --storage-mode local connect data-source postgres \
--pipeline orders \
--name app_db \
--host db.internal \
--user skippr_reader \
--password '${APP_DB_PASSWORD}' \
--database app \
--tables orders \
--tables customers \
--cdc-mode snapshot_then_cdc
skipprd connect data-sink athenaiceberg \
--pipeline orders \
--name lake \
--warehouse s3://my-iceberg-warehouse/ \
--glue-database-name analytics \
--athena-workgroup-name primary \
--athena-results-s3-bucket my-athena-results \
--region us-east-1
skipprd connect schema-sink athenaiceberg \
--pipeline orders \
--name lake_schemafrom skippr import (
Config,
DataSinkAthenaIceberg,
DataSourcePostgres,
DataSourcePostgresSourceCdcMode,
EnvRef,
LocalStorage,
Pipeline,
)
cfg = Config().workspace("analytics").storage(LocalStorage())
app_db = cfg.data_source(
"app_db",
DataSourcePostgres(
host="db.internal",
user="skippr_reader",
password=EnvRef("APP_DB_PASSWORD"),
database="app",
tables=["orders", "customers"],
cdc_mode=DataSourcePostgresSourceCdcMode.SNAPSHOTTHENCDC,
),
)
lake = cfg.data_sink(
"lake",
DataSinkAthenaIceberg(
warehouse="s3://my-iceberg-warehouse/",
glue_database_name="analytics",
athena_workgroup_name="primary",
athena_results_s3_bucket="my-athena-results",
region="us-east-1",
),
schema_sink="lake_schema",
)
cfg.pipeline("orders", Pipeline(data_source=app_db, data_sink=lake))
cfg.save("skippr.yml")export APP_DB_PASSWORD='your-postgres-password'
skipprd discover --pipeline orders
skipprd sync --pipeline orders --once
skipprd query "SELECT count(*) FROM analytics.orders"Which to choose
Choose TIBCO Integration if you already run BusinessWorks or Flogo processes, and the next system after the process is enough.
Choose Skippr if you want one binary, live SQL, and Iceberg files that stay yours. Skippr will not run a BW process.
Install from Install. Connector and query reference live in Developer Docs. For optional onboarding in your VPC, Enterprise Jumpstart or Contact.
