Celigo alternative — Celigo vs Skippr

Celigo integrator.io is iPaaS. You draw a flow: export from a source, lookups and branches, import into a destination. Editions are Standard, Professional, and Enterprise. Official packaging is endpoints and flows, not tasks or bytes. Standard and Professional include 20 flows and 3 endpoints. Enterprise is unlimited endpoints and still lists 20 flows on the edition table. Concurrency is 25 on Standard and 50 on Enterprise (add-on on Professional). CDC is Professional and Enterprise, not Standard. On-premise agent is an add-on on every edition; agent groups are Enterprise only. A 30-day trial is unlimited; after that a free account keeps one active flow. Price is quote. Celigo's own line is that they do not meter tasks, data volume, or vCores. There is no Iceberg destination. 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 flow seat. ELT into a warehouse is one path, not the product.

Feature	Skippr	Celigo
Deploy	Single Rust binary, your VPC or on-prem	integrator.io SaaS. On-prem agent is an add-on
Schema	In-stream evolution, sibling columns	Flow mapping and lookups
Storage	Open Iceberg on Parquet you own	Target app. No Iceberg dest
CDC	Log-based; fails closed if the dest cannot honour	CDC on Professional and Enterprise. Not a log tail
Query	`skipprd query` on Iceberg ∪ WAL; history in any Iceberg engine	Downstream after the flow
Pricing	Free self-hosted engine	Quote. Edition plus endpoints and flows.

What Celigo is good at

A flow that already maps Shopify, NetSuite, and a 3PL without a second tool. That is the product. Integration Apps (prebuilt channel-to-ERP) are why ecommerce teams buy it. If the job is "NetSuite plus the storefront," that is a real product.

Where the job is wider

Celigo is an iPaaS canvas. 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.

Endpoint math is the ops. The next connected system can move the quote. Extra flows sit on top of the edition table. CDC is an edition gate, not a Postgres WAL reader.

Skippr will not run a Celigo flow. Skippr also will not match the NetSuite Integration App catalog. If the job is "ecommerce iPaaS we already staff," Celigo is the narrower tool. If the job is live SQL on Iceberg you run, Celigo 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.

YAMLCLIPython

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

bash

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")

bash

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 Celigo if you want integrator.io flows into NetSuite and the storefront, 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 a Celigo flow.

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

Celigo alternative — Celigo vs Skippr ​

What Celigo is good at ​

Where the job is wider ​

Getting started ​

Which to choose ​

Celigo alternative — Celigo vs Skippr

What Celigo is good at

Where the job is wider

Getting started

Which to choose