Self-Hosted Deployment

The platform ships as a Docker Compose stack you run on your own infrastructure — same product as cloud, on servers you control. This page covers what a self-hosted deployment needs and where it differs from cloud. Installation and setup are handled with our team directly — use the button above to get started.

Requirements

Resource	Minimum
CPU / RAM	2 cores / 4 GB
Disk	20 GB free
OS	Linux, Windows Server 2019+, or macOS
Docker	20.10+ with Compose v2+

The stack also needs outbound access to portal.provenmap.com (license/auth) and registry.hub.docker.com (image pulls).

Important

PostgreSQL is bring-your-own — the shipped compose file doesn't run it for you. Have a reachable instance (managed or self-run) ready before you start the stack.

Configuration essentials

AI features (Chat, in-app insight generation) run through a model provider, connected once from Settings → Connectors — identical to cloud. See the Integrations Reference. The plugin loop (/analyze, /sync, /insights) needs no model provider at all.

Note

Trial credits to fund early usage before you connect your own model provider are available on request — billed to you, not your users.

SSL, backups, and upgrades

Self-hosted deployments work with your existing reverse proxy and SSL termination, and pair with whatever backup strategy you already run against your PostgreSQL instance. Version upgrades and rollbacks are supported. We walk through the specifics together during setup.