Air-Gapped Operation

Use the standard Docker export and import commands. No special tooling is needed.

On a machine that can reach Docker Hub, save the image to a file:

Transfer that file by whatever route your network allows, then load it on the inside:

Use a permanent tag rather than :latest, so you can still tell afterward which build you imported. To update the documentation later, repeat these steps with a newer image.

Use this section when your security team asks what the server does on the network.

While serving requests, the server makes no outbound network connections. The documentation, the search indexes, and the model it uses to match your questions are all inside the image, and every answer comes from the container’s own filesystem. The license check reads a local key file and contacts no license server.

Two things are switched off rather than missing, which is worth stating precisely:

Vaadin verifies this before publishing each image. The image is started in a sealed network namespace with no network route, and every one of its tools is called from inside that namespace. The test fails if anything in the server even tries to resolve a hostname. It also includes one outbound request that is expected to fail, which confirms the test environment really is isolated.

One environment variable controls usage reporting: AMPLITUDE_API_KEY. Leave it unset — the default — and the server reports nothing. A self-hosted deployment needs no configuration for this.

To confirm, check the startup log. It prints one of these lines:

The published image contains the reporting code but doesn’t use it. If your security review needs that code absent rather than switched off, request an image built without it.

The hosted server at mcp.vaadin.com does report usage — see What the Hosted Server Runs.