You bring code
Push a repo, clone one, or import an image. Your agent can hand it over too — with one scoped token.
Bring code — yours or your agent's — and Opsting builds, deploys, and keeps it running on your own k3s cluster. It even hosts the apps that extend what your agents can do. No SaaS. No lock-in.
$ ./opsting-install ✓ k3s · registry · gitea · control plane $ git push opsting main → buildkit image ok → scan 0 CVE → deploy hardened ✓ nova ~ live at notes.local
Push a repo, clone one, or import an image. Your agent can hand it over too — with one scoped token.
BuildKit images, generated manifests, lint, CVE scan, and deploy gating — the boring 80%, owned.
Signed event webhooks and Nova, the ops assistant, watch builds and crashes so you — or an agent — can act.
Laptop, homelab, or a tucked-away cloud VM. One installer, no SaaS dependency, no control plane you don't own.
Claude Code or opencode in your cluster — or bring your own with one scoped token and portable Agent Skills.
Pick Fast for iteration or Hardened for production. Routing, manifests, and gating handled either way.
Builds, crashes, CVE holds — every payload HMAC-signed so an agent can trust it before it reacts.
Anything an agent builds — even the tools and MCP servers it then uses — is just another app. Capabilities grow without touching platform code.
The in-platform ops assistant reads crashes and walks you through fixes, driving the same surface your external agents use.
Add your own provider key when you want the assistant, code review, and build summaries.
Three commands. Runs on hardware you control.
curl -Lo opsting-install https://tryatelier.blob.core.windows.net/tryatelier/latest/opsting-install chmod +x opsting-install ./opsting-install