Trust Center · as of October 2026

Who may write to your plants? And how is that secured?

eco2lot reads data from your plants and can write setpoints back on request. That is exactly why IT and operations management ask a few clear questions before a decision. Here are the answers, in plain language, with links to the product pages where the technical details continue.

  • Reading is the default; writing needs an approval per data point
  • The connection goes from the inside out; your controllers stay behind the firewall
  • Your data lives where you decide: Germany, EU cloud or on your premises
Plant room with an open control cabinet containing a small edge computer with a green status LED and neatly routed network cabling
Reading is the default Collecting measured values needs no write access.
Writing only with approval Per data point: value range, role, read-back.
Connection from the inside out Inbound ports stay closed.
Every command in the audit log Who, when, which value, confirmed by the device.
How the data flows

From the plant to the platform and back on request

The way in is always open: measured values flow encrypted from the eco2node to the platform. The way back is closed until you open it for a specific data point, and then four rules apply.

The way of the data: always read, write only with approval YOUR PLANT NETWORK · BEHIND YOUR FIREWALL RefrigerationController, sensors, meters Heating / PVRegulators, inverters ProductionPLCs, machines, instrumentation eco2node Modbus · OPC UA · M-Bus · BACnet buffers locally, sends encrypted Firewall TLS, from inside only with approval ECO2LOT PLATFORM · GERMANY, EU OR YOUR SITE Read: dashboards, alarms, analyses Measured values, states, diagnostics. Reading is enough. Roles per tenant, site and data point. Write: four rules per data point Approval: only explicitly approved points Value range: each point has permitted limits Role: only authorized people Read-back + audit log: device confirms the value
Always read, write only with approval: the way back to the plant stays closed until you open it for a specific data point.
A recent example

In October 2026 in France, and in early November also in German supermarkets, refrigeration controllers were changed remotely. The controllers reported "all fine" because they ran exactly the setpoint someone had entered. The plant is yours. Is the controller, too? That is why at eco2lot the way back to the plant stays closed until you open it deliberately, and a second measurement layer reports when the real process deviates from the target.

How eco2node keeps the connection inside-out
The five questions

What your IT and your operations management want to know

Question 1

Who may write to our plants via eco2lot?

Only those who are approved for it. By default, eco2lot only reads.

eco2lot collects measured values and states from your plants. That is the everyday work of the platform, and nobody needs write access for it.

If eco2lot is to send a setpoint, that is a deliberate decision per data point. You define which point is controllable, which range the value may stay within and which role may change it. Every command is logged, and the device reports the value back so that it is visible what actually arrived.

How eco2lot controls within safety limits
Question 2

How does eco2lot reach the plants without exposing a controller to the internet?

The connection goes from the inside out. Your controllers stay behind your firewall.

The eco2node sits in your plant room, in the separated plant network. It talks to controllers, meters and regulators via the usual protocols: Modbus, OPC UA, M-Bus, BACnet.

The eco2node establishes the connection to the platform itself, encrypted via TLS. There is nothing to address from outside: inbound ports stay closed, your controllers stay invisible to the internet. If we are asked to check something on the eco2node, we use your VPN access, by your rules, time-limited and logged.

About eco2node
Question 3

Where is our data?

Wherever you decide: with us in Germany, in your cloud or on your own infrastructure.

You have three options. We operate eco2lot for you in ISO 27001-certified data centres in Germany, including updates, backups and support. Or eco2lot runs as a dedicated instance on a cloud platform in the EU, with its own database and its own configuration.

Or the entire platform runs at your site, in your own data centre or server room. Then your operating data never leaves your premises.

The three hosting models
Question 4

Who sees what, and who may change what?

Permissions apply per tenant, per site and per data point.

A plant manager sees their sites, an energy manager all plants, a service provider only the systems they are responsible for. Reading and changing are separate permissions: you define who may change setpoints, alarm limits or approvals — per data point.

External partners such as refrigeration contractors, energy consultants or manufacturers get their own restricted access instead of your admin account.

Administration and roles
Question 5

How do we notice when a plant behaves differently than it should?

Through a second, independent layer: measured values, target-actual comparison and alarms.

Every change to controllable data points is in the audit log: who, when, which value, confirmed by the device. Independently of that, eco2lot observes the real process. If the temperature in the cold store rises faster than usual, the heating runs outside its schedule or the PV system delivers nothing in sunshine, an alarm rule fires.

This works equally for defects, operating errors and unauthorized access. The notification goes out by email, SMS or into your control system, with an escalation chain: who is informed after how many minutes.

Alarms and escalation

What you should know about the security of eco2lot

Can eco2lot switch or shut down a plant on its own?

Only if you approve exactly that data point for it, with value range and role. Without approval eco2lot reads and alerts. Safety-critical interventions belong in local protection logic in the PLC; the platform remains the layer that observes and reports.

Does BS-Systeme need permanent remote maintenance access to our network?

Not for operating the platform. For support on the eco2node we use your VPN access by your rules, time-limited and logged.

What happens if the connection to the platform drops?

The eco2node buffers measured values locally and sends them on once the connection is back. If the connection stays down, eco2lot reports the outage as its own alarm. Missing data is therefore visible and never a silent gap.

Questions about pricing, hosting or onboarding beyond security? They are collected in the general FAQ.