# Clanker DevOps

Clanker DevOps is a provider-agnostic workspace for DevOps and infrastructure work.

Use it for incidents, deploys, cost review, security checks, Kubernetes operations, GitHub context, MCP agents, and reviewed changes.

## Before and after

Before Clanker DevOps, operators and agents jump between repos, terminals, dashboards, clusters, tickets, cost views, and account screens before they can form a useful answer.

After Clanker DevOps, the workflow starts by collecting live context, connects security and FinOps signals to the same operational view, and keeps apply, publish, delete, and account changes behind review.

## Product surfaces

![Scan infrastructure in Clanker DevOps](https://clankercloud.ai/scan-your-infra.png)

![Investigate cloud cost in Clanker DevOps](https://clankercloud.ai/cost-explorer-1.png)

![Start a security scan in Clanker DevOps](https://clankercloud.ai/start-scanning-your-infra.png)

![Use Kubernetes context in Clanker DevOps](https://clankercloud.ai/kubernetes-support.png)

## Question to action

Clanker DevOps follows a simple operator loop:

1. Ask a grounded infrastructure question.
2. Inspect live context before answering.
3. Generate a safe plan before changes.
4. Apply only when maker mode is intentional and the plan is reviewed.

Relevant screenshots:

![Talk to infrastructure in Clanker DevOps](https://clankercloud.ai/talk-to-your-infra.png)

![Inspect topology in Clanker DevOps](https://clankercloud.ai/2d-view.png)

![Plan agent work in Clanker DevOps](https://clankercloud.ai/plan-agent.png)

![Explicit deploy action in Clanker DevOps](https://clankercloud.ai/one-click-deploy.png)

## Interactive DevOps example

The Clanker DevOps page includes an interactive example for real infrastructure work. Visitors can click scenarios, inspect topology, ask operational questions, and see how the workspace keeps cloud resources, repos, topology, logs, and reviewed plans in one place.

## Workflow examples

The page also includes a show/hide "Show workflow examples" section with seven common DevOps workflows:

1. Ideas / Ticketing: capture requests and requirements.
2. Repo / Build: code, build, and test changes.
3. CI / Test: automate quality and validation.
4. Deploy / Release: ship with confidence and control.
5. Observe / Logs / Traces / Cost: unify operational and cost signals.
6. Incident / Debug / Rollback: respond fast and recover with confidence.
7. Automate / Optimize: turn repeated work into safe automations.

## Trust boundary

- Credentials stay on the user's machine.
- Teams can bring their own model keys.
- Agents can manage Clanker Cloud workflows through the local boundary.
- Read-only investigation comes before reviewed changes.

## Videos

- [Workspace walkthrough](https://clankercloud.ai/videos/clanker-cloud-lp-home.mp4)
- [FinOps cost investigation](https://clankercloud.ai/videos/clanker%20cloud%20new%20finops.mp4)
- [Deep infrastructure research](https://clankercloud.ai/videos/deep-research-short.mp4)

## What it does

- Investigates incidents with live infrastructure, repo, deploy, and runtime context.
- Plans deploys with runtime, secrets, domains, cost, and rollback context.
- Explains cloud cost movement before suggesting optimization.
- Reviews exposure and risky settings before remediation.
- Gives MCP-capable agents live context through Clanker Cloud instead of pasted credentials.
- Keeps apply, delete, publish, and account changes behind review.

## Typical loop

1. Connect the context your team already trusts.
2. Ask the operational question.
3. Review the evidence and gaps.
4. Generate a plan when action is needed.
5. Approve high-impact steps explicitly.

Related:

- [Workspace](https://clankercloud.ai/workspace)
- [MCP setup](https://clankercloud.ai/mcp)
- [Cloud for Agents](https://clankercloud.ai/cloud-for-agents)
- [Security model](https://clankercloud.ai/security)
- [FinOps workflow example](https://clankercloud.ai/examples/find-aws-cost-spike)
- [Local credential boundary](https://clankercloud.ai/security/local-credentials)