NiFi MiNiFi

NiFi MiNiFi is a lightweight tool that collects data from remote sources, such as sensors or branch offices, and sends it to a central system.

  • Automation
  • Databases
  • Tools & Utilities
NiFi MiNiFi is a lightweight tool that collects data from remote sources, such as sensors or branch offices, and sends it to a central system. It is designed to run efficiently on small devices, allowing you to manage and transport information reliably from the very edge of your network.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

70/100 Good

Maintained
100last commit 2 days ago
Popular
45178 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
77no serious findings, 3 minor, CI, tests

Based on 4 of 5 factors.

GitHub stars
178
Open issues
13
Last commit
2026-11-19
Latest release
rel/minifi-cpp-1.1.0
License
Apache-2.0
Activity
steady

Checked 2 days ago - source: GitHub (apache/nifi-minifi-cpp)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Fill in the config before starting Use MiNiFi's text configuration file (YAML) as a template and set your own keystore/truststore files (the files and passwords that protect encrypted connections) and any log or output paths. If you leave the example values such as /tmp/ssl or localtest, MiNiFi may not connect securely or may read/write the wrong files. source
  • Register and start it as a service From the MiNiFi folder, run bin/minifi.sh install, then run sudo service minifi start (sudo is the admin command on Linux/Mac). Installing first is required; if you skip it, the service command has nothing to manage and MiNiFi will not run as a managed background service. source
  • Start it in the background for testing From the MiNiFi folder, run bin/minifi.sh start to launch it while keeping your terminal available. This is useful before you set up a service, but closing the terminal or stopping the process will stop MiNiFi. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I install MiNiFi as a background service?

From the MiNiFi folder, run bin/minifi.sh install and then start it with sudo service minifi start. You must install it first; otherwise the service command has nothing to manage. For short testing, bin/minifi.sh start also works, but stopping the terminal stops MiNiFi.

What MiNiFi configuration values should I replace before startup?

Use the YAML configuration file as a template and set your own keystore and truststore files, passwords, and log or output paths. If you leave example values such as /tmp/ssl or localtest, MiNiFi may not connect securely or may read and write the wrong files.

Why do my MiNiFi.properties changes disappear after restarting?

A Cloudera user reported that minifi.properties can be reset to previous values on every start, erasing changes such as nifi.flow.engine.threads=5. This made the property disappear after adding it to the file.

Is it acceptable to use MiNiFi to pull from a NiFi output port?

A support thread notes that using an RPG on MiNiFi to pull from a NiFi output port is not ideal. This comes up in the context of sending data from NiFi to MiNiFi with the same configuration.

Answers sourced from community.cloudera.com, community.cloudera.com, github.com, github.com

Community

Collected 48 days ago - public community threads