Skip to main content
This is where the loop closes. Your coding agent builds the app, Monk deploys it to your cloud, and from that point on the software runs autonomously. You describe what you want, and the agents handle the rest.

​
Before You Start

1

Monk installed

If not, follow Install Monk.
2

Agent connected

The plugin connects your coding agent to Monk over MCP automatically during install — there is no separate connection step. If you’re unsure, run /monk check installation status.
3

Cloud credentials (optional)

If you want to deploy to the cloud (recommended), have your cloud provider credentials ready. See Obtaining Credentials for AWS, GCP, Azure, or DigitalOcean setup.Want to try Monk locally first? Skip this step — Monk can deploy to your local machine too.

​
Deploy

Open your project in your coding agent. Optionally, start by getting the lay of the land:
Monk analyzes the code and returns a summary with an architecture diagram of your app. Then deploy:
That’s it. No configuration files, no Dockerfiles, no Terraform. This works on existing codebases too — even if your project already has a docker-compose file, IaC definitions, or other deployment configuration. Monk uses these to orient itself but does not modify them. Your existing deployment stays working until you are ready to make the switch. Don’t have an app handy? Ask your coding agent to build one and deploy it in a single prompt:
Deploying to your cloud account will incur cloud provider costs. These vary depending on what you are deploying. Monk always asks for confirmation before creating cloud infrastructure on your behalf. Start with smaller VMs when trying things out — you can always scale up later.
If you want more control upfront, be specific:
More detail means fewer questions. Either way works.

​
What Happens Next

The deployment is a short guided flow. You review and approve; the agents do the work.
1

Pick a team

Monk asks which team the project belongs to — Personal, or one of your organizations.
2

Enter credentials in the local Monk dashboard

A browser window opens the local Monk dashboard with a form for your cloud API key and any database or service secrets. Credentials go straight into the form — they are never pasted into chat and never exposed to the agents.
3

Confirm the configuration

Back in your coding agent, Monk prepares the deployment configuration and asks you to confirm the credentials are in place.
4

Approve the infrastructure

The dashboard opens once more showing the virtual machines Monk wants to create. Inspect and approve.
5

Deployment runs autonomously

Monk builds containers, provisions the infrastructure, deploys everything, and wires services together. Because Monk can see the running app, it detects and fixes issues on its own — API routing problems, for example.
A typical first deployment takes five to fifteen minutes. You will see progress updates in your agent’s chat, and when it finishes Monk hands you a live HTTPS link to your app in production. Credential form in the local Monk dashboard

​
You Are Live

When deployment finishes, Monk reports live URLs, service health, and estimated monthly cost. Your application is running on your cloud. Try:

Autonomous operations

Your app is deployed — now learn how Monk keeps it running, sets up CI/CD, and monitors your services

​
Tips

If Monk asks too many questions, put more detail in your prompt. If you want to preview the plan before committing:
If a deployment fails:
Credential issues are the most common cause — double-check them in Obtaining Credentials.

​
Cleaning Up

Done trying things out?
This stops and removes all cloud infrastructure Monk created, so you do not incur costs while idle. Nothing is lost — you can always deploy again later and Monk will bring it all back.

​
Troubleshooting

Troubleshooting

Common issues and how to fix them