Skip to main content

​
Deploy to AWS

Monk will ask for region preference and AWS credentials (if not already configured). With specific region:
With managed database:
With MongoDB:
→ AWS Integrations for all AWS services

​
Deploy to Google Cloud

With region:
With Cloud SQL:
With Firebase Hosting:
→ GCP Integration for all GCP services

​
Deploy to Microsoft Azure

With region:
With Cosmos DB (MongoDB API):
With Azure Database:

​
Deploy to DigitalOcean

With region:
With DO Managed MongoDB:
With DO Spaces:
→ DigitalOcean Integrations for all DO services

​
Deploy to Hetzner

With region:
With specific instance type:

​
Hybrid Deployments

Mix cloud providers for optimal placement:
Monk handles cross-cloud networking and configuration automatically. Example scenarios: Serverless frontend + containerized backend:
Multi-cloud for redundancy:
Cost-optimized stack:

​
Compare Costs Across Clouds

Before deciding, ask Monk to compare:
Monk shows:
  • Cost breakdown per provider
  • Monthly estimates
  • Differences in pricing
  • Which is most cost-effective

​
Regional Deployments

​
Deploy to Specific Regions

​
Ask for Region Recommendations

Not sure which region to use?
Monk considers:
  • Latency to your users
  • Cost differences between regions
  • Service availability
  • Compliance requirements

​
Multi-Region Deployments

Deploy to multiple regions simultaneously:
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:

​
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:

​
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:

​
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:

​
Switching Clouds

Already deployed to one cloud? Migrate to another:
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

​
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

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:
Add additional clouds as needed:

​
Use Managed Services Where Available

Let cloud providers handle complexity:

​
Co-locate Resources

For best performance and lowest cost, keep related services in the same cloud/region: Good:
Less optimal:
(Cross-cloud latency and data transfer costs)

​
Consider Data Transfer Costs

Moving data between clouds is expensive. Ask Monk: