Snowpipe alternative — Snowpipe vs Skippr

Snowpipe is Snowflake's serverless loader. A pipe is a schema object with a COPY INTO. Files land in a stage. Cloud notifications or the REST API tell the pipe. Rows are typically queryable within a minute. Snowpipe Streaming is the row path: SDK, REST, or the Kafka connector, ingest-to-query as low as five seconds, up to 20 GB/s per table on the high-performance architecture. Both bill 0.0037 Platform Credits a GB. Text files (CSV, JSON, XML) bill uncompressed size. Binary files (Parquet, Avro, ORC) bill observed size. Streaming bills uncompressed input values, not JSON keys. Streaming Classic (Java SDK 4.x and older) bills 0.01 credits a client-instance-hour plus serverless compute. Dest is a standard table, Snowflake-managed Iceberg v2 or v3, or (Snowpipe only) an externally managed Iceberg table with FULL_INGEST. Streaming Named Channels use offset tokens for exactly-once order. Elastic Channels skip that bookkeeping. Snowflake's own docs send database and SaaS CDC to Openflow, not to a pipe. 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 credit per GB loaded. ELT into a warehouse is one path, not the product.

Feature	Skippr	Snowpipe
Deploy	Single Rust binary, your VPC or on-prem	Pipe or Streaming channel in a Snowflake account
Schema	In-stream evolution, sibling columns	COPY column mapping. Streaming can add columns
Storage	Open Iceberg on Parquet you own	Snowflake tables, or Snowflake-managed Iceberg. External Iceberg is FULL_INGEST
CDC	Log-based; fails closed if the dest cannot honour	File or row ingest. Database CDC is Openflow
Query	`skipprd query` on Iceberg ∪ WAL; history in any Iceberg engine	Snowflake after the pipe commits
Pricing	Free self-hosted engine	0.0037 credits/GB. Classic Streaming is 0.01 credits/client-hour.

What Snowpipe is good at

Files that already land in S3, GCS, or Azure Blob and need to become Snowflake rows without a warehouse you size. That is the product. Streaming is the same job for producers that emit rows, including Kafka. Iceberg dest is real when the catalog is Snowflake, or when Snowpipe can FULL_INGEST into an external REST catalog. If the job is "these files into this account," that is a real product.

Where the job is wider

Snowpipe is a loader. It is not a Streamhouse. There is no Iceberg ∪ WAL. There is no skipprd query on in-flight rows. Iceberg here is a Snowflake table type, except the external-catalog FULL_INGEST path. A pipe does not join, aggregate, or filter. Transforms sit in Dynamic Tables or streams and tasks after the load.

Credit math is the ops. 0.0037 a GB looks small until JSON keys, decompression, and a second warehouse line for anything after COPY. Classic Streaming still bills idle clients. A pipe is not a log tail. Skippr will not replace a Snowpipe that already auto-ingests partner files into Snowflake.

If the job is "Snowflake file or row ingest we already staff," Snowpipe is the narrower tool. If the job is live SQL on Iceberg you run, Snowpipe was never that. Managed NiFi CDC is Openflow.

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 Snowpipe if you want serverless file or row ingest into Snowflake, and the warehouse after the pipe is enough.

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

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

Snowpipe alternative — Snowpipe vs Skippr ​

What Snowpipe is good at ​

Where the job is wider ​

Getting started ​

Which to choose ​

Snowpipe alternative — Snowpipe vs Skippr

What Snowpipe is good at

Where the job is wider

Getting started

Which to choose