Qlik Replicate alternative — Qlik Replicate vs Skippr

Qlik Replicate is client-managed log CDC. It used to be Attunity. You install a Windows or Linux server, pick a source endpoint, pick a target, full-load, then stream changes. Oracle, SQL Server, Db2, SAP, and a long mainframe-adjacent list are the reason it still wins RFPs. May 2026 added a Cloudera Iceberg target. That path does not support transactional apply, unlimited LOB size, or schema-name settings. The Qlik Open Lakehouse path is not native Iceberg inside Replicate: you land CSV on S3, then a Talend Cloud onboard task builds Iceberg. Dollar prices are quote, usually next to Qlik Data Integration. There is no public per-row card.

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

Feature	Skippr	Qlik Replicate
Deploy	Single Rust binary, your VPC or on-prem	Replicate server you operate. Open Lakehouse needs Talend Cloud on top
Schema	In-stream evolution, sibling columns	Source-driven apply. Cloudera Iceberg ignores schema-name settings
Storage	Open Iceberg on Parquet you own	Warehouse, Kafka, S3, or Cloudera Iceberg. Open Lakehouse is a second hop
CDC	Log-based; fails closed if the dest cannot honour	Log CDC after full load. LOB, null unique keys, and identity columns have named limits
Query	skipprd query on Iceberg ∪ WAL; history in any Iceberg engine	Destination after apply. No engine in Replicate
Pricing	Free self-hosted engine	Quote. See Qlik.

Talk through skipprd now

Paul Bot knows the docs. Google Meet as soon as you join, any time of day.

Chat now →

Any time · 20 minutes · Google Meet now

What Qlik Replicate is good at

This is the log reader enterprises already trust on Oracle and Db2. Control tables, apply modes, and a weekend cutover runbook are the product. You can keep an existing May 2026 install, keep writing S3, and let Open Lakehouse compact Iceberg without an upgrade. If the job is "do not touch the source, land every change in the warehouse," that is a real CDC server.

Where the job is wider

Replicate is a replicator. It is not a Streamhouse. There is no Iceberg ∪ WAL. There is no skipprd query on in-flight rows. Iceberg is either Cloudera (with apply and LOB limits) or CSV-to-S3 plus a Cloud task that will not evolve schema and waits up to 15 minutes after a full load.

Their own guide is specific: no primary key that is a LOB; tables without a key drop LOB columns; a unique index with nulls can update or delete every matching target row; identity columns are not created on the target; do not run source maintenance during a task. Those are mechanisms, not jokes.

Skippr will not give you Attunity's SAP or mainframe source list. Skippr also will not replace a Replicate control-table estate. If the job is "enterprise log CDC into a warehouse we already query," Replicate is the narrower tool. If the job is live SQL on Iceberg you run, Replicate 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

CLI

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")

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 Qlik Replicate if you need Attunity-lineage log CDC into a warehouse or S3, and query after apply is enough. For the Cloud suite around it, see Qlik Talend Cloud.

Choose Skippr if you want one binary, live SQL, and Iceberg files that stay yours. Skippr will not replace a Replicate server on SAP or mainframe logs.

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