Skip to content

Commit

Permalink
docs: upstream
Browse files Browse the repository at this point in the history
  • Loading branch information
planetscale-actions-bot committed Aug 16, 2024
1 parent 154425f commit d9a4442
Show file tree
Hide file tree
Showing 3 changed files with 15 additions and 14 deletions.
6 changes: 3 additions & 3 deletions docs/concepts/deployment-options.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,12 +28,12 @@ Multi-tenancy is the default deployment option. When you sign up for a PlanetSca

## Single-tenancy deployment on PlanetScale

Single-tenant deployment options are available with [PlanetScale Enterprise](/docs/concepts/planetscale-plans#planetscale-enterprise-plan). Companies that require their PlanetScale databases to be hosted in a single-tenant environment have two options: Enterprise Single-tenant and Managed.
Single-tenant deployment options are available with [PlanetScale Enterprise](/docs/concepts/planetscale-plans#planetscale-enterprise-plan). Companies that require their PlanetScale databases to be hosted in a single-tenant environment have two options: Enterprise — Single-tenant and Managed.

{% callout %}
In both options, your database is deployed in a single-tenant environment. The main difference between Enterprise Single-tenant and Managed is who owns the underlying account. With [Managed](/docs/enterprise/managed/overview), your database is deployed in your own AWS/GCP account. With Enterprise Single-tenant, PlanetScale owns and manages the account.
In both options, your database is deployed in a single-tenant environment. The main difference between Enterprise — Single-tenant and Managed is who owns the underlying account. With [Managed](/docs/enterprise/managed/overview), your database is deployed in your own AWS/GCP account. With Enterprise — Single-tenant, PlanetScale owns and manages the account.

If you're interested in learning more, please [reach out](/contact) and we can figure out the best solution for your use case.
If you're interested in learning more, please [reach out](/contact), and we can figure out the best solution for your use case.
{% /callout %}

### Single-tenancy highlights
Expand Down
21 changes: 11 additions & 10 deletions docs/concepts/planetscale-plans.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,8 @@ On top of processing and memory, all **Scaler Pro** cluster sizes share the foll
| **PlanetScale CLI** | Included |
| **SSO** | Available as an add-on\*\*\* |
| **Audit log retention** | 6 months |
| **Private connections** | [Configurable](/docs/concepts/private-connections) |
| **BAAs** | Available for an additional fee |
| **Automatic backups** | Every 12 hours |
| **Support** | Standard, upgrade available\*\*\* |
| [**Data Branching®**](/docs/concepts/data-branching) | Included |
Expand Down Expand Up @@ -151,16 +153,15 @@ When you choose to change cluster size, we upgrade each of your replicas one by

PlanetScale's Enterprise Plan is great for users that want to scale farther, shard horizontally, and run PlanetScale in a dedicated AWS/GCP account. We offer many different deployment options, all of which come with the same set of standard features. The table below covers those shared features, as well as the different options that vary depending on your chosen deployment.

| | **Multi-Tenant** | **Single-Tenant** | **[Managed](/docs/enterprise/managed/overview)** |
| --------------------------- | ---------------- | ----------------- | ------------------------------------------------ |
| Horizontal sharding ||||
| Unlimited connections ||||
| Customizable feature limits ||||
| BAAs available ||||
| Private connections ||||
| PCI compliant ||| ✔ (on AWS) |
| Dedicated AWS/GCP account ||||
| Your own AWS/GCP account ||||
| | PlanetScale Enterprise | **[PlanetScale Managed](/docs/enterprise/managed/overview)** |
| ------------------------------------------------------ | --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Horizontal sharding |||
| Customizable feature limits |||
| [Support](/docs/support/support-overview) | Business — Enterprise upgrade available | Enterprise |
| PCI compliant || ✔ (on AWS) |
| Dedicated AWS/GCP account | Optional ||
| Bring your own cloud (an AWS or GCP account _you_ own) |||
| Billing | Directly from PlanetScale | Partial payment through PlanetScale and infrastructure costs through AWS/GCP. Take advantage of your own discounts. Optionally, purchase through [AWS Marketplace](https://aws.amazon.com/marketplace/pp/prodview-luy3krhkpjne4). |

## How do I know if I need an Enterprise plan?

Expand Down
2 changes: 1 addition & 1 deletion docs/concepts/security.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ The following are two examples of data locality in PlanetScale:

### HIPAA and Business Associate Agreements

PlanetScale can enter into Business Associate Agreements (BAAs) with customers who purchase [Business support](/docs/support/support-overview) or an [Enterprise plan](/docs/concepts/planetscale-plans#planetscale-enterprise-plan). Please [reach out for more information](/contact), and we'll be in touch shortly.
PlanetScale can enter into Business Associate Agreements (BAAs) with customers who purchase [Business support](/docs/support/support-overview), an [Enterprise plan](/docs/concepts/planetscale-plans#planetscale-enterprise-plan), or qualify for our startup pricing. Please [reach out for more information](/contact), and we'll be in touch shortly.

The customer must determine whether they are a Covered Entity — or a Business Associate of a Covered Entity — as defined under HIPAA. If so, the customer may require a BAA with PlanetScale for the purposes of our relationship.

Expand Down

0 comments on commit d9a4442

Please sign in to comment.