Skip to content

08 Features

Security and data

Your data stays yours: isolated per customer by the database itself, not by an application filter, and hosted in Italy on Nexilica infrastructure.

Data in Italy Isolated in the database Roles and permissions The gateway calls out

Illustrative figures.

How it works

Underneath everything else

Security is not a section of the datasheet: it is the condition that makes everything above it usable. If the data is not defensible, it is not evidence either.

The field opens no ports

The gateway opens the connection to the system, never the other way round. No inbound port is needed on the plant network, and that is what keeps the conversation with whoever defends it short.

Isolated by the database

Each customer has a dedicated user and row policies that bind what that user can read. Isolation sits in the connection, not in an application filter somebody can forget.

Permissions per plant

Whoever runs a site sees theirs, whoever coordinates sees the portfolio. Roles are assigned per plant rather than per table, because that is how the work is organised.

Hosted in Italy

The infrastructure is ours and it is in Italy, in both forms the service is delivered. Data sovereignty is a verifiable location, not a statement.

What comes out

What it means in practice

Security claims are only worth something if they say how. These say how.

Managed service, in two locations

Where it is used

In every industry, no exceptions

The protocol changes, the way of working does not. It is why the same measurement layer sits under plants that have nothing in common.

Who can see
your data?

A 30-minute technical call with whoever handles networks and security at your company. Awkward questions are welcome.