Host Pistis for several companies
Keep companies fully apart, and see what open source includes and what managed hosting adds.
Pistis never mixes two companies on one server. Each company gets its own complete setup, called a cell, and nothing is shared between cells.
One cell per company
A cell is everything one company uses: its Pistis servers, database, keys and sandbox machines. One Helm release or one compose stack is one cell. A company that hosts Pistis itself runs one cell. A managed service runs one cell per company.
What each company gets to itself
- Its own namespaces. A compromised server can't reach another company.
- Its own database. A separate Postgres instance, not a schema, so no shared tables or backups.
- Its own keys, from its own key in a key management service (KMS). One company's key opens nothing of another's.
- Its own sandbox machines, on its own node pool (
sandboxes.nodeSelector,sandboxes.tolerations) with gVisor or Kata. No kernel is shared. - Its own network. Sandboxes reach only their own cell and DNS.
- Its own domain, sign-in and admins.
Open source and managed
Everything to run a cell: Pistis, every sandbox provider, the web app, sign-in, the policy and audit, agents, MCP, your own machines, the Helm chart, the compose file and pistis doctor. Apache-2.0. Every security feature is here, and none is a paid extra.
A control plane that creates, upgrades, backs up and restores a cell per company, plus on-call, compliance reports and support. The control plane works through the cluster API, holds no company's keys and never sits in the path of a request.
Choose how to run it
- Strictest: host it yourself. Code, tokens and transcripts never leave your network.
- Managed, code at home: a managed cell with your own KMS key, running sessions on your own machines in your network.
- Managed: a cell with sandboxes on its own node pool. Simplest, and still nothing is shared.
Operators of a managed cell can reach its cluster.
Keys from your own KMS key and an audited emergency-access process limit what they can read. That is the security trade-off. Only hosting it yourself removes it.