Skip to content

An open Iceberg lake.
You own it.

Deploy the open-source engine in your cloud. Use our Cloud Control Plane to manage it at scale.

Get started

Launch the binary. No discovery call.

skipprd is a complete, self-serve engine. Install it, point it at Postgres, and land Apache Iceberg tables in your own bucket. The Cloud Control Plane is there when you want fleet management — not as a gate on the software.

Install skipprdDeveloper Docs →

Mid-market VP track: Book a 20-min call · 20 minutes, no sales pitch.

skipprd
$ brew install skipprd/tap/skipprd$ skipprd connect data-source postgres --pipeline orders --name production$ skipprd connect data-sink skippr-lake --pipeline orders --name lake --warehouse 's3://my-lake/' --catalog-table skippr$ skipprd sync --pipeline orders

Skippr is a stream lake ​

A warehouse copy of last night's extract is not enough. Skippr ingests continuously from OLTP systems, SaaS APIs, files and streams, then lets you query the table as it fills. Iceberg snapshot commits are ACID — atomic, so readers never see a half-written table. That is a stream lake: live operational state on open files you own.

Production database to Iceberg on your S3 bucket Production database streams through local CDC into the skipprd Rust binary, which performs a local multi-threaded write of Iceberg and Parquet into your S3 bucket. Production DatabasePostgres, MySQLSQL Server, MongoDBLocal CDCInserts, updates, deletesStays in your VPCskipprd Rust binaryOne processWAL · schema · IcebergLocal multi-threaded writeParquet filesACID Iceberg snapshotsYour S3 bucketIceberg / Parquet you ownDuckDB · Athena · Snowflake
Production Database → Local CDC → skipprd Rust binary → Local multi-threaded write → Your S3 bucket (Iceberg / Parquet).

Why that matters ​

Most stacks still batch into a vendor warehouse, then hope another tool can read the same rows. Skippr lands Apache Iceberg tables on Parquet in your object store. Compute is decoupled: skipprd query, Athena, Snowflake, DuckDB, notebooks — the same tables. No second copy. No lock-in.

  • Open lake architecture — Apache Iceberg on Parquet. Storage in your bucket. Compute wherever you point it.
  • Ingest that finishes — CDC including updates and deletes. Exactly-once where the destination supports it. Each source declares append, merge or replace-by-day, and Skippr refuses to start a pipeline the destination cannot honour.
  • One binary, your machines — a single, resource-efficient Rust binary. Deploy in your cloud or on-prem.
  • Privacy by default — data stays in your deployment. Self-host, or we operate skipprd in your account — your cloud, your buckets, your sovereignty.

Why Skippr

Built to replace the expensive defaults

Privacy by default. Each source declares append, merge, or replace-by-day — and Skippr refuses to start a pipeline the destination cannot honour.

AgainstSkippr
vs. FivetranNo volume-based pricing anxiety. Data stays inside your VPC.
vs. Apache FlinkNo complex JVM cluster management. One ultra-lightweight Rust binary.
vs. DuckDBHandles transactional write-locks, micro-inserts, and live schema drift continuously so DuckDB can query cleanly.

How the stream lake works ​

  1. Stream ingest — CDC, APIs, files and Kafka land through one engine. Each pipeline declares append, merge or replace-by-day.
  2. In-stream query — skipprd query runs SQL against the lake table plus rows that just arrived. --watch follows a sync.
  3. Realtime materialised views — Iceberg snapshots are atomic. Operational state is queryable as it lands, not after a warehouse window.
  4. SkipprLake — open tables in your object store, or the same ingest into any warehouse.
  5. Lineage — source field to lake table, in git and in the Skippr IDE.
  6. Agentic workloads — ReAct suites grounded in those tables, not in a scrape of the public web. Expanded below.

You keep the systems you already run. Skippr is the stream lake they write to.

Agentic workloads ​

Live context for agents, inside your private cloud. ​

AI agents can't reason over yesterday's stale warehouse batches. Skippr feeds live transactional state directly into local Parquet/Iceberg tables, providing a secure, real-time context and memory layer that agents can query locally via DuckDB without data leaking outside your private cloud.

