> ## Documentation Index > Fetch the complete documentation index at: https://planetscale.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Deployment options > PlanetScale offers two deployment options to accommodate your application and business needs: multi-tenancy and single-tenancy. export const PlatformAvailability = ({current, vitess, postgres, neki}) => { const docsHref = path => { if (!path) return path; const normalized = path.startsWith('/') ? path : `/${path}`; return normalized; }; const labels = { vitess: 'Vitess', postgres: 'Postgres', neki: 'Neki' }; const combinedLabels = { both: 'Vitess and Postgres', all: 'Vitess, Neki, and Postgres', 'postgres-neki': 'Postgres and Neki' }; if (combinedLabels[current]) { return

{combinedLabels[current]}

; } const hasVitess = current === 'vitess' || Boolean(vitess); const hasPostgres = current === 'postgres' || Boolean(postgres); const hasNeki = current === 'neki' || Boolean(neki); const only = [hasVitess, hasPostgres, hasNeki].filter(Boolean).length === 1; const engines = []; if (current === 'vitess' || current === 'postgres' || current === 'neki') engines.push(current); if (hasVitess && current !== 'vitess') engines.push('vitess'); if (hasNeki && current !== 'neki') engines.push('neki'); if (hasPostgres && current !== 'postgres') engines.push('postgres'); return

{engines.map(engine => { const isCurrent = current === engine; const href = docsHref(engine === 'vitess' ? vitess : engine === 'postgres' ? postgres : neki); const label = only ? `${labels[engine]} only` : labels[engine]; const state = isCurrent || !href ? 'current' : 'link'; if (isCurrent || !href) { return {label} ; } return {label} ; })}

; }; ## Overview **Multi-tenancy** — In a multi-tenant environment, your database is hosted on infrastructure shared with other users/customers. **Single-tenancy** — In a single-tenant environment, your database is hosted on dedicated infrastructure that is not shared with any other users/customers. Your deployment options depend on the [PlanetScale plan](/docs/planetscale-plans) you choose. This documentation covers some differences between single-tenancy and multi-tenancy so you can evaluate which plan may be suitable for you. For an in-depth look at the different plans we offer, see the [PlanetScale plans documentation](/docs/planetscale-plans). ## Multi-tenancy deployment on PlanetScale Multi-tenancy is the default deployment option. When you sign up for a PlanetScale account with the Base plan, your databases will be created in our multi-tenancy deployment offering. Our Enterprise plan also offers a multi-tenancy deployment option. ### Multi-tenancy highlights * Your database runs on PlanetScale's [secure cloud infrastructure](/docs/security) * Lowest cost plans * No configuration requirements on your end * BAAs available for HIPAA compliance * [Private connection support](/docs/vitess/connecting/private-connections) via AWS PrivateLink * [Private connection support](/docs/vitess/connecting/private-connections-gcp) via GCP Private Service Connect ## Single-tenancy deployment on PlanetScale Single-tenant deployment options are available with [PlanetScale Enterprise](/docs/planetscale-plans#enterprise-plan). Companies that require their PlanetScale databases to be hosted in a single-tenant environment have two options: Enterprise — Single-tenant and Managed. 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/plans/managed), your database is deployed in your own AWS, GCP, or Azure account. With Enterprise — Single-tenant, PlanetScale owns and manages the account. If you're interested in learning more, please [reach out](https://planetscale.com/contact), and we can figure out the best solution for your use case. ### Single-tenancy highlights * Your resources run in a separate isolated AWS account, GCP project, or Azure subscription, apart from other customers * Your databases can be deployed to supported cloud provider regions that offer three availability zones, including regions that PlanetScale does not offer on our self-serve plans * Azure does not make every PlanetScale-supported VM SKU available to every subscription. Coordinate region selection with your PlanetScale Solutions Engineer. PlanetScale may ask you to verify that your dedicated subscription has access to the required VM SKUs and sufficient quota across three availability zones in each requested region. * You can continue to use the PlanetScale UI and CLI in the same way that you would our general self-serve offerings, but the infrastructure runs in an isolated environment * BAAs available for HIPAA compliance * Support for private database connectivity via: * **AWS** — [AWS PrivateLink](/docs/plans/managed/aws/privatelink) (recommended) or [VPC peering](/docs/plans/managed/aws/vpc-peering) * **GCP** — [Private Service Connect](https://cloud.google.com/vpc/docs/private-access-options) * **Azure** — [Azure Private Link](/docs/plans/managed/azure/private-link) If you have any questions about which deployment option may be best for you, [reach out to us](https://planetscale.com/contact) and we can help you figure it out. ## Need help? Get help from [the PlanetScale Support team](https://planetscale.com/contact?initial=support), or join our [Discord community](https://pscale.link/community) to see how others are using PlanetScale. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.