3 apps IoT Data
Emoncms screenshot thumbnail

Emoncms

Energy meters, solar systems, heat pumps, and temperature sensors report to Emoncms, which logs every reading as a time series and turns it into graphs, dashboards, and ready-made apps. Readings arrive over an HTTP input API, MQTT topics beneath emon/, or AES-encrypted posts for devices without HTTPS, from scripts, Node-RED, Home Assistant, or emonHub. Input processing calibrates values, combines inputs, converts watts to cumulative kilowatt-hours, and logs the result to a feed. Device templates configure known hardware in one step, and schedules limit processes to set time windows. The graph viewer plots feeds on two axes, groups them into daily, weekly, monthly, or annual bars, and offers feed statistics and CSV export. Virtual feeds calculate values like heat pump COP on request and store nothing; post processing rebuilds feeds from recorded data. My Electric Flow charts live solar, battery, and grid power with an energy-flow breakdown and a Tariff explorer for Octopus Agile and other time-of-use tariffs. My Heatpump reports COP and SCOP. Other apps cover boilers, solar diversion, CO2 air change rates, and the UK grid fuel mix. The dashboard editor places dials, gauges, thermometers, charts, text, and images, and a dashboard can be made public. Sync uploads feeds to another server on a schedule and downloads them for recovery; the Backup module backs up and restores data. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Deploy
Apache IoTDB screenshot thumbnail

Apache IoTDB

Sensors on factory floors, wind turbines, and connected vehicles produce readings every second, and Apache IoTDB is the time-series database built to store those readings and answer questions over them. Devices write through client sessions that tolerate out-of-order, delayed, and multi-frequency arrivals, so a gateway that reconnects after an outage can backfill history without corrupting the timeline. Series live in a device hierarchy you can browse like a directory tree, or in tables queried with standard SQL, common table expressions, set operations, and more than one hundred built-in aggregation and time-series functions. The TsFile columnar format shares one time column across aligned series and applies encodings designed for sensor data, which keeps high-frequency archives compact while Spark and Hadoop jobs read the same files directly for larger analysis. Pipe synchronization streams records or transfers whole TsFiles between edge sites and central clusters with path and device filtering, so plants keep collecting locally while headquarters queries a continuous copy. AINode brings forecasting, anomaly detection, and missing-value imputation into the database itself: register a model with SQL, then ask for predictions in the same query language instead of shipping measurements to a separate machine learning service. A low-memory Edge edition runs collection on constrained gateways, and clusters scale by adding DataNodes under ConfigNode coordination with automatic load balancing. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy
Arc screenshot thumbnail

Arc

Arc keeps the telemetry you cannot afford to lose in one open time-series database, so last minute's sensor readings and last year's can be queried together with plain SQL. Metrics usually end up split between a fast recent store and a forgotten archive, and Arc removes that split. Data lands as open Apache Parquet on local disk, S3, Azure Blob, or any S3-compatible store such as MinIO, R2, or SeaweedFS, while background compaction merges small files and hot and cold tiers move older data to cheaper storage. Writers can send MessagePack columnar batches, InfluxDB Line Protocol, Prometheus Remote Write, MQTT topic subscriptions, or TLE satellite data, and existing Telegraf agents point at it without changing the collection layer. Queries support window functions, CTEs, joins, and aggregations, and results return as JSON, columnar MessagePack, or Apache Arrow IPC, with an optional Arrow Flight SQL listener for ADBC clients. Retention policies, continuous queries for rollups, a write-ahead log, backup and restore, token authentication with RBAC, per-token quotas, and GDPR-style deletes cover the data lifecycle. Grafana, Superset, a VS Code extension, a Python SDK, and the arcli command line connect to it, and the companion Launchpad web console adds a SQL console, log viewer, monitoring charts, alerts, and MQTT management. It runs as a single binary and serves HTTP on port 8000. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Deploy