Reuse operational best practices
Wodby-maintained services package runtime configuration, deployment behavior, and service connections into reusable building blocks. Your agent configures them for your app instead of reinventing each component.
Agentic DevOps
DevOps for your coding agent.
Bring the agent you already use. Wodby gives it the tools and workflow guidance to deploy and operate your applications, not just write their code.
Use Wodby Cloud or your own infrastructure.
Your agent. A shared operations platform.
- 1
Your coding agent
Work in the agent or harness you already use.
- 2
Wodby tools + skills
MCP connects the tools. Skills guide the workflow.
- 3
Your applications
Stacks, deployments, environments, and task logs.
AI power. Less infrastructure slop.
Built to be maintained, not just generated.
Let your agent solve the application problem. Build on Wodby’s standardized services and workflows instead of leaving your team with a pile of generated deployment scripts to maintain.
Standardize the workflow
Agents use Wodby’s deployment operations and workflow skills, with task history and logs your team can inspect. The process stays on the platform after the agent’s session ends.
Keep receiving maintained updates
Wodby maintains its catalog services beyond the first deployment. Automatic stack updates can bring in newer service revisions according to your update policy, without asking an agent to regenerate the setup.
You control rollout: running environments upgrade automatically only when auto-upgrade is enabled for them. Review changes in staging before promoting them to production. Your application code and custom services remain your responsibility.
How automatic updates workFrom repository to running application
Start with a concrete job.
Bring an existing application
Have your agent inspect the repository, identify services and dependencies, and map them to a Wodby stack. Surface data, configuration, and access gaps before creating resources.
A migration plan you can review, not an automatic production move.
Deploy a staging copy
After reviewing the plan, authorize your agent to configure the target application and deploy staging. Follow deployment tasks, then check runtime health and application behavior.
A staging environment to validate before a separate production cutover.
Investigate a failing app
Ask your agent to inspect task logs and runtime state, read recent application logs, or briefly watch a selected container. Use the evidence to narrow down what failed.
A diagnosis and proposed next steps. Authorize fixes separately.
Start with your agent
DevOps with Codex
Use Codex with Wodby to assess an existing repository, plan its migration, and deploy a staging copy using managed application stacks.
Follow the walkthrough →DevOps with Claude CodeConnect Claude Code to Wodby to investigate failed deployments, correlate task and application logs with your repository, and review a fix before deploying it.
Follow the walkthrough →More than a tool connection
Give your agent a platform to work with.
Your agent decides how to approach the task. Wodby supplies application context, reusable stacks, and deployment operations.
Build on managed stacks
Reuse service definitions and application stacks instead of starting every deployment from raw infrastructure.
Explore application stacks →Guide the whole workflow
Wodby skills help agents discover resources, plan migrations, follow tasks, and troubleshoot with relevant evidence.
Explore workflow skills →Keep your infrastructure choice
Run applications on Wodby Cloud, a supported managed Kubernetes provider, or self-hosted Kubernetes.
Compare hosting options →You choose the access. You authorize the changes.
- Start with read access and choose the organization and permissions your agent needs.
- Review the target environment and costs before granting permissions to make changes.
- Follow task status and logs to inspect what happened, not just the agent’s summary.
- Keep production data, DNS changes, and cutover as separately authorized steps. Access to your current hosting must be arranged separately.
Instructions guide the agent; token permissions limit what it can do through Wodby. Only grant access you intend it to use.
Review access and safety boundaries →Try it with your own repository
Ask for a plan first.
Connect an agent, open your application repository, and start with this read-only request.
Migration planning prompt
Use Wodby’s wodby2-migrate guidance to inspect this repository and plan its migration to Wodby. Identify required services, configuration changes, data transfer, likely downtime, and blockers. Do not create resources, connect to my current hosting, or change anything.Connection guidance for Codex, Claude Code, OpenCode, Hermes, Grok Bot. Other compatible MCP clients can use the same endpoint.