PipelineWise alternative — PipelineWise vs Skippr

PipelineWise is Wise's Apache-2.0 Singer runner. YAML in Git. pipelinewise import, then a scheduled run. It still ships log-based CDC, key incremental, full table, and FastSync (FullSync and PartialSync) on the routes they kept. Schema changes can alter the target. Load-time transforms mask or drop columns before they land. Data-diff compares source and target in a time window. Wise shrank the public connector set so they can keep serving their own replication: sources are MariaDB and PostgreSQL; targets are PostgreSQL and Snowflake. Other packaged connectors, including Snowflake as a source, are experimental. Release 0.64.1 is the last cut before that shrink. They are still releasing in 2026 (0.98.1 on 30 Oct 2026), including Snowflake Iceberg publication and copy_native_to_iceberg.

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 Singer pipe. ELT into a warehouse is one path, not the product.

Feature	Skippr	PipelineWise
Deploy	Single Rust binary, your VPC or on-prem	Python 3.12 or Docker. YAML plus a scheduler you run
Schema	In-stream evolution, sibling columns	Detects source change and applies compatible target alters
Storage	Open Iceberg on Parquet you own	Postgres or Snowflake. Iceberg publication on Snowflake FastSync
CDC	Log-based; fails closed if the dest cannot honour	Log-based, incremental, or full table on the kept routes
Query	`skipprd query` on Iceberg ∪ WAL; history in any Iceberg engine	Destination after the run. Data-diff is a check, not live SQL
Pricing	Free self-hosted engine	Apache-2.0, pay your infra. See their docs.

What PipelineWise is good at

This is a runner a payments company still uses to move terabytes. FastSync is the bulk path when Singer row-by-row is the wrong tool. Load-time masking is in the YAML, not a later dbt model. Data-diff and Iceberg FastSync on Snowflake are named operations, not blogware. If your job is MariaDB or Postgres into Postgres or Snowflake, and you want Singer plus a bulk handover, that is a real product.

Where the job is wider

The public catalog is two sources and two targets. The old Meltano-Hub-shaped menu left with the shrink. pipelinewise init still writes some legacy templates that are not packaged. Do not treat 0.64.1 as the install you want.

PipelineWise is Singer ELT on a schedule. There is no Iceberg ∪ WAL. There is no skipprd query on in-flight rows. Query waits for Snowflake or Postgres. Iceberg on Snowflake is a publication of the destination, not a Streamhouse. Skippr will not give you PipelineWise data-diff, FastSync PartialSync, or their Slack / VictorOps alert handlers. Skippr also does not speak Singer, so you cannot drop in a leftover tap. If the job is "Wise-shaped MariaDB to Snowflake," PipelineWise is the narrower tool. If the job is live SQL on Iceberg you run, PipelineWise 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 PipelineWise if you want Wise's Singer runner for MariaDB or Postgres into Postgres or Snowflake, with FastSync and data-diff.

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

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

PipelineWise alternative — PipelineWise vs Skippr ​

What PipelineWise is good at ​

Where the job is wider ​

Getting started ​

Which to choose ​

PipelineWise alternative — PipelineWise vs Skippr

What PipelineWise is good at

Where the job is wider

Getting started

Which to choose