Automatically translate this page?

Regions — geographically distributed flespi datacenters

The location for all data in your flespi account.

Flespi platform is currently located in two independent data centers — in the Netherlands and in Russia.

Now new flespi customers are prompted to pick the region where they want all their flespi entities (channels, devices, subaccounts, etc.) and data (messages, intervals, logs) to reside. This is often critical for compliance with the national legislation (e.g. Russia requires all personal data to be stored on the territory of the Russian Federation).

By default, https://flespi.io provides authorization and registration in the EU region, while https://ru.flespi.io provides authorization and registration in the RU region.

Be attentive when picking the region since this determines the location for all your personal data.

You can have accounts in both datacenters registered for the same social network accounts or email/password but these will be two separate entities with distinct tokens to access them.

The two datacenters are completely autonomous with only some common services shared between locations, i.e. billing system, customer support system, protocols and devices databases, and some internal platform checking tools.

The datacenters have separate NOC channels — flespi_noc for EU region and flespi_noc_ru for the RU region. 

The configuration of all flespi regions can be retrieved via the following REST API call: https://flespi.io/auth/regions. Connecting to the RU region MQTT Broker or REST API endpoint requires the use of different hostnames — with “ru-” prefix, e.g.: ru-mqtt.flespi.io for MQTT and ru.flespi.io for REST.


See also
Once testing is done and your intentions become serious, follow this guide to upgrade your flespi account.
Complement and/or transform your device data to meet the requirements of a third-party platform.