Skip to main content

​
Before You Start

Make sure you have:
  • ✅ Monk installed in your IDE (Installation)
  • ✅ A project open in your IDE
  • ✅ Cloud provider account (AWS, GCP, Azure, or DigitalOcean)
Need credentials? See Obtaining Credentials for step-by-step guides on getting API keys and access tokens for cloud providers and services.

​
Step 1: Open Your Project

Open any project folder in your IDE. Monk works with:
  • Any programming language
  • Any framework
  • Existing apps or new projects
  • Monorepos or single services

​
Step 2: Deploy

Open the Monk chat window and type: 
deploy this project
That’s it. No configuration files, no setup scripts.
Prefer to work through Claude Code, Gemini, Codex, or another coding agent? First run Monk: Manage MCP Server in your IDE and enable Monk MCP for the current workspace. Then your coding agent can call Monk for deployment and operations tasks directly from the same project context.

​
Step 3: Answer Questions

Monk will ask for information it needs: Cloud Provider: 
Monk: Which cloud provider would you like to use?
      - AWS
      - GCP
      - Azure
      - DigitalOcean

You: AWS
Region: 
Monk: Which region?

You: us-east-1
Credentials (Secure Prompt): 
Monk: I need AWS credentials to provision infrastructure.
      [Secure input fields appear]

You: [Provide AWS access key and secret key]
Credencial Form → How to get AWS credentials Service Choices: 
Monk: Your app needs PostgreSQL. How would you like to deploy it?
      - Self-hosted (container)
      - AWS RDS (managed)
      - Neon (serverless)

You: AWS RDS

​
What’s Happening

While you wait (5-15 minutes), Monk:
  1. Analyzes your code - Understands your application structure
  2. Creates containers - Builds Docker containers automatically
  3. Provisions infrastructure - Creates VMs, databases, networking
  4. Deploys everything - Gets your application running
  5. Wires it together - Connects services, databases, APIs
You’ll see progress updates in the chat window.

​
Deployment Complete

When finished, Monk shows:
  • URLs - Where your application is running
  • Status - Health of all services
  • Cost - Estimated monthly cost
Your application is live!

​
Try It Out

Test your deployed application: Check status: 
what's running right now?
View logs: 
show me the logs
Check cost: 
how much am I spending?

​
Common First Deployment Scenarios

Web app (React + Node.js):
  • Frontend deployed to Netlify
  • Backend containerized on cloud VMs
  • Database on managed service (RDS)
  • Everything wired together automatically
Monk deployment using Netlify API service (Python/FastAPI):
  • API containerized and deployed
  • PostgreSQL database provisioned
  • Load balancer configured
  • HTTPS enabled
App with MongoDB:
  • Self-hosted or managed MongoDB
  • Application automatically wired to database
  • Credentials generated and injected
→ See MongoDB Deployment Guide for MongoDB options Monorepo (Multiple services):
  • Each service analyzed independently
  • Deployed to optimal targets
  • All services connected securely

​
Troubleshooting

Monk asks too many questions?
  • Be more specific: deploy to AWS us-east-1 with RDS for PostgreSQL
Deployment failed?
  • Check credentials are correct (verify credentials guide)
  • Ensure you have permissions in cloud account
  • Ask Monk: what went wrong?
Missing Integration? Monk will send information about missing integrations to our ticketing tool. It Enhance a product focus without user extra friction.
Want to see the plan first?
  • Use: analyze this project to see what Monk found
  • Use: show me the configuration before deploying

​
Next Steps

Now that you’ve deployed: → Autonomous Operations - Learn how Monk works autonomously → Obtaining Credentials - Add more cloud providers or services → Prompting Guide - Learn to prompt effectively → Features - Explore what Monk can do