realtime.report

What It Is

Realtime Reporter is positioned as a tool for creating “out-of-the-box webscada implementations,” offering a Dashboard and REST API. Its website indicates that it provides interfaces around objects commonly used in industrial/SCADA scenarios, such as tags, logs, setpoints, and alarms. It is suitable for integration work such as device data visualization, reading tag status, retrieving alarms, and submitting logs.

Core Capabilities and Developer Experience

Based on the documentation, the currently published APIs include the Tag API, Logs API, and Changes API. These allow users to retrieve tags, update tags, record logs for one or multiple tags, and fetch setpoints and alarms. The Devices API and Reporter API are still marked as under development, suggesting that the product’s capabilities may not yet be fully available. Its API is described as a universal REST API that can communicate with all scripting languages. The getting-started tutorial uses PHP as an example: after initializing reporter_api with an API key, it requests /v1/tags/{id} and returns JSON data containing fields such as id, name, is_setpoint, is_alarm, value, Address, type, and offset.

Pricing, Deployment, and Ecosystem

The main content does not disclose any pricing model, free trial, plans, payment methods, or enterprise support information. It also does not clarify whether the product is open source, can be self-hosted, or supports private deployment. In terms of ecosystem, apart from the REST API and PHP example, there is no clear mention of integrations with PLCs, databases, MQTT, Grafana, alerting systems, or cloud platforms. Before procurement or production use, teams should contact the vendor directly to confirm licensing, SLA, deployment architecture, security mechanisms, and data compliance requirements.

Pros and Cons

The main advantages are that the API direction is clear, covering common WebSCADA use cases such as tags, logs, alarms, and setpoints; the REST API format is relatively friendly for system integration; and the documentation at least provides an API key flow, sample code, and response examples. The drawbacks are also obvious: publicly available information is very limited, the Devices/Reporter API is not yet complete, and the documentation lacks error codes, authentication details, rate limits, pagination, SDK installation instructions, and version management. The copy also contains spelling issues, and the overall documentation maturity is average.

Who It’s For and Access from China

It is better suited to industrial automation integrators, internal tool developers, or teams that need to quickly validate a WebSCADA API. If you need a mature open-source ecosystem, alternatives such as ThingsBoard, Node-RED, Grafana, and Ignition SCADA are worth comparing. Access from China cannot be determined from the available content; network connectivity, payment options, and localization support should be tested directly or confirmed with the vendor.