Argus Flow
An open-source data pipeline distribution that gathers everything you need to run Apache NiFi 2.10.0 in production. Custom extension bundles (NARs), deployment packages (tar.gz, RPM, container images), a Kubernetes operator, and configuration/certificate/user-management tooling — consolidated from scattered repositories into a single monorepo so every artifact ships from one build pipeline at matching versions.
Highlights
Extensions, distribution, and operator in one pipeline
NiFi extensions, the operator, and the certificate scripts used to live in separate repositories, which made versions drift apart. They are now a single monorepo: one make target produces NARs, tar.gz, RPM, and container images at matching versions.
12 bundles, 18 NARs, isolated dependencies
Extensions are split into domain bundles and each bundle is packaged as its own NAR, so third-party dependencies never collide across bundle boundaries. Deploy only what you need from CDC, lakehouse, Hive, Parquet, database, reporting, and flow analysis.
A NiFi 2.x Kubernetes operator without ZooKeeper
It uses NiFi 2.x native Raft coordination, so clusters run without ZooKeeper. NiFiCluster and NiFiFlow custom resources give declarative management, scale-down performs a safe Offload → Disconnect → Remove sequence, and cert-manager integration issues TLS certificates automatically.
Configuration, certificates, and accounts handled by tooling
Instead of hand-editing a 200-line nifi.properties and its XML files, an interactive wizard collects the values and shows a diff before saving. The --check diagnostic catches certificate SAN mismatches, upcoming expiry, and commented-out login providers — preventing failures such as Invalid SNI.
What's in the distribution
Extension bundles, deployment packages, the Kubernetes operator, and the operations tooling are built together from one repository, while each directory can still be built on its own.
Core Capabilities
From CDC, lakehouse, Hive, and file-format extensions to operational governance rules, database authentication, distribution packaging, the Kubernetes operator, and configuration/TLS automation — twelve pillars of NiFi operations in a single distribution.
Four CDC sources
Built on Debezium Embedded Engine 3.2.2, emitting change events from major relational databases as JSON FlowFiles.
Lakehouse sinks
Load records directly into open table formats and columnar stores.
Database processors
Broader relational integration, from querying to bulk loading.
Hive / ORC
Hive3 integration and ORC output in a dedicated bundle.
File formats & record serialization
Readers and writers that let you control timestamp formatting.
General-purpose processors
Recurring field requirements folded into the standard bundle.
Five monitoring reporting tasks
Watch node resource state against thresholds and notify externally.
Six flow analysis rules
Operational governance rules that flag flow anti-patterns through static checks.
Database authentication & authorization
Providers built for environments where neither LDAP nor an external IdP is an option, so nobody has to hand-edit users.xml.
Distribution packaging
Repackages the official binaries into artifacts you can put straight into production.
Kubernetes operator
Define NiFi 2.x clusters declaratively and automate scaling and updates.
Configuration & TLS automation
Standardizes the configuration areas where things most often go wrong right after installation.
Editions
Use the entire open-source distribution freely as Community, or move to Enterprise when you need an operational SLA and dedicated technical support.
Community
Use and operate the extension bundles, deployment packages, operator, and tooling without restriction.
Enterprise
Everything in Community plus SLA-backed dedicated support, deployment and migration services, and custom extension development.
A NiFi production distribution released as open source
Argus Flow is published on GitHub under the Apache License 2.0. Extension bundle sources, distribution packaging, the Kubernetes operator, and the operations tooling are all open, so enterprises can audit the code, extend it for their own environment, and run it entirely on their own — even in air-gapped networks.
- Apache 2.0 with no commercial-use restrictions
- Upstream attribution and license headers verified in the build
- Self-operated on-premises or air-gapped