First rough draft of BYOC docs

[dchw]

No description provided.

[brandonSc]

Suggested change

	"Bring Your Own Cloud" (BYOC) satellites **Experimental** are a hybrid between [self hosted](../self-hosted.md) and [earthly-managed](../../satellites.md) 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.
	"Bring Your Own Cloud" (BYOC) satellites **Experimental** are a hybrid between [Self-Hosted](../self-hosted.md) and [Cloud](../../satellites.md) 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.

We tend to call these "Cloud" satellites in our pricing page and in other doc pages.

[brandonSc]

I still think we should be consistent with how we name these products in our docs and pricing page. We haven't referred to Earthly-Managed in the other pages, so it might get confusing.

I also think the term Earthly-managed could include BYOC because Earthly manages those clouds too.

[brandonSc]

I left some minor comments, but I think the docs are great overall! I like all the screenshots, that should make it easy to follow along with, especially when not familiar with CloudFormation.

[brandonSc]

Should we update the table on this page?
https://docs.earthly.dev/docs/remote-runners

[vladaionescu]

Reading through these tables again, I'm realizing that it's pretty hard to follow along. e.g. the difference "you are responsible for monitoring" isn't clear whether that refers to BYOC or self-hosted.

I think that these tables could be better represented like this:

BYOC vs Cloud

	Earthly Cloud	Earthly BYOC
Who is responsible for monitoring and reliability of the Satellite	✅ Earthly	✅ Earthly
Satellites are deployed within your internal network	❌ No	✅ Yes
Earthly Cloud and Earthly staff are prevented from accessing your internal network	✅ N/A	✅ Yes
How is compute billed	✅ Zero-margin compute via Earthly	✅ Supported by you via your cloud provider
Automatic updates	✅ Yes	✅ Yes
Auto-sleep to drastically reduce compute cost	✅ Yes	✅ Yes
Automatic management and GCing of cache volumes	✅ Yes	✅ Yes
Users can launch and remove satellites via the earthly sat CLI	✅ Yes	✅ Yes
Requires access to a set of limited AWS capabilities	✅ No	❌ Yes

BYOC vs Self-Hosted

	Earthly Self-Hosted	Earthly BYOC
Who is responsible for monitoring and reliability of the Satellite	❌ You	✅ Earthly
Satellites are deployed within your internal network	✅ Yes	✅ Yes
Earthly Cloud and Earthly staff are prevented from accessing your internal network	✅ Yes	✅ Yes
Compute is billed directly to you from your cloud provider	✅ Yes	✅ Yes
Automatic updates	❌ No	✅ Yes
Auto-sleep to drastically reduce compute cost	❌ No	✅ Yes
Automatic management and GCing of cache volumes	❌ No	✅ Yes
Users can launch and remove satellites via the earthly sat CLI	❌ No	✅ Yes
Requires access to a set of limited AWS capabilities	✅ No	❌ Yes

Markdown for this:

### BYOC vs Cloud

| | Earthly Cloud | Earthly BYOC |
|-------|-------|-------|
| Who is responsible for monitoring and reliability of the Satellite | ✅ Earthly | ✅ Earthly |
| Satellites are deployed within your internal network | ❌ No | ✅ Yes |
| Earthly Cloud and Earthly staff are prevented from accessing your internal network | ✅ N/A | ✅ Yes |
| How is compute billed | ✅ Zero-margin compute via Earthly | ✅ Supported by you via your cloud provider |
| Automatic updates | ✅ Yes | ✅ Yes |
| Auto-sleep to drastically reduce compute cost | ✅ Yes | ✅ Yes |
| Automatic management and GCing of cache volumes | ✅ Yes | ✅ Yes |
| Users can launch and remove satellites via the `earthly sat` CLI | ✅ Yes | ✅ Yes |
| Requires access to a set of limited AWS capabilities | ✅ No | ❌ Yes |


### BYOC vs Self-Hosted

| | Earthly Self-Hosted | Earthly BYOC |
|-------|-------|-------|
| Who is responsible for monitoring and reliability of the Satellite | ❌ You | ✅ Earthly |
| Satellites are deployed within your internal network | ✅ Yes | ✅ Yes |
| Earthly Cloud and Earthly staff are prevented from accessing your internal network | ✅ Yes | ✅ Yes |
| Compute is billed directly to you from your cloud provider | ✅ Yes | ✅ Yes |
| Automatic updates | ❌ No | ✅ Yes |
| Auto-sleep to drastically reduce compute cost | ❌ No | ✅ Yes |
| Automatic management and GCing of cache volumes | ❌ No | ✅ Yes |
| Users can launch and remove satellites via the `earthly sat` CLI | ❌ No | ✅ Yes |
| Requires access to a set of limited AWS capabilities | ✅ No | ❌ Yes |