Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Brian gillet patch 2 #1864

Closed
wants to merge 8 commits into from
Closed
Show file tree
Hide file tree
Changes from 5 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -5,12 +5,14 @@ title: Overview

:::info Deployments

This section provides an overview of the deployment types available for dbt Cloud.
This section provides an overview of the deployment types available with specific dbt Cloud plans.
If you’re interested in learning more about an Enterprise plan, contact us at [email protected].

:::

In general, the dbt Cloud application deployment models fall into two categories: **Multi Tenant** and **Single Tenant**. These deployments are hosted on infrastructure managed by dbt Labs. Both models leverage AWS infrastructure as described in the [Architecture](deployment-architecture) section.
In general, the dbt Cloud application deployment models fall into two categories: **Multi Tenant** and **Single Tenant**. These deployments are hosted on infrastructure managed by dbt Labs. The Multi Tenant model leverages AWS infrastructure as described in the [Architecture](deployment-architecture) section.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
In general, the dbt Cloud application deployment models fall into two categories: **Multi Tenant** and **Single Tenant**. These deployments are hosted on infrastructure managed by dbt Labs. The Multi Tenant model leverages AWS infrastructure as described in the [Architecture](deployment-architecture) section.
The dbt Cloud application deployment models fall into two categories: **Multi-Tenant** and **Single Tenant**. These deployments are hosted on infrastructure managed by dbt Labs. The Multi-Tenant model leverages AWS infrastructure as described in the [Architecture](deployment-architecture) section.


The Single Tenant model can be deployed to AWS or Azure infrastructure managed by dbt Labs. The Single Tenant model is only available with dbt Labs' Virtual Private dbt plan. All other plans leverage the Multi Tenant model. Contact us at [email protected] to discuss the best plan for your requirements.

For more information on these deployment models view the below pages.

Expand Down
2 changes: 2 additions & 0 deletions website/docs/docs/dbt-cloud/deployments/multi-tenant.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,8 @@ title: Multi Tenant (SaaS)

The Multi Tenant (SaaS) deployment environment refers to the SaaS dbt Cloud application hosted by dbt Labs. This is the most commonly used deployment and is completely managed and maintained by dbt Labs, the makers of dbt. As a SaaS product, a user can quickly [create an account](https://www.getdbt.com/signup/) and get started using the product. The deployment is hosted in AWS and will always contain the latest software updates and bug fixes.

If your organization requires more advanced security, SSO/RBAC, or additional support, please contact dbt Labs sales ([email protected]) to learn more about our Enterprise plans.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If your organization requires more advanced security, SSO/RBAC, or additional support, please contact dbt Labs sales ([email protected]) to learn more about our Enterprise plans.
If your organization requires advanced security features, SSO/RBAC, or additional support, please contact dbt Labs sales ([email protected]) to learn more about our Enterprise plans.


For more information about the dbt Cloud Production deployment see the below.

- [Application Data Flows](/docs/dbt-cloud/deployments/deployment-architecture#application-data-flows)
Expand Down
8 changes: 4 additions & 4 deletions website/docs/docs/dbt-cloud/deployments/single-tenant.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,15 +3,15 @@ id: single-tenant-deployment
title: Single Tenant
---

The Single Tenant deployment environment provides a hosted alternative to the Multi Tenant (SaaS) dbt Cloud environment. While still managed and maintained by dbt Labs, the Single Tenant environment provides dedicated infrastructure with one or more instances of dbt Cloud that can only be accessed by a single customer. This is accomplished by spinning up all the necessary infrastructure with a re-usable Infrastructure as Code (IaC) deployment built with [Terraform](https://www.terraform.io/). The Single Tenant infrastructure lives in a dedicated AWS account and can be customized with certain configurations such as Firewall rules to limit ingress traffic or hosting in a specific AWS Region.
The Single Tenant deployment environment provides a hosted alternative to the Multi Tenant (SaaS) dbt Cloud environment. While still managed and maintained by dbt Labs, the Single Tenant environment provides dedicated infrastructure with one or more instances of dbt Cloud that can only be accessed by a single customer. This is accomplished by spinning up all the necessary infrastructure with a re-usable Infrastructure as Code (IaC) deployment built with [Terraform](https://www.terraform.io/). The Single Tenant infrastructure lives in a dedicated AWS or Azure account and can be customized with certain configurations such as Firewall rules to limit ingress traffic or hosting in a specific AWS or Azure Region.

A few common reasons for choosing a Single Tenant deployment over the Production SaaS product include:
A couple common reasons for choosing the Virtual Private dbt plan, which includes a Single Tenant deployment include:
- A requirement that the dbt Cloud application be hosted in a dedicated VPC that is logically separated from other customer infrastructure
- A desire for multiple isolated dbt Cloud instances for testing, development, etc

_To learn more about setting up a dbt Cloud Single Tenant deployment, [please contact our sales team](mailto:[email protected])._
_To learn more about the Virtual Private dbt plan, [please contact our sales team](mailto:[email protected])._

For more information about the dbt Cloud Single Tenant deployment see the below.
For more information about the Single Tenant deployment see the below.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For more information about the Single Tenant deployment see the below.
For more information about the Single Tenant deployment:


- [Application Data Flows](/docs/dbt-cloud/deployments/deployment-architecture#application-data-flows)
- [Hosted Network Architecture](/docs/dbt-cloud/deployments/deployment-architecture#hosted-network-architecture)