Docs · Offline
Offline that is verifiable, not asserted
Cogeto runs fully inside a customer network with no outbound connectivity at all. This is a supported first class deployment, not a degraded mode, and the architecture makes it checkable.
What runs inside the boundary
- Language models and embeddings run in a local runtime on your hardware; a vision model in the same runtime reads scans that character recognition cannot handle.
- Page recognition runs on CPU inside the instance, with English and Croatian language packs.
- Web style search for the research path is self hosted inside the instance.
- Storage, identity, and the queue are the same stack as every other deployment. There is no telemetry.
Why you can verify it
Every model call passes through a single egress seam, enforced in continuous integration: there is exactly one place in the codebase where a call could leave the instance, and in the offline configuration it points at the local runtime. The code is open source, so your security team can confirm this rather than trust it.
Air gapped installs
For environments where even image pulls are unavailable, the instance ships as an offline image bundle, so installation happens from media you carry across the boundary. Offline deployments are planned together in the pilot conversation: sizing for the local model runtime, the bundle handover, and the update procedure for your environment.
Know the measured quality before you commit
Local and hosted model configurations are measured separately, and every configuration's scores are published per release. The administration page shows the measured quality of the configuration you run and flags untested combinations.
Plan the offline install with us.
Air gaps are a normal conversation here. The pilot can run entirely inside your network.