Skip to content

Industrial AI, on your servers or ours

The same Overvis HMI, in our EU cloud or on your own servers, with the AI models you choose.

  • Our cloud or your servers

    EU cloud, dedicated cloud, your own data centre or an air-gapped network.

  • Minimise the surface

    No passwords and no admin API. Devices sit in a closed VPN.

  • Full control

    The AI writes nothing to a device until a person approves it.

  • Each site is isolated

    Own members, roles and equipment per site, on one bill.

Choose the isolation level you need

Every option runs the same software, the same AI and the same gateways. They differ in where the servers are, who runs them and whether data leaves your network.
EU cloudDedicated cloudOn-premisesAir-gapped
Where it runsOvervis servers in Germany, sharedA separate installation for you, in the EU or in your own cloud accountYour data centre, inside your networkYour hardware, in a network with no internet
AI modelsEU-hosted modelsEU-hosted models or your own providerYour own provider or models on your serversModels on your servers
Data leaves your networkYes, to Overvis in GermanyTo your chosen region onlyOnly where you allow itNever
Operated byOvervisOvervisOvervis with your ITYour IT, with Overvis support
UpdatesContinuousScheduled with youScheduled with youDelivered as packages
Sign-inEmail code, passkeys, authenticatorSSO with your identity providerSSO with your identity providerSSO with your identity provider
Ready for a pilotThe same dayWithin weeksWithin weeksWithin weeks

Securityat every layer

Install Overvis HMI on your own servers and the whole system stays inside your network. Devices talk only to your servers, and nothing is reachable from the internet unless you open it.

Servers

We own our infrastructure

Overvis runs on its own infrastructure, not on AWS, Azure or Google Cloud, and depends on no cloud provider. That is why the same system installs on your servers unchanged.

Only what you choose faces the internet

On your own servers you can close everything to the internet except what your end clients need, such as viewing their stored data.

Access

Every API call runs with the caller's rights

There is no admin API with its own sign-in or wider access. Every call is made as a user and limited to that user's role, so no key or account opens all the others.

There are no passwords to steal

People sign in with a passkey, a one-time code by email or from an authenticator app, or SSO with your identity provider. A passkey's secret never leaves the person's own devices.

Devices

Devices cannot reach each other

Each device connects to the servers through its own encrypted VPN tunnel. The VPN carries no traffic between devices or between users, so one device cannot reach another.

Each device answers only what it must

A device answers only requests from your servers, and only the ones your installation uses. Where a controller cannot filter requests itself, the MC252 and the AI help set up the filtering in front of it.

Response

The AI helps audit an installation

It lists who has which role, which API keys exist and which devices are connected, and goes through them with your team.

The AI helps you respond to a vulnerability quickly

When a vulnerability is published, it finds the affected devices and prepares the changes. A person approves them before anything is sent.

AI that works under your rules

Every change is approved.Every action is recorded.

Before anything is written to a device, a person with the right role approves it, with the device, the parameter and the new value in front of them.

  • Write limits. A value can have a minimum and a maximum. A write outside them is refused, whoever sends it.

  • Full audit log. Every action by a person or the AI: who, when and what, from a setting to a write.

  • Revert. Return a workspace to an earlier setup when a change was wrong.

Assistant action

Do you allow the assistant to lower the peak demand limit at the factory?

Site
Factory, main feeder
Parameter
Peak demand limit
New value
650 kW
RejectAllow

Each workspace has its own team.Each role has its own rights.

Five roles, View only, Operator, Editor, Admin and Owner, decide what each member of a workspace can see and change. The AI acts with the rights of the person who asked.

  • Roles per workspace. The same person can be an Editor on one site and View only on another.

  • SSO. Sign in through your identity provider, over SAML or OpenID Connect, on enterprise installations.

  • Keys with your rights. API keys act with their owner's rights, and admins see every CLI key in the workspace.

Current members

  • Anna Lind

    anna@example.com

    Owner
  • Tomasz Kowal

    tomasz@example.com

    Admin
  • Marek Nowak

    marek@example.com

    Editor
  • Jonas Weber

    jonas@example.com

    Operator
  • Night shift

    nightshift@example.com

    Operator
  • Field service

    service@example.com

    View only
  • External auditor

    audit@example.com

    View only

The assistant works as the signed-in member and can do only what that role allows.

Built for scale

Horizontally scaled

Databases, services and the API all scale out. An installation starts on a few servers and grows with no fixed limit on sites, devices or users.

  • Readings. Stored with 1-minute to 1-hour aggregates, so reports over long periods stay fast.
  • Devices. Connections and polling are spread across servers.
  • API. Requests and live value streams are spread the same way.

Workspace isolation

Full isolation: devices, data, dashboards, automations and the audit log stay inside their own workspace. Nothing in one workspace can read another.

  • Roles. Five per workspace, from View only to Owner. The AI acts with the rights of the person who asked.
  • Keys. A workspace API key works only in its own workspace.
  • Devices. Adding an MC252 takes someone at the device to press its button or read the code on its screen.

Open integration

Devices, readings, dashboards, alarms, automations and the audit log are all in a documented, typed API, which the CLI uses too. Your team or integrator builds the integration with your WMS, MES or APS on it.

  • Read. Live values as a stream, raw readings and aggregates over any period, and the alarm log.
  • Export. The audit log as JSON or CSV.
  • Write. Values to devices under the same roles and limits as in the app, readings from other systems, and constants such as tariffs or targets.

Start with a pilot

A pilot runs on one of your sites, with your equipment and your team, before anything is rolled out.
  1. 1

    We agree on the scope

    A call about your sites, equipment and security requirements, and the deployment that fits them.

  2. 2

    Your team works on real equipment

    Gateways go in, the AI sets up the devices, and your team works with it on one site.

  3. 3

    You get a written review

    A report on what was set up, how your team used it and what a roll-out would take.

  4. 4

    The roll-out is quoted per year

    The quote covers the deployment, gateways at volume price, invoicing and the SLA.

Plan a pilot

Tell us about your sites. A technical specialist answers within two working days.

We use these details only to answer you. See the privacy policy.

Frequent questions

Where is our data stored?

In the EU cloud, on servers in Germany. In a dedicated cloud, in the EU region or the cloud account you choose. On-premises and air-gapped, on your own servers and nowhere else.

Can we use our own AI models?

Yes. Use your own provider account, or models running in your infrastructure. An air-gapped installation always runs on models inside your network.

Who approves the AI's changes?

A person with the right role. Every write to a device and every change to the setup waits for their approval and goes into the audit log. Write limits are checked before anything is sent.

Do you support single sign-on?

Yes, on enterprise installations: SAML or OpenID Connect with your identity provider, such as Microsoft Entra ID, Okta or Google Workspace.

How does it help with NIS2 and the EU AI Act?

Human approval before changes, a log of every action and role-based access are the controls both expect. Overvis HMI holds no certification yet; send your questionnaire and we answer it in full.

Can we export our data?

Yes. Device setup, screens and the full history of readings export with tools built into the product.

How are on-premises installations updated?

Updates are scheduled with your IT. Air-gapped installations receive them as packages your team installs.

What does a pilot cost?

It is quoted for the site: the gateways, the usage for its duration and the support. The proposal states it in writing before anything starts.

Can we sell it under our own brand?

Yes. The software and the gateways can carry your brand, with regional exclusivity open to negotiation. The Partners page covers reselling.

Do you sell gateways in volume?

Yes, at volume prices, with one billing account for all your sites and invoicing by bank transfer.

Cookies