VegaDūtaPlatform · Self-hosting
Source-available, and yours to run
VegaDūta is published under the Business Source License 1.1: free to run, fork and build on - including for production use - with the single restriction that you cannot offer it as a competing hosted service. Each version converts to Apache-2.0 four years after release.
Self-hosting means your conversations, documents, and credentials stay on infrastructure you control. Install from a signed release artifact - not a source build - unless you choose to build from source yourself.
By the VegaDūta team · Last updated
In short
- VegaDūta is source-available under the Business Source License 1.1 - free to run, fork and build on, including commercially; every version converts to Apache-2.0 four years after release.
- Self-host paths are first-class release artifacts: desktop installers (macOS .dmg, Windows, Linux), the Docker Compose stack, and a Helm chart published as a signed OCI chart on GHCR.
- Every release artifact is pinned, checksummed (SHA256SUMS), cosign-signed and ships an SBOM.
Three supported install paths
Desktop installers for macOS (.dmg), Windows and Linux set up a personal install - one person, local sign-in, a bundled local model. The Docker Compose stack brings up the platform's services together, including the core API, the web console, the knowledge sidecar that handles document extraction and embeddings, Postgres, Valkey, and Keycloak for sign-in. The Helm chart is published as a signed OCI artifact on GHCR for Kubernetes.
Verified artifacts, not source builds
Every release pins its container images to the release tag on GHCR, ships SHA256SUMS and a sigstore bundle, signs the images and the chart with cosign, and includes SBOMs. You can verify what you are running before you run it.
Models: your keys or your hardware
A self-hosted install uses the same bring-your-own-key providers as the hosted service. One of them is Ollama, which points the platform at models running on your own hardware, so an install can work without sending prompts to a hosted model API.
What is not supported yet
The Terraform modules under infra/ are drafts and should not be treated as a supported deployment path. An optional Temporal-based workflow engine is in the code and is off by default.
Frequently asked questions
Is VegaDūta open source?
VegaDūta is source-available under the Business Source License 1.1: free to run and modify, including commercially, except for offering it as a competing hosted service. Each version automatically converts to Apache-2.0 four years after release.
How do I self-host VegaDūta?
Use a signed release artifact: the desktop installer for a personal install, Docker Compose for a server (./scripts/vegaduta up), or the Helm chart published on GHCR for Kubernetes.
Can I run VegaDūta on Kubernetes?
Yes. The Helm chart is published as a signed OCI artifact on GHCR at oci://ghcr.io/cd-lc/charts/vegaduta, alongside the platform images.
Can a self-hosted install use local models?
Yes. The Ollama connector points the platform at a model server on your own hardware, alongside the other bring-your-own-key providers.
Sources
See it working in two minutes
The sandbox provisions a real tenant — describe an agent in one sentence and test it, no account, no card. Or browse ~90 industry workflow recipes to see what teams build.
