Self-Hosted Energy Monitoring with IAMMETER

Self-Hosted Energy Monitoring with IAMMETER

IAMMETER meters are not limited to IAMMETER-Cloud. Their open interfaces allow electricity data to be stored and processed on a server controlled by the customer.

There is no single self-hosted architecture that fits every project. The right choice depends on whether you need:

• a ready-to-use local monitoring interface;
• data middleware for an enterprise application;
• integration with an existing open-source platform;
• direct ingestion into your own EMS, BMS, ERP or IoT backend.

IAMMETER supports all four paths:

                        ┌─→ IAMMETER-Docker ─→ Local charts and APIs
IAMMETER energy meter ──┼─→ IAMMETER-Central ─→ Customer ERP / EMS / BMS
                        ├─→ Open-source platform ─→ Automation and dashboards
                        └─→ Customer receiver ─→ Custom backend and database

This page helps you select an architecture. Detailed installation and protocol instructions are maintained in the linked technical guides.

1. Compare the Four Deployment Paths

Option	Primary user	Ready monitoring UI	Data storage	API for customer development	Development effort
IAMMETER-Docker	Individual users, developers and small local projects	Yes, with basic monitoring functions	Customer server	Yes	Low to medium
IAMMETER-Central	Enterprises, partners and system integrators	Device-management UI only; no complete energy-analysis UI	Customer MySQL or MariaDB	Yes, designed for customer applications	Medium
Open-source platform	Users already operating Home Assistant, Node-RED or another platform	Provided by the selected platform	Depends on the platform	Depends on the platform	Low to medium
Direct integration	Customers with their own backend and engineering team	No	Customer-defined	Customer-defined	High

The simplest choice is not always the smallest software component. Select the option that removes work your team does not want to build or maintain.

2. Quick Recommendation by User Type

Choose IAMMETER-Docker when:

• you want a local interface and historical monitoring quickly;
• the project is operated by an individual or a small technical team;
• the server is a Raspberry Pi, mini PC, NAS or private host;
• you want APIs for extending the interface later;
• you need a practical starting point without building the ingestion backend.

Choose IAMMETER-Central when:

• the customer already has an ERP, EMS, BMS or custom front end;
• the application needs a consistent API layer for IAMMETER devices;
• data must be stored in a customer-managed MySQL or MariaDB database;
• the project needs device and measurement middleware rather than a ready-made energy-analysis product;
• the integration team wants to avoid implementing every meter-side transport and payload parser independently.

Choose an open-source platform when:

• Home Assistant, Node-RED, OpenHAB, ioBroker, Zabbix or ThingsBoard is already part of the project;
• the platform already provides the required dashboard or automation features;
• you do not need a separate IAMMETER-specific backend.

Choose direct integration when:

• your organization already operates an ingestion service and database;
• your backend can receive HTTP/HTTPS, MQTT/MQTTS or TCP/TLS data;
• your engineers want full control of the data model, retention and business logic;
• the additional development and operational responsibility is acceptable.

3. IAMMETER-Docker: A Ready Local Monitoring System

IAMMETER-Docker is an open-source, self-hosted energy monitoring system. It combines data ingestion, storage, basic energy-monitoring functions, charts and APIs in one deployment.

What IAMMETER-Docker provides

• deployment on a customer-controlled server;
• basic electricity-consumption and solar-monitoring functions;
• historical data and charts;
• SQLite and MySQL support;
• API access for developing a custom UI;
• support for IAMMETER meters and custom SN workflows;
• optional datalogger use cases for local collection.

What it is best at

IAMMETER-Docker is a strong choice when the user wants to begin monitoring locally before writing custom software. A developer can use the built-in interface first and add a separate dashboard or data workflow through the available APIs later.

What to consider

The customer remains responsible for the host, network, updates, backups, storage capacity and security. IAMMETER-Docker provides application functionality, but it does not remove normal self-hosting operations.

Continue with:

• Deploy IAMMETER-Docker
• IAMMETER-Docker Advanced Features
• Offline Datalogger Mode

4. IAMMETER-Central: Data Middleware for Customer Applications

IAMMETER-Central is private-deployment middleware for enterprises, partners and system integrators.

What IAMMETER-Central provides

• registration and management of IAMMETER devices;
• storage and management of voltage, current, power and energy data;
• MySQL and MariaDB support;
• APIs for customer-developed applications;
• a consistent middleware layer between IAMMETER meters and an ERP, EMS, BMS or custom front end.

IAMMETER product SNs and supported Virtual Meter SNs can be registered in IAMMETER-Central. This differs from the custom-SN flexibility available in IAMMETER-Docker.

