Runs with the cable pulled
Install, upgrade, licensing and AI models ship offline. The machine can stay off the public network forever.
Private deployment is not the same as running offline.
The site has no public network
In finance, energy, manufacturing and government, production networks are often physically isolated. Installing a platform cannot start with a request for a dedicated line.
Diting ships packages, images, dependencies, licenses and AI models together. Upgrades work the same way: bring the bundle in, upgrade by the book, roll back if needed.
How offline delivery runs
Build the bundle
Generate an offline package for the target profile, with images, dependencies and license.
Bring it in
Move the bundle into the isolated network and verify signatures and digests.
Install
Install standalone, performance cluster or HA, with visible steps.
Upgrade
Import the upgrade bundle offline. Rollback stays available.
Intranet
- Packages and images
- License file
- Upgrade bundle
- AI models
Public network
Not involvedThe public network is not involved
After installation, the platform needs no connection to any vendor server. Cut the link, pull the cable, block the port: nothing changes.
- Offline license checks
- Local model loading
- Offline upgrade bundles
- No egress
Fits
- Physically isolated production networks
- Compliance regimes that forbid any egress
Doesn't fit
- Teams that want the platform to pull updates and models from a vendor cloud
Bring your system in
Tell us what you run: OS, kernel, public network or not, virtual machines or clusters. We will map the path in.