Apache NiFi alternative — Apache NiFi vs Skippr

Apache NiFi is a Java flow engine. You draw processors on a canvas. Each unit of work is a FlowFile: attributes in a write-ahead log, bytes in a content repository, history in a provenance repository. The current line is 2.x (2.12.0 on 13 Sep 2026). Java 21. Clustering is ZooKeeper by default, or Kubernetes leases and a ConfigMap in 2.x. Back pressure, guaranteed delivery, and runtime edits are the design. CDC is a processor (often Debezium-shaped). Iceberg is a sink (PutIceberg, PutIcebergCDC). The project is Apache-2.0. Cloudera Data Flow is the managed path: deployments bill 0.30 USD a CCU-hour, per minute, plus your cloud bill. Functions bill from 0.10 USD an invocation. Snowflake Openflow is NiFi in a Snowflake coat; that is a different page.

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 canvas. No three-repository disk layout. ELT into a warehouse is one path, not the product.

Feature	Skippr	Apache NiFi
Deploy	Single Rust binary, your VPC or on-prem	Java 21 process or cluster. Cloudera Data Flow on EKS/AKS. Functions are Stateless NiFi
Schema	In-stream evolution, sibling columns	Per-processor. Record readers and writers. You wire the convert
Storage	Open Iceberg on Parquet you own	Wherever the last processor writes. Iceberg is one sink among many
CDC	Log-based; fails closed if the dest cannot honour	CaptureChange / Debezium processors on supported databases
Query	`skipprd query` on Iceberg ∪ WAL; history in any Iceberg engine	Provenance on FlowFiles. SQL is `QueryRecord` on a queue, not a lake
Pricing	Free self-hosted engine	Apache-2.0, pay your JVM and disks. Cloudera: see their CCU list.

What Apache NiFi is good at

The canvas is honest for routing. Listen on HTTP, fan out to S3, Kafka, and a warehouse, apply back pressure when a dest slows, and keep a provenance event for every hop. That lineage is why regulated teams still run it. Hundreds of processors (Cloudera lists 450-plus on Data Flow). You can change a connection while the flow is live. For IoT, syslog, files dropped on an edge box, or a protocol NiFi already speaks, that is a real product.

Where the job is wider

NiFi is a flow runtime, not a Streamhouse. There is no Iceberg ∪ WAL. There is no skipprd query on in-flight rows. QueryRecord runs on a queue. The lake starts after PutIceberg.

The disk layout is the ops. Lose the FlowFile repository and you lose track of in-flight work. Content and provenance want their own volumes and a retention policy. A cluster is election plus load-balanced connections, not a binary. 2.0 dropped XML templates and the Variable Registry; you had to pass through 1.27.0. NiFi Registry is marked for removal, so Git-shaped flow versioning is still a design you own. Python processors are not the centre.

Cloudera's meter is CCU time plus the Kubernetes bill. A flow that sits idle still holds a pod. Functions cap around 15 minutes and have no UI.

Skippr will not give you the canvas, provenance search, or that processor list. Skippr also will not listen on every industrial protocol NiFi already has. If the job is "route anything to anything on a graph," NiFi is the narrower tool. If the job is live SQL on Iceberg you run, NiFi 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 Apache NiFi if you want a canvas, provenance, and a processor for a protocol skipprd does not speak.

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

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

Apache NiFi alternative — Apache NiFi vs Skippr ​

What Apache NiFi is good at ​

Where the job is wider ​

Getting started ​

Which to choose ​

Apache NiFi alternative — Apache NiFi vs Skippr

What Apache NiFi is good at

Where the job is wider

Getting started

Which to choose