Skip to content
Proxus 2.0.1 Licence and sign-in fixes after the 2.0 upgrade Release notes
Try free Book a demo

Deployment scenarios · No internet at all

No internet, from install to licence.

Some plants never touch the internet. Proxus installs from a package, activates its licence offline and runs with no connection outside your network.

Book a demo All deployment scenarios
Where
Inside the isolated network, at any level
Install
The install package, with the images loaded from files
Fits
Defence, pharma, energy and any site without an internet path

The layout

Where everything sits.

L4–L5 Enterprise and cloud L3.5 Plant DMZ L3 Operations L1–L2 Control and machines Internet Not needed Install package Images and licence, carried in Your systems On the same network Proxus hub Namespace, historian, screens Edge Gateway Line 1 Buffering Edge Gateway Line 2 Buffering PLCs Line 1 CNCs Line 1 Meters Line 2 Sensors Line 2
  • Proxus
  • Your systems
  • Not needed
  • Reads machines
  • Values, buffered by the sender
  • Installs and updates

What you install

The hub
From the install package: the installers run without internet, and the container images are loaded from files.
The licence
Activated offline: the key is checked on the server against its signature and expiry.
The gateways
Use the images already on the host when no registry can be reached.
Sign-in
Single sign-on with an identity server that runs inside your network too, if you want it.

How it connects

Outside your network
Nothing. Hub and gateways need no internet access at any time.
Inside it
As in Hub and edge gateways: each gateway connects out to the hub on 7422, over TLS.

When something fails

The link to the hub drops
Each gateway keeps reading, runs its rules and functions and serves its own MQTT broker. Values wait on its disk with their original time and reach the hub in order when the link returns.
A gateway stops
Docker starts it again. Its machines are not read in the meantime; the other gateways are not affected.
The hub stops
The gateways keep collecting and buffering. Screens, history and alarms in the hub are unavailable until it is back, then the backlog arrives.
A gateway is lost
Revoke it in the hub: its key stops working within seconds, and no other gateway shares it.

The limits

Updates
New versions arrive the same way, as a package you carry in.
AI Assistant
Runs with a language model inside your network; cloud models are out of reach by design.
One gateway per set of machines
A gateway runs as a single instance. If it stops, its machines are not read until it is back; no second gateway takes over.
A restart during a hub outage
A running gateway rides out a hub outage. A gateway that is restarted while the hub is out of reach starts processing when the hub answers again.

Other layouts

Layouts combine. These are the other six.

Next step

Place it on your own plant.

Bring a sketch of your networks and the machines you want to connect. An engineer places the hub and the gateways on it with you, with the firewall rules your IT team will ask for.

Book a demo Talk to an engineer

  1. Scoping call

    Equipment, protocols, sites and the systems the data has to reach.

  2. Technical walkthrough

    A working demo against a scenario that resembles your plant, not a generic tour.

  3. Pilot plan

    A defined first line or site, with the deployment and security questions answered up front.

  4. Roll-out

    The same templates bring the next lines and sites online.