What IAMMETER-Central does not provide

IAMMETER-Central is not a complete energy-consumption or solar-analysis application. Its interface is focused on middleware and device management. The customer supplies the business UI, reports, permissions and workflows required by the final application.

This separation is valuable when an enterprise already has its own management system and needs a maintained way to bring IAMMETER measurements into it.

5. IAMMETER-Central or Direct Integration?

Both approaches can deliver meter data to a customer-owned application, but the engineering boundary is different.

Responsibility	IAMMETER-Central	Direct integration
Receive meter uploads	Handled by Central	Customer implements it
Parse IAMMETER payloads	Handled by Central	Customer implements it
Store meter measurements	Handled through Central's database layer	Customer designs it
Device registration	Central workflow	Customer designs it
API for ERP/EMS/BMS	Central API	Customer builds it
Final business UI	Customer builds it	Customer builds it
Protocol-level control	Less customer code required	Full customer control

Choose Central when your main goal is to use meter data in an existing business application without owning the complete ingestion layer.

Choose direct integration when your engineering team already has the required ingestion, device-management and storage infrastructure, or when the project requires a highly specialized data path.

For the receiver-side engineering involved in direct integration, see Receive IAMMETER Energy Data on Your Own Server.

6. Use an Existing Open-source Platform

An existing platform may already provide the exact dashboard, automation or monitoring functions the project needs.

Supported integration paths include:

• Home Assistant for local energy dashboards and automation;
• Node-RED for data flows and control logic;
• OpenHAB and ioBroker for home automation;
• Zabbix for infrastructure-style monitoring;
• ThingsBoard for IoT dashboards and workflows.

Each platform page is the authoritative implementation guide for that platform, while this page only helps you select the appropriate deployment path.

For a broader comparison, see Integrate IAMMETER with Self-hosted and Open-source Systems.

7. Build a Completely Custom Backend

IAMMETER meters can send data directly to a customer receiver using supported open interfaces such as:

• MQTT or MQTTS;
• HTTP or HTTPS;
• TCP or TLS.

A custom backend gives the customer full control over:

• device identity and site mapping;
• raw and normalized data storage;
• retention and aggregation;
• reports, tariffs and alarms;
• application users and permissions;
• integration with existing enterprise services.

It also makes the customer responsible for protocol handling, validation, scaling, availability, monitoring and security.

Start with:

• Develop Your Own Energy Monitoring System
• Receive IAMMETER Data on Your Own Server
• IAMMETER Local APIs and Open Interfaces
• MQTT Integration Guide

8. Local Operation and Data Ownership

Self-hosting means the customer controls the application host and its stored data. Whether the complete system can operate without Internet access depends on the selected architecture and network design.

Typical LAN-only paths include:

• meter to IAMMETER-Docker on the same network;
• meter to a locally deployed IAMMETER-Central instance;
• meter to a local MQTT broker;
• a local platform reading the meter through Local API or Modbus TCP;
• meter upload to a receiver on the same LAN.

A remote server still requires an Internet connection, private WAN or VPN path. Local access and IAMMETER-Cloud use are not necessarily mutually exclusive, but coexistence depends on the selected run mode and deployment configuration.

For the distinction between no Internet, no cloud and no local network, see Use a Wi-Fi Energy Meter Without Internet or Cloud.

9. Plan for Growth

A successful pilot should have a path to production scale.

Before selecting a platform, confirm:

1. expected meter and channel count;
2. required upload or polling interval;
3. daily record volume and retention period;
4. database, backup and recovery requirements;
5. tenant, site and user-permission model;
6. monitoring and last-seen alerts;
7. Internet-independent operation requirements;
8. integration points with ERP, EMS, BMS or automation systems;
9. who maintains the server, database and application;
10. whether the customer needs a ready UI, middleware APIs or complete protocol control.

The best architecture is the one whose operational boundary matches the team that will maintain it.

10. Recommended Next Step

Your goal	Start here
Run a local monitoring interface quickly	Deploy IAMMETER-Docker
Integrate IAMMETER data with an enterprise application	Evaluate IAMMETER-Central
Add IAMMETER to a smart-home platform	Home Assistant Integration
Compare supported open-source platforms	Self-hosted Integration Overview
Build a custom data receiver	Receive Data on Your Own Server
Review all meter-side interfaces	Firmware and Open Interface Guide

For an enterprise or partner deployment where the correct boundary between Central and direct integration is unclear, contact IAMMETER with the expected device count, database requirement and target business system.

Last updated: July 16, 2026