Self-hosting
Run Sieve in your own environment with Sieve Vault, and evaluate the Vault bundle before a full install.
Sieve can run entirely inside your own cloud account or data centre as Sieve Vault. Vault serves the same System One and /v1/decisions API as the hosted service, makes no outbound calls, and keeps your content, logs and metrics in your environment.
How it is delivered
Everything ships as signed container images with a Helm chart, a software bill of materials, checksums and an offline licence file. There is no hosted control plane to connect to and no Terraform. The Vault install guide covers the bundle, prerequisites, installation and licence renewal step by step.
Evaluate before installing
Before a cluster install, we can provide an evaluation setup that checks your container environment and licence without GPUs and without internet access. It answers the same API with fixed, non-meaningful probabilities, so you can test your integration, networking and authentication. Ask for it through an Enterprise & sales ticket on the console's Support page or at support@sthanika.ai.
Calling a self-hosted gateway
Your code changes only the base URL: point TYPESAFE_BASE_URL (or the SDK's base_url / baseURL) at your Vault endpoint. Authentication uses the method your installation is configured for: API keys, your identity provider (OIDC) or mutual TLS. Put Vault behind your own TLS-terminating load balancer.
The interactive Try it in the API reference can call a gateway on your own machine (localhost, 127.0.0.1 or [::1]), for example through a port-forward, so you can test a Vault installation from these docs.
Operations
- Containers run as non-root with a read-only filesystem, all Linux capabilities dropped and no privilege escalation.
- Vault exposes health checks and Prometheus metrics for your monitoring.
- Assurance reports run inside your cluster.
- Upgrades, support and calibration checks are agreed in your Vault contract.
Next steps
Last updated