Multi-Cloud
Write once, deploy anywhere. Your application code stays the same whether you deploy to AWS, GCP, or both. No cloud-specific SDKs, no vendor lock-in.
See how it could work for your team.
AWSprod-us-east-1 · us-east-1True cloud portability
Most "multi-cloud" solutions still require cloud-specific code or force you to use the lowest common denominator. Encore takes a different approach: your application code uses Encore's cloud primitives, and Encore maps them to the best services on each cloud.
A database in your code becomes RDS on AWS and Cloud SQL on GCP. Pub/Sub becomes SNS+SQS on AWS and Cloud Pub/Sub on GCP. You get production-grade managed services on every cloud.
- Same code, different clouds
- Production-grade services (not containers)
- Switch clouds without rewrites
Same declarations, provider-native infrastructure on each side.
Why multi-cloud?
Avoid Lock-in
Negotiate better pricing, switch providers if needed, and keep your options open as cloud landscapes evolve.
Regional Compliance
Deploy to different clouds in different regions to meet data residency requirements.
Customer Requirements
Some customers require deployment on specific clouds. Support them without maintaining separate codebases.
Your cloud accounts
All infrastructure runs in your own AWS or GCP accounts. Connect your accounts to Encore, and all resources are provisioned directly there. You have full access, and your data never passes through Encore's infrastructure.
You can have different environments on different clouds. Development on GCP, production on AWS. Or one product on AWS and another on GCP. It's entirely flexible.
“What used to take days or weeks of back-and-forth between developers and infra teams is now automated and completed in minutes.”
Josef Sima, Engineering Director at Groupon
Deploy everywhere, code once
True cloud portability without compromise.
Run in your terminal to get started locally.