// the find
apache/streampipes
Apache StreamPipes - A self-service (Industrial) IoT toolbox to enable non-technical users to connect, analyze and explore IoT data streams.
StreamPipes is an Apache-governed industrial IoT platform that lets non-engineers wire up OPC UA, MQTT, Kafka, and other industrial data sources into processing pipelines through a drag-and-drop UI. The backend is Java, the pipeline elements run as microservices, and the whole thing ships as Docker Compose or Helm. It's aimed at manufacturers and operations teams who need to get machine data flowing without writing ETL code from scratch.
OPC UA support is first-class — includes a browser-based node explorer and event subscriptions, which is genuinely rare in open-source tooling. The extension model is well-thought-out: custom processors/sinks are standalone microservices built against a Java SDK and deployed independently, so you're not patching the core to add a new connector. Multi-transport support (NATS default, Kafka, Pulsar, RabbitMQ) with environment-specific Compose files means you can slot it into an existing message bus without rearchitecting. Active Apache governance means the project won't quietly die — there's a dev mailing list, release process, and Jira.
730 stars for a platform this heavyweight is a red flag — the community is small relative to the footprint, and that matters when you hit an obscure OPC UA edge case at 2am. The full stack is a lot of moving parts (CouchDB, InfluxDB, NATS, extensions service, UI, core backend) — the Compose file is not something you hand to a junior ops person and walk away. Python and Go clients exist but the SDK story is Java-first; anything non-JVM is a second-class citizen. No hosted offering means every deployment is your problem to maintain, upgrade, and back up.