RudderStack alternative — RudderStack vs Skippr

RudderStack is customer data infrastructure: SDK and cloud event collection, warehouse destinations, and reverse ETL back out to the same SaaS tools. Reverse ETL treats each record sent to each destination as an event (100 records to 3 dests = 300 events). Sources are warehouse tables, SQL models, or audiences. Sync modes are Upsert and (on some dests) Mirror. Free includes reverse ETL (10 connections, 250,000 events/month). Growth starts at 265 USD/month for 1 million events (225 USD/month billed annually); 3M is 735; 5M is 995; 25M is 2,750 USD/month. Enterprise is a quote (5-minute warehouse sync, HIPAA, SSO). Iceberg: Snowflake Streaming can write Snowflake-managed Iceberg tables (included on that dest; Snowflake compute and your external volume are extra). Those Iceberg tables can be a reverse-ETL source if the role can read and write. RudderStack is not Iceberg ∪ WAL you query in one binary.

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. Skippr will not be your event SDK. ELT into a warehouse is one path, not the product.

Feature	Skippr	RudderStack
Deploy	Single Rust binary, your VPC or on-prem	RudderStack Cloud (VPC on Enterprise)
Schema	In-stream evolution, sibling columns	Tracking plans. Warehouse models for reverse ETL
Storage	Open Iceberg on Parquet you own	Warehouse dest, or Snowflake-managed Iceberg via Streaming
CDC	Log-based; fails closed if the dest cannot honour	Event stream, or warehouse reverse ETL. Not Postgres WAL
Query	`skipprd query` on Iceberg ∪ WAL; history in any Iceberg engine	The warehouse. RudderStack is collect / activate
Pricing	Free self-hosted engine	Free 250k events. Growth from 265 USD/month (1M).

What RudderStack is good at

One pipeline for client events into the warehouse and modeled rows back into the tools, with transformations in JavaScript or Python. That is the product. Snowflake Streaming Iceberg is why some Snowflake estates skip a second loader for the event tables. If the job is "this identify into this warehouse and this audience into Iterable," that is a real product.

Where the job is wider

RudderStack is a CDP pipeline. It is not a Streamhouse. There is no Iceberg ∪ WAL. There is no skipprd query on in-flight lake rows. Iceberg write is Snowflake Streaming, not a portable catalog you own independently of Snowflake. Reverse ETL events multiply by destination. Postgres CDC still starts before the SDK. Skippr will not replace rudderanalytics.track.

Event volume, warehouse sync minutes, and reverse-ETL connections (10 / 25 / unlimited) are the ops. Skippr will not run RudderStack. Segment, Census, and Hightouch are separate pages.

If the job is "event CDP we already staff," RudderStack is the narrower tool. If the job is live SQL on Iceberg you run, the SDK 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 RudderStack if you want event collection plus reverse ETL, and event-volume pricing (or Snowflake Iceberg via Streaming) is enough.

Choose Skippr if you want one binary, live SQL on Iceberg ∪ WAL, and files that stay yours. Skippr will not run the RudderStack SDK.

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

RudderStack alternative — RudderStack vs Skippr ​

What RudderStack is good at ​

Where the job is wider ​

Getting started ​

Which to choose ​

RudderStack alternative — RudderStack vs Skippr

What RudderStack is good at

Where the job is wider

Getting started

Which to choose