Discovery and import
Connect a cloud account or a Kubernetes cluster with read-only access. Overseer inventories what's there, you choose what to bring under management, and it lands in Git as code.
Closed alpha, onboarding teams now
Ask for infrastructure.
Ask for infrastructure.
Review it like code.
Overseer maps what already runs in your cloud, turns each request into a Git-backed changeset, and applies nothing until your team approves it. Then it keeps watching for drift.
Works with Google Cloud, AWS, Hetzner and Kubernetes.120+resource types
4cloud providers
Every changereviewed in Git
Live demo
From a question to a merged change
A recorded session in the product: discovering a Google Cloud project, deploying an app and working through an incident. Every change lands as a changeset that someone approves.
# gcp-discovery
Synced
What it does
The work Overseer takes off your plate
Changesets you can review
Every request becomes a changeset with a full plan, an estimated cost and a risk level. Merge it and Overseer applies exactly that.
Drift, explained
Overseer compares the cloud with what's in Git, shows which field moved, and proposes the fix as a changeset.
Kubernetes, live
Connect GKE, EKS or k3s clusters, manage Helm releases and manifests, and check pods, logs and node usage in place.
Secrets stay secret
Overseer generates a value or opens a masked prompt. Secrets go straight to Secret Manager or Vault and never pass through the chat.
Health and diagnosis
When something degrades, Overseer reads the logs and events, posts what it found in the resource's channel and prepares a fix for you to approve.
Built for teams
Ask in a shared channel and a teammate reviews and merges the change. Threads, direct messages and @mentions keep the discussion next to the infrastructure it's about, and everyone sees the same live status.
Channels with memory
Every environment and service gets its own channel with its history, open changesets and live status. Mention @overseer anywhere; it remembers your conventions and past decisions.
Everything on the record
Every request, plan, approval and merge is logged with who did it, so you can always trace how something got the way it is.
Overseer for developers and platform engineers
Ship your app without becoming a cloud expert
- Point Overseer at a repository and it works out what the app needs to run.
- Environment variables, secrets and dependencies are wired up for you, and you can see exactly how.
- CI is set up to build and deploy the app on every merge.
Keep the guardrails without becoming the bottleneck
- Every intent lives in Git, in a folder structure that mirrors your organization.
- A curated catalog decides what can be created and how it is configured.
- Teams ask for what they need; you set the rules and review what matters.
How it works
Nothing changes until you approve it
Ask
Describe what you need in a shared channel, the way you'd tell a colleague: a Postgres database for the billing service, or a staging copy of production.
Review the plan
Overseer works out the resources, checks them against your policies, estimates the cost and opens a changeset for your team to review. Nothing has changed yet.
Merge and stay in sync
Once a teammate merges it, the change is applied. From then on Overseer keeps the cloud matching what's in Git and tells everyone when it doesn't.
Why is checkout-api drifting? Record whatever is live if it is right.
- get_topology_summarykubernetes, prod-gke
- read_resourceproduction/checkout-api
- live_diff2 keys changed on the cluster
- plan_changeset#checkout-api
Two env vars were set on the cluster by hand. I recorded them in a changeset; merge it when it looks right.
Changeset
a41f9c02
planned
in #checkout-api
+ FEATURE_FLAGS_URL: https://flags.internal
+ CACHE_TTL_SECONDS: "300"
Google Cloud, AWS, Hetzner and Kubernetes, managed the same way
Google Cloud
AWS
Kubernetes
Hetzner
Closed alpha
Get early access
We're onboarding a few teams at a time. Leave your email and we'll reach out when there's room.