Skip to content

Peliqan alternative — Peliqan vs Skippr ​

Peliqan is a SaaS data platform for consultants and small data teams. Connectors land a built-in Postgres warehouse (they call it a cache), or yours: Snowflake, BigQuery, Fabric, Redshift. You query in SQL, poke tables in Excel, write Python apps on Pro. Reverse ETL, writeback, and an MCP server sit on the same login. Connect is 75 euros a month per standard source on a 12-month contract (85 USD), 500k rows fair use, no Python apps, no premium sources. Pro is 500 euros a month (570 USD) for 10 users and 10 sources, 5 million rows, reverse ETL, lineage, and Trino. Custom adds on-prem Kubernetes or a private cloud. Each database, warehouse, or SaaS account is one connection. Two HubSpot accounts count as two.

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

FeatureSkipprPeliqan
DeploySingle Rust binary, your VPC or on-premSaaS (AWS Frankfurt). On-prem agent or VPN for sources. Full plane on Custom
SchemaIn-stream evolution, sibling columnsConnector-owned. New connectors in a few business days
StorageOpen Iceberg on Parquet you ownBuilt-in Postgres cache, or BYO warehouse. SaaS sources can stay as a copy
CDCLog-based; fails closed if the dest cannot honourCDC listed for databases. SaaS is scheduled or a limited live fetch
Queryskipprd query on Iceberg ∪ WAL; history in any Iceberg engineSQL editor, Excel add-in, Trino on Pro. Warehouse after the load
PricingFree self-hosted engineFrom 75 euros per source per month. See their pricing.

What Peliqan is good at ​

One login instead of an ingest tool, a warehouse, and a spreadsheet plugin. 300+ connectors aimed at ERP, CRM, and accounting. The Excel add-in is the honest pitch for consultants who will not open a SQL client. Pro adds writeback and published APIs. They do not bill overages; they ask you to upgrade if you stay above the fair-use row cap. For a 12-month contract and a handful of SaaS sources, that is a real product.

Where the job is wider ​

Sources and rows are the cap. Connect has no premium sources and no Python apps. Reverse ETL starts on Pro. G2 reviewers who like the connectors still say you need SQL or Python, and that it is not self-service until someone who knows the platform sets it up. A 12-month contract is the published default.

Peliqan stores a copy of SaaS data in their warehouse unless you pick the limited live-fetch mode. Database sources can federate. There is no Iceberg ∪ WAL. Query of in-flight CDC rows is not the product. On-prem of the whole plane is Custom, not Connect.

Skippr will not give you Peliqan's Excel add-in, MCP seats, or a white-label data cloud for your clients. If the job is "HubSpot plus Excel on a per-source bill," Peliqan is the narrower tool. If the job is live SQL on Iceberg you run, Peliqan 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.

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 Peliqan if you want connectors, a built-in warehouse, and Excel on one 12-month bill, and you fit the source and row cap.

Choose Skippr if you want one binary, no per-source subscription, live SQL, and Iceberg files that stay yours.

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