Skip to content

Commit

Permalink
add links for addon
Browse files Browse the repository at this point in the history
  • Loading branch information
kylegalbraith committed Nov 14, 2023
1 parent b898035 commit 1954f57
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 6 deletions.
13 changes: 8 additions & 5 deletions content/self-hosted/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,8 @@ However, with self-hosted Depot builders, you can choose to run your builds insi

Self-hosted builders use a connection that you configure inside your Depot organization with details about your cloud account (type, ID). You can then decide to use either Depot-hosted builder machines or your self-hosted cloud connection on a per-project basis.

**To leverage self-hosted builders, you must have our [self-hosted addon](/pricing) added to your organization.**

## Why use self-hosted builders?

Self-hosted builders are great for organizations that want to run builds on their own infrastructure, inside their own cloud account. Depot fully manages the lifecycle of machines and volumes within your account, but you control that infrastructure and data at all times. The `depot` CLI communicates directly with the machines launched in your account, meaning your build data does not pass through Depot-managed infrastructure at all.
Expand All @@ -22,11 +24,12 @@ Self-hosted builders do require some additional setup work, so for organizations

Depot self-hosted builders support the following clouds:

| Cloud | | Support | Notes |
| ---------------- | --- | ----------- | ------------------------------------ |
| **AWS** || Supported | Currently provisioned with Terraform |
| **Google Cloud** | 🤔 | Considering |
| **Azure** | 🤔 | Considering |
| Cloud | | Support | Notes |
| ---------------- | --- | ----------- | ----------------------------------------------- |
| **AWS** || Supported | Currently provisioned with Terraform |
| **Google Cloud** | 🤔 | Considering | Need this? [let us know](mailto:[email protected]) |
| **Azure** | 🤔 | Considering | Need this? [let us know](mailto:[email protected]) |
| **On-prem** | 🤔 | Considering | Need this? [let us know](mailto:[email protected]) |

## Next steps

Expand Down
2 changes: 1 addition & 1 deletion content/self-hosted/setup-and-usage.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ module "depot-connection" {

## Configure a Depot project to use self-hosted builders

After you have created a connection and provisioned the infrastructure, you can choose to use that new connection on a per-project basis if you are on a Enterprise plan.
After you have created a connection and provisioned the infrastructure, you can choose to use that new connection on a per-project basis if you have the [self-hosted addon](/pricing).

You can update an existing project to use self-hosted builders by changing its connection type.

Expand Down

0 comments on commit 1954f57

Please sign in to comment.