How it works - Managed cloud, self-hosted, or air-gapped — same product, your call

One stack, three deployments

Laminae ships as several Docker Compose files. The managed cloud runs those files, per tenant, on Hetzner. Self-hosted are the same files on your own infrastructure. Air-gapped are the same files again, with bundled Ollama replacing the cloud model endpoints. There’s no separate edition for any of them — the code path is identical.

That matters because it means the “cheap” option isn’t the experimental one. Self-host is a first-class citizen. Your compliance team can audit the same artefact we run, and your ops team can roll back to a known-good backup without coordinating with us.

Managed cloud

We provision a per-tenant project on Hetzner. No shared infrastructure between customers, no noisy-neighbour story to keep track of. EU hosting by default. Encryption at rest, with BYOK on request for tenants whose security team requires it, or behind the company VPN for those who need it.

Model calls go out to the AI provider you choose — OpenAI, Anthropic, or an open-source endpoint we run for you. The cloud version is the right call for teams that want the product without taking on the operational work of running it.

Self-hosted

The same Compose file, on your hardware. You get the same stack, configured with your own secrets and your own keys. Update cadence is your call — we ship versioned images and release notes, and you pin to whatever version your change board has approved.

Air-gapped

Same Compose file again. Cloud model endpoints are replaced with bundled Ollama running locally. Nothing leaves your network — not embeddings, not queries, not telemetry. This is the right deployment when your data residency requirements are absolute, or when the network you’re serving has no egress at all.

What you get