Furo Docs

IT requirements

What has to be approved at the site — per connection, and what applies in every case.

This page is meant for the operator's IT. It describes completely what a connection to Furo requires. Which way is an option for your asset is under The four ways, what the EMS has to provide for it under EMS requirements.

The most important point

On none of these ways does Furo open a connection into the customer network. Every connection that touches a site is opened outbound from there. So no way requires inbound port approvals, port forwarding, VPN tunnels or services reachable from outside.

Per connection

ConnectionApproval at the siteWhat Furo needs
Manufacturer cloudnoneaccess to the manufacturer API
Controller via brokeroutbound TCP 8883 (MQTT over mTLS)one client certificate per controller
Schedule handovernoneaccess to the partner API
Asset as clientoutbound TCP 443 (HTTPS) to api.furoenergy.comAPI key per asset
Virtual batterynone—

With manufacturer cloud and schedule handover nothing has to be set up at the site: the asset communicates with its cloud as before, and Furo talks to that cloud.

Approval by hostname or IP address

The two endpoints a site has to reach have a fixed IP address: the Telemetry API at api.furoenergy.com and the MQTT broker. A firewall rule can therefore name the hostname (FQDN) or the IP address. The hostname is preferable — it also survives a later change of address, which is announced beforehand in any case.

With manufacturer cloud and schedule handover Furo talks to the partner's cloud, not to the site. No approval is needed there.

Encryption and authentication

  • Every connection is encrypted: HTTPS in the REST patterns, MQTT over mTLS on 8883 at the broker. There is no unencrypted access.
  • The server certificates are publicly trusted and rotate automatically. Certificate pinning is therefore not recommended.
  • Authentication is per asset, not per company: one API key or one client certificate per asset. A compromised credential thus affects only that one asset and can be replaced individually.
  • Of API keys Furo stores only the hash, never the key itself.
  • Keys and certificates can be replaced at any time. A change is announced, the old credential only switched off after confirmation.

Data and location

  • The services run in the Google Cloud region europe-west3 (Frankfurt am Main), the database on Supabase in eu-central-1 (AWS Frankfurt). Both locations are in Germany; there is no transfer to a third country.
  • Only asset-related measurements and schedules are transmitted. Personal data is not part of the interface.

What the EMS itself has to provide

This page covers only network and security. Which limits the EMS accepts, which measurements it delivers and how it behaves without a schedule is under EMS requirements — the list that should reach the manufacturer before ordering.

On this page