Internal developer platform

Your agents ship.
You approve prod.

Kalzone builds, configures, deploys and watches container services. Every action is an API call and an MCP tool, so Claude can run the whole loop. Changes to prod wait for a human.

Claude Code: /plugin install kalzone@kalzone

› build hello and ship it

kalzone.requestRelease hello  wait: true
  ✓ r12  sha:4f1c9e2  digest pinned · 1m48s
kalzone.createDeployment hello → dev
  ✓ succeeded  blue-green · healthy
kalzone.promoteDeployment hello dev → prod
  ◷ change request 7c2e…
    waiting for approval at
    platform.kalz.one/requests/7c2e
kalzone.wait request 7c2e
  ✓ approved · prod live
builds

Releases you can trust

GitHub Actions builds the image, reports back over OIDC, and the release is pinned to its digest.

deploys

Blue-green by default

Deploy to dev, promote to prod, roll back to any earlier success. Drift is reconciled for you.

config

Config as revisions

Every change is a numbered revision. Secrets are encrypted, write-only and versioned with it.

queues

Managed queues

Ask for a queue and get delivery, retries and a dead-letter box you can replay.

observe

Grafana included

A dashboard per service, logs from Loki, health and restarts from the host.

audit

Who did what

Teams, roles and an audit log that shows "person via token" for every agent change.

Built for agents

A token does what its owner allows, and no more.

Tokens belong to a person and are cut down by scopes and teams. Errors carry a hint that says how to fix the call. Long work answers once it is final.

  • read
  • logs
  • builds
  • config
  • secrets
  • deploy
  • protected
  • bypass

An MCP tool for every operation at /mcp, the same calls as the REST API and its OpenAPI document. Bypass is granted only by a human admin, never by a token.

Connect Claude in two lines.

/plugin marketplace add klzn-labs/kalzone-skill /plugin install kalzone@kalzone

Then sign in at platform.kalz.one and create an access token for your agent.