webMethods alternative — IBM webMethods vs Skippr
IBM webMethods is process integration that Software AG used to sell. The on-prem engine is still Integration Server (docs still show 10.15): packages, adapters, Broker or Universal Messaging, Designer. The cloud product is IBM Integration SaaS, the rename of webMethods Hybrid Integration. Standard starts at 2,565 USD a month. You buy resource units (RU) and burn them. Enabling webMethods Integration in a production environment is 60 RU a month, plus 4 RU per 100,000 transactions for the first million a year, then 1 RU per 100,000. Credits also cover API calls, B2B, managed file transfer, and events. Connectors and on-prem runtimes are listed as unlimited on that page. Self-managed is IBM Integration Software Capacity 16.2.1 (VPC cores): MQ, App Connect, and API Connect in the same licence as webMethods Integration, B2B, and MFT. The old webMethods Integration Cloud died at the end of 2023. *.softwareag.cloud metering URLs retire on 14 August 2026 in favour of *.platform.ipaas.ibm.com. This is iPaaS. It 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 RU. ELT into a warehouse is one path, not the product.
| Feature | Skippr | IBM webMethods |
|---|---|---|
| Deploy | Single Rust binary, your VPC or on-prem | Integration Server on-prem, or IBM Integration SaaS |
| Schema | In-stream evolution, sibling columns | Flow mapping. Adapter metadata |
| Storage | Open Iceberg on Parquet you own | Target application. No Iceberg destination |
| CDC | Log-based; fails closed if the dest cannot honour | Events and adapter polls. Not log CDC |
| Query | skipprd query on Iceberg ∪ WAL; history in any Iceberg engine | Downstream after the flow. No lake SQL in IS |
| Pricing | Free self-hosted engine | SaaS from 2,565 USD/month in RUs. Capacity is VPC cores. |
What IBM webMethods is good at
A service that already talks an SAP adapter, a B2B envelope, and an IS package from 2012. That is the product. Hybrid control plane plus unlimited on-prem runtimes is why some estates stayed through the IBM buy. If the job is "keep the Integration Server package," that is a real product.
Where the job is wider
webMethods is an integration server. It is not a Streamhouse. There is no Iceberg ∪ WAL. There is no skipprd query on in-flight rows. The flow ends; then you query the next system.
RU math is the ops. 60 RU a month is the base for one production Integration environment before the first transaction. A million transactions a year is 40 RU on the first-tier rate, then the cheaper band. Capacity VPC is a different meter for the same brand. Metering that still points at softwareag.cloud breaks after 14 August 2026.
Skippr will not run an IS package. Skippr also will not replace MQ or B2B. If the job is "process integration we already staff," webMethods is the narrower tool. If the job is live SQL on Iceberg you run, webMethods 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 IBM webMethods if you need Integration Server or Integration SaaS process flows, and the next system after the flow is enough.
Choose Skippr if you want one binary, live SQL, and Iceberg files that stay yours. Skippr will not run an IS package.
Install from Install. Connector and query reference live in Developer Docs. For optional onboarding in your VPC, Enterprise Jumpstart or Contact.