Bring Your Own Cloud (BYOC)
Last updated
Was this helpful?
Earthly 0.8
Last updated
Was this helpful?
This feature is experimental.
Not recommended for production usage yet, since it might introduce breaking changes in the future.
Feedback is welcome and much appreciated!
"Bring Your Own Cloud" (BYOC) satellites are a hybrid between and satellites. These satellites are managed by Earthly; just like our managed offering, but within your infrastructure. This blends the ease-of-use of managed satellites with the security benefits that self hosting can bring.
BYOC satellites are .
Who is responsible for monitoring and reliability of the Satellite
✅ Earthly
✅ Earthly
❌ You
Satellites are deployed within your internal network
❌ No
✅ Yes
✅ Yes
Earthly Cloud and Earthly staff are prevented from accessing your internal network
✅ N/A
✅ Yes
✅ Yes
How is compute billed
✅ Zero-margin compute via Earthly
✅ To you via your cloud provider
✅ To you via your cloud provider
Automatic updates
✅ Yes
✅ Yes
❌ No
Auto-sleep to drastically reduce compute cost
✅ Yes
✅ Yes
❌ No
Automatic management and GCing of cache volumes
✅ Yes
✅ Yes
❌ No
Users can launch and remove satellites via the earthly sat CLI
✅ Yes
✅ Yes
❌ No
Requires access to a set of limited AWS capabilities
✅ No
❌ Yes
✅ No
Make sure that you meet the base requirements for your cloud provider:
Assuming you meet these requirements, there are multiple methods you can use to provision resources required to operate BYOC. Choose the one that works best for your organization:
Follow the instructions for your selected installation method to provision the required resources and install BYOC.
To use a satellite created by BYOC, you'll need to configure your networking (usually a VPN) to ensure access. We have guides to enable BYOC on VPNs for the following VPN providers:
Now that you have your cloud installation configured in your cloud provider and Earthly, it's time to take it for a test drive!
First, make sure you can see your new cloud by running earthly cloud list, which lists all the cloud installations within your organization. Your output should look something like this:
The * indicates the default cloud that will be used when launching satellites within your organization, unless otherwise specified.
To test-launch a new satellite within the cloud, run:
This will launch a new satellite using your newly created cloud. Assuming that works, kick the tires by trying to run one of your builds on it!
If everything looks good, you're done! If you would like this new cloud to be the default, simply run:
This makes the new cloud you created be the default for the entire organization.
This setting is global for all users within the org. This prevents people from launching satellites in the wrong cloud, and accidentally disseminating information that shouldn't be.
To get a better idea of what will be provisioned, see this section about . All installation methods create the same resources.