Jitterbit alternative — Jitterbit vs Skippr

Jitterbit Harmony is iPaaS. You draw an operation in Cloud Studio (or the older Design Studio desktop). A Cloud Agent or a Private Agent runs it. Tiers are Standard (2 to 3 connections), Professional (5), and Enterprise (8 or more). Private Agents are 2, 2, and 4. Environments are 2 on Standard and 99 above. Agent grouping is optional on Professional and included on Enterprise. Annual contract. Quote, plus an Enterprise Licence Agreement if you want one invoice for the estate. API Manager, EDI, extra Private Agents, and premium message queues are add-ons. Connector licence is Standard or Enterprise; Enterprise connectors are a subscription add-on. Salesforce Change Data Capture sits on the Salesforce Events connector (Enterprise add-on). There is no Iceberg connector in the Studio catalog. 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 connection seat. ELT into a warehouse is one path, not the product.

Feature	Skippr	Jitterbit Harmony
Deploy	Single Rust binary, your VPC or on-prem	Cloud Studio plus Cloud or Private Agents
Schema	In-stream evolution, sibling columns	Studio mapping
Storage	Open Iceberg on Parquet you own	Target you wired. No Iceberg connector
CDC	Log-based; fails closed if the dest cannot honour	Salesforce Events CDC as an Enterprise add-on. Not a log tail
Query	skipprd query on Iceberg ∪ WAL; history in any Iceberg engine	Downstream after the operation
Pricing	Free self-hosted engine	Quote. Connections plus agents. API Manager and EDI extra.

Talk through skipprd now

Paul Bot knows the docs. Google Meet as soon as you join, any time of day.

Chat now →

Any time · 20 minutes · Google Meet now

What Jitterbit Harmony is good at

An operation that already maps NetSuite, a file drop, and an API on one Private Agent. That is the product. EDI plus API Manager on the same Harmony login is why some mid-market estates stay. If the job is "SaaS process we already staff," that is a real product.

Where the job is wider

Jitterbit is an integration studio. It is not a Streamhouse. There is no Iceberg ∪ WAL. There is no skipprd query on in-flight rows. The operation ends; then you query the next system.

Connection math is the ops. The next endpoint can move you up a tier. API Manager and EDI are separate SKUs. Salesforce CDC is an add-on, not a Postgres WAL reader.

Skippr will not run a Harmony operation. Skippr also will not match the EDI or API Manager surface. If the job is "iPaaS we already staff," Jitterbit is the narrower tool. If the job is live SQL on Iceberg you run, Jitterbit 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.

YAML

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-1

CLI

skipprd --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_schema

Python

from 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 Jitterbit if you want Harmony operations into SaaS and warehouses, and the next system after the operation is enough.

Choose Skippr if you want one binary, live SQL, and Iceberg files that stay yours. Skippr will not run a Harmony operation.

Install from Install. Connector and query reference live in Developer Docs. For optional onboarding in your VPC, Enterprise Jumpstart or Contact.