Public previewRAGSuite is open-source, self-hosted and EU-ready — and we build it in the open.See it live

Platform Platform overviewSee it in actionAI SearchAI AssistantAI Connectors & MCPIntegrationsQuality LoopAdministration & SecurityMobile app
Solutions IT & Platform teamsCompliance & Data ProtectionDevelopersAgencies & Partners
Sovereignty
References
Pricing
Resources Trust CenterEU AI ActSecurity & disclosureFree toolsOpen source & open coreDocumentation ↗API reference ↗GitHub ↗ReferencesBlogChangelog
Company AboutPartnersContact
Search See it live Book a demo
Sovereignty

No phone-home: how to verify an AI platform isn't calling out

"No phone-home" is a claim you can test, not just trust. How to verify a self-hosted AI platform makes no outbound connections — at the network layer.

SOVEREIGNTY outbound0 packetsno phone-home · verified ragsuite.de
Jürgen Pietschmann
Jürgen Pietschmann AI Consultant
Published14 June 2026 Updated25 June 2026 Read2 min Sovereignty

“No phone-home” means the software makes no outbound connections — no telemetry, no licence check-in, no usage beacon — and the right way to trust that claim is to verify it at the network layer, not to take it on faith. For a self-hosted platform, this is one of the few sovereignty properties you can prove yourself, directly, in an afternoon.

Why phone-home matters

Many “self-hosted” tools still call out: to validate a licence, to report usage, or to ship telemetry. Each outbound connection is a small breach of the sovereignty promise — a channel a Betriebsrat will ask about, an auditor will note, and an air-gapped environment will break on. A platform that phones home is not fully under your control, however it is hosted.

How to verify it — three levels

From quick check to proof

  • Network monitoring. Watch egress at the firewall or with a packet capture while you exercise the platform. A silent system shows no unexpected outbound traffic to the vendor.
  • Egress allow-listing. Deny outbound by default and permit only what you choose. If the platform still functions, it is not depending on a hidden call-home.
  • The air-gap test. Disconnect it entirely. If it still starts and serves answers — including unlocking paid capabilities — there is, by definition, nothing phoning home.

The third is the strongest proof: a system that runs air-gapped cannot be calling out, because there is nowhere for the call to go.

What makes “no phone-home” possible

The practical test: deny all egress, then confirm AI Search and the AI Assistant still answer over your own content. They do — because retrieval, generation (with local models via Ollama) and licensing all happen inside your network. For the broader picture, see What is sovereign enterprise AI? and the sovereignty page.

Frequently asked questions

Why does phone-home matter for compliance?

Each outbound connection is a channel a Betriebsrat will ask about, an auditor will note, and an air-gapped environment will break on. Removing it simplifies your DORA resilience and NIS2 supply-chain story, and reassures a works council that employee queries are not shipped to a third party.

Doesn't licensing require a server check?

Not with an offline key. RAGSuite validates a cryptographically signed token locally, so there is no licence server to contact and an air-gapped install simply works.

Sources & further reading

  1. RAGSuite — sovereignty (no phone-home, offline licensing) — how it's built
  2. What is sovereign enterprise AI? — the runtime-control test

← All posts