That is the point of a stream lake for AI:

  • Agents see current orders, inventory, jobs and spend — not last night's batch.
  • The tables are ordinary Iceberg/Parquet in your bucket, so the same files power BI, notebooks and agents.
  • Query stays local. DuckDB, skipprd query, or your own process. Row-level data does not leave the VPC to "give the model context."
  • The ontology, metrics and lineage already on the lake become the tools an agent is allowed to use.

Read the Skippr ReAct suite, or start from Developer Docs and land the tables first.

Get started ​

Install skipprd, then land Postgres into Iceberg on a bucket you own. Full flags, Python, and every connector live in Developer Docs.

bash
brew install skipprd/tap/skipprd
skipprd --version
skipprd connect data-source postgres --pipeline orders --name production
skipprd connect data-sink skippr-lake --pipeline orders --name lake \
  --warehouse 's3://my-lake/' --catalog-table skippr
skipprd discover --pipeline orders
skipprd sync --pipeline orders
bash
curl -sL https://raw.githubusercontent.com/skipprd/skipprd/main/install.sh | sh
skipprd --version
bash
pip install skippr
python -c "import skippr; print(skippr.Session)"

Enterprise Jumpstart ​

skipprd works completely out of the box. You do not need a call to land Iceberg tables in your own bucket.

Enterprise Jumpstart is optional: we deploy the binary in your VPC, wire the first sources, and hand you the keys. It is a premium onboarding track for teams that want a founder-engineer in the room for the first pipelines — not how Skippr ships, and not a substitute for the software.

Book a 20-min callWhat Jumpstart covers →

  • PostgreSQL
  • Xero
  • Salesforce
  • Shopify
  • Snowflake
  • Sage
  • Stripe
  • SAP
  • MySQL
  • HubSpot
  • BigQuery
  • QuickBooks
  • MongoDB
  • WooCommerce
  • Databricks
  • Odoo
  • SQL Server
  • Magento
  • Amazon S3
  • Zoho
  • ClickHouse
  • PayPal
  • DuckDB
  • KashFlow
  • DynamoDB
  • Google Analytics
  • Power BI
  • Microsoft
  • Google Ads
  • Excel
  • Meta
  • IRIS
  • Redshift
  • LinkedIn
  • MariaDB
  • SumUp
  • Azure
  • Revolut
  • Oracle
  • Google Cloud
  • PrestaShop
  • Apache Kafka
  • Slack
  • Google Sheets
  • Autodesk
  • Square
  • Tableau
  • Instagram
  • RabbitMQ
  • BigCommerce
  • Bing
  • Looker
  • AdRoll
  • eBay
  • Apple
  • Zendesk

Built for data teams who want the lake, not a project ​

Skippr is for ambitious data teams and startups. You might already have a data team, or want a trusted lake fast. The skipprd Rust binary drops into your cloud or on-prem. Data does not leave your deployment.

  • Working lake in days, not a six-month project.
  • You keep the stack. You own the tables.
  • Open-source engine. Cloud Control Plane when you need scale.
Tom Quigley

“Skippr has saved us hundreds of hours of engineering time and thousands of dollars every month. It's a no brainer.”

Tom QuigleyDevOps EngineerLinkedIn

Works without a callYou own the Iceberg tablesskipprd is open sourceOptional Enterprise Jumpstart

The stream lake stack. One binary. Your cloud.

Deploy skipprd in your VPC. Use the Cloud Control Plane when you run it at scale.

IntegrationSchema discoveryLineageSemantic layerOntologyModellingIceberg lakesAgentic AI

Integration

Every system the business runs, in one place.

Accounts, ERP, CRM, ads, product databases and event streams land in the warehouse or lake you already pay for. Batch loads, change data capture and SaaS APIs run through one engine.

Each source declares how it must be written — append events, merge current state, or rewrite a revised day — and Skippr refuses to start a pipeline the destination cannot honour.

  • Databases, files, streams and SaaS APIs, from Postgres to GA4, Stripe and Xero
  • Change data capture from Postgres, MySQL, SQL Server, MongoDB and DynamoDB — updates and deletes included
  • Exactly-once delivery where the destination supports it
  • Crash-safe: re-run the same command and it resumes where it stopped
Browse connectors →

You own the Iceberg tables. The engine is open source and self-hosted — no vendor lock-in. It works out of the box. Enterprise Jumpstart is optional if you want help landing the first pipelines.