Skip to main content

​
What It Does

Running on AWS but want to switch to DigitalOcean? On GCP but need to move to Azure? Monk migrates your entire application between cloud providers with a simple conversation. No vendor lock-in. Switch clouds anytime.

​
How It Works

​
The Migration Process

Starting point:
  • Your application is running on Cloud 1 (e.g., AWS)
  • Managed by Monk
Migration steps:

​
1. Request Migration

Chat with Monk in your IDE: 
You: Migrate this application to DigitalOcean

​
2. Provide Credentials

Monk asks for credentials to the target cloud provider: 
Monk: I'll need DigitalOcean credentials to provision resources.
      Please provide your DigitalOcean API token.

You: [Provides token]

Monk: Credentials received. Analyzing current deployment...
Your credentials stay secure - They’re stored on your side, never exposed to the LLM, and never sent to Monk servers. See Security for details. Monk needs these because everything runs on your infrastructure (Bring Your Own Infrastructure - BYOI).

​
3. Resource Provisioning

Monk provisions matching resources on the target cloud: 
Monk: Current AWS infrastructure:
      - 2x t3.medium instances (API servers)
      - 2x t3.small instances (workers)
      - Application Load Balancer
      - VPC with security groups

Monk: Creating equivalent DigitalOcean resources:
      - 2x 2GB Droplets (API servers)
      - 2x 1GB Droplets (workers)
      - Load Balancer
      - VPC with firewall rules
Monk creates infrastructure that matches your current deployment, optimized for the target cloud’s instance types and services.

​
4. Workload Transfer

Monk starts your application on the new cloud and stops it on the old one: What gets migrated:
Data migrationCurrently, Monk migrates workloads (containers, configuration, networking) but not database data. For databases: - Managed services (RDS, Cloud SQL, etc.) remain on original cloud - Self-hosted databases stay on original infrastructure
  • Your migrated application connects to databases on the original cloud Full data migration is coming soon!

​
5. DNS Switchover

If you’re using a DNS provider (Route 53, Cloudflare DNS, etc.):
  • Monk automatically updates DNS records to point to new infrastructure
  • Traffic seamlessly shifts to new cloud
  • Old workloads receive no new requests
If you’re not using DNS managed by Monk:
  • Monk provides new IP addresses/URLs
  • You manually update DNS or load balancer configuration

​
6. Cleanup

After verifying everything works on the new cloud: 
You: Delete the old AWS resources

Monk: Confirming: Delete all AWS resources for this application?
      - 4 instances
      - Load balancer
      - VPC and security groups

You: Yes

Monk: Deleting AWS resources... ✓ Complete
      Migration finished. Running entirely on DigitalOcean.
Done! Your application is now running on the new cloud provider.

​
What Makes This Different

Traditional cloud migration requires:
  • Weeks or months of planning and execution
  • Manually recreating infrastructure on new cloud
  • Learning new cloud provider’s services and terminology
  • Rewriting infrastructure-as-code for new provider
  • Complex data migration strategies
  • Coordinating DNS cutover
  • Risk of extended downtime
  • Expensive migration consultants
With Monk: Request migration, provide credentials, done. Workloads move automatically.

​
Why Migrate?

Cost savings:
  • Move from expensive cloud to cheaper alternative
  • Save 30-60% on compute costs by switching providers
Better services:
  • Access provider-specific features (AWS SageMaker, Azure OpenAI, GCP BigQuery)
  • Use specialized hosting (Netlify, Vercel for frontends)
Geographic expansion:
  • Add regions available on other cloud providers
  • Better latency for global users
Vendor diversification:
  • Reduce dependency on single cloud provider
  • Increase resilience with multi-cloud architecture
Compliance:
  • Meet data residency requirements in specific regions
  • Switch to providers with required certifications

​
Key Capabilities

  • Cross-cloud migration - AWS, GCP, Azure, DigitalOcean
  • Simple workflow - Request migration, provide credentials, done
  • Automatic provisioning - Matching infrastructure created on target cloud
  • Workload transfer - Containers and configuration migrated automatically
  • DNS switchover - Automatic DNS updates when using managed DNS
  • External service preservation - APIs, databases, third-party services stay connected
  • Cost optimization - Often significant savings from provider switch
  • No vendor lock-in - Switch clouds anytime
  • Partial migrations - Move some components, keep others where they are

​
Current Limitations

Database data migration is coming soon. Currently: - Workloads (containers, code, configuration) migrate fully - Database data stays on original cloud - Applications connect across clouds (encrypted by Monk) - Manual data migration possible (export/import) Automatic database data migration will be available soon!