Deployment
Runs where your data lives
Self-hosted: one binary and one database file, with Docker and Kubernetes assets. You choose the model providers and the hosts it may reach.
Self-hosted
One binary. One database file.
There is no fleet of services to run. OrchKernel is one binary and one database file.
01
Docker
An image and a Compose file for a single server.
02
Kubernetes
Manifests for running it in your own cluster.
docker compose
# Configure, create the first admin, then start.
$ cp .env.example .env
$ docker compose run --rm orchkernel init --admin root
$ docker compose run --rm orchkernel --as root token issue --for root
$ docker compose up -d
Your data
Runs where your data lives
Your servers, your model providers, your allowed hosts.
01
Your model providers
You choose them. Each model is cleared for a data class, so restricted data reaches only models cleared for it.
Models and data02
Sealed secrets
Connection secrets are sealed at rest. Agents never hold your vendor keys.
03
Checked egress
Every outbound request is checked against the hosts you allow.
04
A kernel per tenant
Multi-tenant hosting, with a separate kernel for each tenant.
Tenancy and the licenseFrequently Asked Questions
Put an agent on real work, with people in charge
Design partners run one real workflow on OrchKernel and work directly with the engineers building it.
OrchKernel is source-available and self-hosted.