Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.monk.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Deploy to AWS

deploy this to AWS
Monk will ask for region preference and AWS credentials (if not already configured). With specific region: 
deploy to AWS in us-east-1
With managed database: 
deploy to AWS with RDS for PostgreSQL
With MongoDB: 
deploy to AWS with DocumentDB for MongoDB
→ AWS Integrations for all AWS services

​
Deploy to Google Cloud

deploy to GCP
With region: 
deploy to GCP in europe
With Cloud SQL: 
use Cloud SQL for PostgreSQL
With Firebase Hosting: 
deploy frontend to Firebase
→ GCP Integration for all GCP services

​
Deploy to Microsoft Azure

deploy this to Azure
With region: 
deploy to Azure in westus2
With Cosmos DB (MongoDB API): 
use Azure Cosmos DB with MongoDB API
With Azure Database: 
use Azure Database for PostgreSQL

​
Deploy to DigitalOcean

deploy to DigitalOcean
With region: 
deploy to DigitalOcean in nyc1
With DO Managed MongoDB: 
use DigitalOcean managed MongoDB
With DO Spaces: 
use DigitalOcean Spaces for object storage
→ DigitalOcean Integrations for all DO services

​
Deploy to Hetzner

deploy to Hetzner
With region: 
deploy to Hetzner in eu-central
With specific instance type: 
deploy to Hetzner on cx22 instances

​
Hybrid Deployments

Mix cloud providers for optimal placement: 
deploy frontend to Netlify, backend to AWS, database on Atlas
Monk handles cross-cloud networking and configuration automatically. Example scenarios: Serverless frontend + containerized backend: 
deploy React app to Vercel, API to DigitalOcean
Multi-cloud for redundancy: 
deploy primary to AWS, failover to GCP
Cost-optimized stack: 
deploy compute to DigitalOcean, database to Atlas, CDN to Cloudflare

​
Compare Costs Across Clouds

Before deciding, ask Monk to compare: 
how much would this cost on AWS vs GCP vs Azure?
Monk shows:
  • Cost breakdown per provider
  • Monthly estimates
  • Differences in pricing
  • Which is most cost-effective
which cloud is cheapest for this deployment?

compare DigitalOcean vs AWS for my API

​
Regional Deployments

​
Deploy to Specific Regions

deploy to AWS in us-east-1

deploy to GCP in asia-southeast1

deploy to Azure in westeurope

deploy to DigitalOcean in sfo3

​
Ask for Region Recommendations

Not sure which region to use? 
which AWS region is cheapest for my app?

which GCP region is closest to Europe?

recommend an Azure region for US users
Monk considers:
  • Latency to your users
  • Cost differences between regions
  • Service availability
  • Compliance requirements

​
Multi-Region Deployments

Deploy to multiple regions simultaneously: 
deploy to AWS us-east-1 and eu-west-1

deploy to GCP in US and Europe
Monk automatically:
  • Provisions infrastructure in each region
  • Sets up load balancing across regions
  • Configures geo-routing (if applicable)
  • Manages cross-region connectivity

​
What Monk Manages Per Cloud

​
AWS

Infrastructure:
  • EC2 instances for containers
  • VPC and networking
  • Security groups
  • Load balancers (ALB/NLB)
Managed Services:
  • RDS (PostgreSQL, MySQL, MariaDB)
  • DocumentDB (MongoDB-compatible)
  • ElastiCache (Redis)
  • S3 (object storage)
  • Lambda (serverless functions)
  • DynamoDB, SQS, SNS, and more
Ask Monk: 
use AWS Lambda for my API

​
Google Cloud Platform

Infrastructure:
  • Compute Engine VMs
  • VPC networking
  • Firewall rules
  • Load balancers
Managed Services:
  • Cloud SQL (PostgreSQL, MySQL)
  • Firestore (NoSQL)
  • Memorystore (Redis)
  • Cloud Storage (object storage)
  • Cloud Functions (serverless)
  • BigQuery, Pub/Sub, and more
Ask Monk: 
use GCP Cloud Storage for uploads

​
Microsoft Azure

Infrastructure:
  • Virtual Machines
  • Virtual Networks
  • Network Security Groups
  • Load Balancers
Managed Services:
  • Azure Database (PostgreSQL, MySQL)
  • Cosmos DB (MongoDB API, multi-model)
  • Azure Cache (Redis)
  • Blob Storage (object storage)
  • Azure Functions (serverless)
  • Event Hubs, Service Bus, and more
Ask Monk: 
use Azure Blob Storage for files

​
DigitalOcean

Infrastructure:
  • Droplets (VMs)
  • VPC networking
  • Firewalls
  • Load Balancers
Managed Services:
  • Managed Databases (PostgreSQL, MySQL, MongoDB, Redis/Valkey)
  • Spaces (object storage, S3-compatible)
  • App Platform (PaaS)
  • Container Registry
  • Monitoring
Ask Monk: 
use DigitalOcean App Platform for my frontend

​
Switching Clouds

Already deployed to one cloud? Migrate to another: 
migrate this deployment from AWS to GCP
Monk handles:
  1. Provisions equivalent infrastructure on target cloud
  2. Updates all configuration and networking
  3. Guides you through data migration (databases)
  4. Verifies everything works before teardown
move from DigitalOcean to Azure

migrate database from AWS RDS to MongoDB Atlas

​
Cloud-Specific Considerations

​
When to Use AWS

Best for:
  • Enterprise deployments
  • Need for extensive managed services
  • Existing AWS infrastructure
  • Lambda/serverless requirements

​
When to Use GCP

Best for:
  • Data analytics and BigQuery
  • Kubernetes-native deployments
  • Machine learning workloads
  • Firestore/Firebase integration

​
When to Use Azure

Best for:
  • Microsoft stack (.NET applications)
  • Enterprise with existing Azure
  • Cosmos DB global distribution
  • Azure AD integration

​
When to Use DigitalOcean

Best for:
  • Simpler deployments
  • Startups and SMBs
  • Cost-conscious projects
  • Quick setup without complexity

​
Ask Monk for Recommendations

which cloud should I use for my project?

recommend a cloud provider for a Node.js API with PostgreSQL
Monk considers your specific needs and recommends appropriately.

​
Getting Cloud Credentials

Each cloud provider requires different credentials. Monk will request these automatically when you deploy. Need help getting credentials? → See Obtaining Credentials for step-by-step guides for all providers:

​
Multi-Cloud Best Practices

​
Start Simple

Begin with one cloud provider: 
deploy to DigitalOcean
Add additional clouds as needed: 
also deploy to AWS for redundancy

​
Use Managed Services Where Available

Let cloud providers handle complexity: 
use GCP Cloud SQL instead of self-hosted PostgreSQL

use AWS RDS instead of container database

​
Co-locate Resources

For best performance and lowest cost, keep related services in the same cloud/region: Good: 
deploy API to AWS us-east-1 with RDS database in us-east-1
Less optimal: 
deploy API to AWS, database on GCP
(Cross-cloud latency and data transfer costs)

​
Consider Data Transfer Costs

Moving data between clouds is expensive. Ask Monk: 
how much would data transfer cost between AWS and GCP?