Orchestration & Deployments

Map your contracts to your clusters.

Track which version runs for which customer, on which cloud. Kaiten doesn't replace your GitOps — it gives it a brain that understands the business.

Get StartedRead the Docs

Your deployment pipeline is contract-blind.

ArgoCD deploys. Flux syncs. GitHub Actions runs. But none of them know which customer is on which plan, or which version they're entitled to.

What Sales knows

Acme Corp

Enterprise Plan

Zone: EU-West

What DevOps sees

k8s-eu-west-1

namespace: acme

version: ???

What actually runs

??? v1.9 or v2.1

entitlements: ???

license: ???

With Kaiten: one source of truth for all three.

Your infrastructure, orchestrated by the business.

Deployment Zones

Map your topology.

Define the logical environments where your customer instances run — cloud regions, private VPCs, on-premise clusters, or any logical grouping.

Instance Management

Every customer deployment, accounted for.

An instance binds customer, license, deployment zone, platform metadata, and license dates into a single tracked entity with a full lifecycle.

Component & Release Tracking

Know exactly what's running, everywhere.

Model your delivery chain with components and releases. Deploy releases to zones and know exactly which version of which service runs for which customer.

GitOps Integration Loop

We don't replace your pipelines. We orchestrate them.

Webhooks fire to your CI/CD on business events. Your pipeline deploys. The CLI pushes state back. The loop is closed. The Console reflects reality.

Event-Driven Automation

27 events. Infinite automations.

Every state change emits a typed webhook event via the transactional outbox pattern. Guaranteed at-least-once delivery. Trigger any downstream system.

The GitOps integration loop.

kaiten CLI
# Step 1: Kaiten fires a webhook on business events
# → Your CI/CD provisions namespace, deploys release

# Step 2: Your pipeline pushes state back
$ kaiten instances push-state \
    --tenant-id="acme-corp" \
    --instance-slug="acme-production" \
    --release-version="v2.4.1" \
    --status="deployed"

# ✓ Loop closed. Console shows reality.

Two models. Same control plane.

The same Kaiten API manages both models. Your SDKs, Console, and automation logic are identical.

Kaiten Cloud (Multi-tenant)

Standard B2B SaaS with shared infrastructure

  • •Instances are logical — shared infrastructure, differentiated by tenant_id
  • •Rapid time-to-market, managed by us
  • •Standard compliance (SOC 2, GDPR)

Kaiten Standalone (Dedicated)

Enterprise SaaS with isolated deployments

  • •Instances are physical — dedicated VPCs, isolated clusters
  • •Highly regulated industries (Healthcare, Defense, Finance)
  • •Air-gapped or on-premise deployments