Defang BYOC
Defang aims to make it easier to deploy your services to the cloud. Specifically, Defang's goal is to make it easier to deploy your workloads to your own cloud accounts. We refer to this as bring-your-own-cloud (BYOC). We also provide Defang Playground, but it is only intended for non-production workloads so you can get a feel for how Defang works.
Defang provisions and configures the necessary native managed services from your cloud provider to get your services up and running. For example, on AWS, Defang will configure an ALB, set up ECR, configure CloudWatch, and run your service on ECS and more. The following lists the existing and planned support for cloud providers.
Defang does not install or run any Defang or third party services at runtime. Defang does run the Defang build service to build your container images, which terminates after every build.
Configuration
The Defang CLI can be configured to deploy to a cloud provider either by using the --provider flag or by setting the DEFANG_PROVIDER environment variable. For example:
# Supported provider values: auto, aws, defang, digitalocean
# Default is auto, which deploys to the Defang Playground but warns if it detects cloud credentials
$ defang compose up --provider=aws
# or
$ export DEFANG_PROVIDER=digitalocean
AWS
Please read the AWS Provider documentation for more details about how the AWS provider works and how to get started.
DigitalOcean
The Defang DigitalOcean Provider is available for Public Preview as of October 2024.
Please read the DigitalOcean Provider documentation for more details about how the DigitalOcean provider works and how to get started.
GCP
The Defang GCP Provider is available for Public Preview as of December 2024.
Please check out the GCP Provider page for more details.
Azure
We will be working on Azure support in the future. If you are interested in Azure support, please vote on this issue.