Skip to main content
Checked on Izumi 0.5.7, 2026-11-21 (from the code, nothing run). Izumi has no telemetry, no update check and no call to any Akia service. Documents, text chunks, vectors, access records, keys and backups stay on the server. This page lists the only outside calls and how to set a server up without internet.
Not checked live yet: setting up a server without internet (docker save, docker load, transferring the model) was not done in this check. The procedure and the list of images come from the install guide and the code. The table of hosts comes from the guide and the code (the egress test ran on 2026-11-18 on release 0.4.15, for the CIMD hosts only, and was not repeated on 0.5.7).

What leaves the server

Only this, and most rows only when you set them up:

A server without internet

Prepare the model and the images on a machine with internet and the same CPU architecture as the server (amd64 keeps the model as safetensors, arm64 as ONNX: a volume filled on the other architecture does not start).
1

On a machine with internet: build the image and fill the model

Build the image and run the install once until /readyz is 200 (the embedder has then downloaded the model). Then export the images and the model volume:
2

Transfer the files

Copy the install directory (without .env and backups/), tb-images.tar.gz and tb-models.tar.gz to the server.
3

On the server, before the first start

On an arm64 machine cpu-arm64-1.9.4 goes instead of cpu-1.9.4.docker compose may warn that the volume was not created by Compose: it uses it anyway.
4

Continue with the install

Go to Install from the .env file. The embedder starts from the local snapshot. The first admin (First sign-in and admin) runs inside the image and needs no internet.
  • For the monthly restore check (Backup and restore) keep the docker tag line: the script then uses the loaded image of the release instead of building a new one, and the loaded Node image runs its helper containers.
  • Sign-in, connectors and TLS from a public certificate authority need their hosts from the table. Without them nobody can sign in to the web app (the page says sign-in is not set up): what remains are the operator commands, the upload and personal tokens (./tb admin token create) for MCP and the API, and TLS behind your own proxy with your own certificate.

Limits

  • Without the Google or Microsoft hosts there is no sign-in with those accounts and no connectors for Drive and SharePoint.
  • Without claude.ai and chatgpt.com CIMD does not work: turn on DCR or pre-register a client, see OAuth.
  • The embedder for a model change on such a server is filled the same way.

Troubleshooting