Showing the first 18000 characters. Load the complete file to read the remainder.
# PlanetScale
> PlanetScale is a relational database platform for Vitess, Neki, and Postgres that gives you scale, performance, and reliability without sacrificing developer experience.
## Platform
###
- [PlanetScale](https://planetscale.com/docs/index.md): PlanetScale is a relational database platform that brings you scale, performance, and reliability — without sacrificing developer experience.
### Product
- [What is PlanetScale?](https://planetscale.com/docs/what-is-planetscale.md): A fully managed relational database platform for Vitess, Neki, and Postgres, built for scale, performance, and reliability.
- [Vitess, Neki, and Postgres](https://planetscale.com/docs/postgres-vs-vitess.md): Compare PlanetScale's Vitess, Neki, and Postgres products
#### Metal
- [PlanetScale Metal](https://planetscale.com/docs/metal.md): PlanetScale Metal databases are the same PlanetScale databases you know and love, powered by blazing-fast, locally-attached NVMe SSD drives instead of network-attached storage.
- [Create a Metal database](https://planetscale.com/docs/metal/create-a-metal-database.md): Create a new Metal database or upgrade an existing one to locally attached NVMe storage.
- [PlanetScale plans](https://planetscale.com/docs/planetscale-plans.md)
- [How to check performance after upgrading to Metal](https://planetscale.com/docs/metal/metal-performance.md): PlanetScale [Metal](/metal) databases offer performance benefits for many types of workloads.
### Connect and automate
- [Stripe Projects](https://planetscale.com/docs/connect/stripe-projects.md): Stripe Projects allows you to provision and manage PlanetScale Postgres and MySQL/Vitess databases directly from the Stripe CLI with the Stripe Projects developer preview.
- [Cloudflare](https://planetscale.com/docs/connect/cloudflare.md): Create and pay for PlanetScale Postgres or MySQL databases from the Cloudflare dashboard without adding billing details to PlanetScale.
- [PlanetScale Terraform provider](https://planetscale.com/docs/terraform.md): A resource model for Vitess, Neki, and Postgres databases, designed for Terraform and OpenTofu.
#### AI & automation
- [Agents](https://planetscale.com/docs/agents.md): Use agents with PlanetScale to answer database questions, investigate performance, and prepare fixes.
- [Grok Bot](https://planetscale.com/docs/agents/grok-bot.md): Set up PlanetScale Bot to answer database questions, investigate performance, and follow webhook events.
- [Agent setup prompt](https://planetscale.com/docs/agent-setup/prompt.md): PlanetScale instructions for AI agents to install skills, configure MCP, and authenticate the CLI.
- [AI-enhanced development](https://planetscale.com/docs/ai-tooling.md): Improve your database development experience with AI-powered tooling specifically designed for PlanetScale
- [Self-improving database](https://planetscale.com/docs/self-improving-database.md): Use the PlanetScale MCP server with AI coding agents to continuously optimize database performance based on production Insights data and Schema Recommendations
#### MCP
- [PlanetScale Model Context Protocol (MCP)](https://planetscale.com/docs/mcp-server.md): Connect Claude, Cursor, Notion, and other MCP-compatible tools to your PlanetScale databases and Insights
- [Authenticate the MCP server with a service token](https://planetscale.com/docs/mcp/service-token.md): Use a PlanetScale service token to authenticate the hosted MCP server in CI, headless agents, and clients that send a custom HTTP header
### Plans and billing
- [Billing](https://planetscale.com/docs/billing.md): PlanetScale applies billing plans at the **database level**. You can create several databases under one Organization.
- [PlanetScale plans](https://planetscale.com/docs/planetscale-plans.md)
- [Cluster sizes](https://planetscale.com/docs/plans/planetscale-skus.md): Here you'll find a complete list of all the database sizes available to you on PlanetScale.
- [Selecting a region](https://planetscale.com/docs/plans/regions.md)
- [Deployment options](https://planetscale.com/docs/plans/deployment-options.md): PlanetScale offers two deployment options to accommodate your application and business needs: multi-tenancy and single-tenancy.
- [PlanetScale Support](https://planetscale.com/docs/support.md): PlanetScale’s team has a combined 600 years of experience running databases at scale.
#### PlanetScale Managed
- [PlanetScale Managed overview](https://planetscale.com/docs/plans/managed.md): Run PlanetScale in your own AWS, GCP, or Azure account, operated by our team with your data in your cloud.
- [The proof of concept phase of an enterprise contract](https://planetscale.com/docs/plans/managed/proof-of-concept.md): We get many customers that come to us with existing large, production databases.
##### AWS
- [PlanetScale Managed on AWS overview](https://planetscale.com/docs/plans/managed/aws.md): PlanetScale Managed on Amazon Web Services (AWS) is a single-tenant deployment of PlanetScale in your AWS organization within an isolated AWS Organizations member account.
- [Set up PlanetScale Managed in AWS](https://planetscale.com/docs/plans/managed/aws/getting-started.md): The following guide will walk you through setting up a PlanetScale Managed cluster in your Amazon Web Services (AWS) organization.
- [Set up AWS PrivateLink with PlanetScale Managed](https://planetscale.com/docs/plans/managed/aws/privatelink.md): PlanetScale Managed can connect you to your databases via [AWS PrivateLink](https://aws.amazon.com/privatelink/). The following guide describes how PlanetScale Managed with AWS PrivateLink works and how to set it up.
- [Set up AWS VPC peering with PlanetScale Managed](https://planetscale.com/docs/plans/managed/aws/vpc-peering.md): Private database connectivity between your VPC and a PlanetScale Managed deployment over AWS VPC peering.
- [Set up AWS Reverse PrivateLink with PlanetScale Managed](https://planetscale.com/docs/plans/managed/aws/reverse-privatelink.md): [PlanetScale Managed](/docs/plans/managed/aws) can connect to your existing databases via AWS PrivateLink for the purposes of data imports.
- [Back up and restore in AWS](https://planetscale.com/docs/plans/managed/aws/back-up-and-restore.md): PlanetScale Managed backup and restore functions like the hosted PlanetScale product. For more info, see [how to create, schedule, and restore backups for your PlanetScale databases](/docs/vitess/backups).
##### Azure
- [PlanetScale Managed on Azure overview](https://planetscale.com/docs/plans/managed/azure.md): A single-tenant deployment of PlanetScale in a dedicated Azure subscription that you own and PlanetScale operates.
- [Set up PlanetScale Managed in Azure](https://planetscale.com/docs/plans/managed/azure/getting-started.md): Prepare a dedicated Azure subscription and deploy the one-time bootstrap required for PlanetScale Managed.
- [Set up Azure Private Link with PlanetScale Managed](https://planetscale.com/docs/plans/managed/azure/private-link.md): Connect an application virtual network privately to a PlanetScale Managed deployment in Azure.
##### GCP
- [PlanetScale Managed on GCP overview](https://planetscale.com/docs/plans/managed/gcp.md): PlanetScale Managed on Google Cloud Platform (GCP) is a single-tenant deployment of PlanetScale in your GCP organization within an isolated project.
- [Set up PlanetScale Managed in GCP](https://planetscale.com/docs/plans/managed/gcp/getting-started.md): The following guide will walk you through setting up a PlanetScale Managed cluster in your Google Cloud Platform (GCP) organization.
- [Set up GCP Private Service Connect with PlanetScale Managed](https://planetscale.com/docs/plans/managed/gcp/private-service-connect.md): PlanetScale Managed can connect you to your databases via [GCP Private Service Connect](https://cloud.google.com/vpc/docs/private-service-connect).
- [Back up and restore in GCP](https://planetscale.com/docs/plans/managed/gcp/back-up-and-restore.md): PlanetScale Managed backup and restore functions like the hosted PlanetScale product. For more info, see [how to create, schedule, and restore backups for your PlanetScale databases](/docs/vitess/backups).
##### Security and access
- [User management](https://planetscale.com/docs/plans/managed/security-and-access/user-management.md)
- [Cloud accounts and contents](https://planetscale.com/docs/plans/managed/security-and-access/cloud-accounts-and-contents.md)
- [Data requests](https://planetscale.com/docs/plans/managed/security-and-access/data-requests.md)
- [Schema snapshots](https://planetscale.com/docs/plans/managed/security-and-access/schema-snapshots.md)
##### Settings
- [Maintenance schedules](https://planetscale.com/docs/plans/managed/maintenance-schedules.md): Enterprise customers have the option to enable scheduled maintenance windows on databases.
### Security
- [Security and compliance](https://planetscale.com/docs/security.md): PlanetScale is committed to delivering a powerful and easy-to-use database platform while keeping your data secure.
- [Vulnerability disclosure](https://planetscale.com/docs/security/vulnerability-disclosure.md)
- [How PlanetScale uses AI](https://planetscale.com/docs/how-we-use-ai.md): Which PlanetScale features use generative AI, and how we ensure customer data stays secure and private.
#### Account access
- [Authentication methods](https://planetscale.com/docs/security/authentication-methods.md): There are three ways to authenticate with PlanetScale: _email address and password_, _single sign-on_, and _OAuth via GitHub_.
- [Multi-factor authentication](https://planetscale.com/docs/security/multi-factor-authentication.md): Multi-factor authentication (MFA) provides better safety for your databases and prevents unauthorized access to your user account.
- [Account password security](https://planetscale.com/docs/security/account-password-security.md): In addition to best practices like [multi-factor authentication](/docs/security/multi-factor-authentication), PlanetScale securely stores your account passwords and validates passwords against known security breaches.
- [Security log](https://planetscale.com/docs/security/security-log.md): The Security log gives you insight into recent authentication and other security-related `actions` for your account. Your security log also details when you performed each `action`.
#### Organization access
- [Access control](https://planetscale.com/docs/security/access-control.md)
- [Single sign-on](https://planetscale.com/docs/security/sso.md): Single sign-on (SSO) provides additional account security by allowing company administrators to require the use of an identity provider when logging into PlanetScale.
- [Audit log](https://planetscale.com/docs/security/audit-log.md): The organization audit log grants [Organization Administrators](/docs/security/access-control#organization-administrator) access to review **actions** performed by individual members of the organization.
- [Teams](https://planetscale.com/docs/security/teams.md): PlanetScale allows you to create teams within organizations.
- [Vitess (185 pages)](https://planetscale.com/docs/_llms/vitess.txt): Documentation for Vitess.
## Neki
###
- [Neki](https://planetscale.com/docs/neki.md): Horizontal sharding for Postgres
### Architecture
#### Foundations
- [Overview](https://planetscale.com/docs/neki/overview.md): The components of a Neki deployment and how they fit together
- [When to shard](https://planetscale.com/docs/neki/when-to-shard.md): Whether a Postgres workload needs horizontal sharding
- [Neki vs PlanetScale Postgres](https://planetscale.com/docs/neki/coming-from-postgres.md): The upgrade path from regular Postgres to Neki
- [Neki vs Vitess](https://planetscale.com/docs/neki/vitess-and-postgres.md): Vitess concepts mapped to Neki's Postgres architecture
#### Core concepts
- [Data topology](https://planetscale.com/docs/neki/data-topology.md): How Neki maps tables and shard keys to shards
- [Query planning](https://planetscale.com/docs/neki/query-planning.md): How Neki plans a statement, and how to inspect its plan with EXPLAIN
- [Shard targeting and fanout](https://planetscale.com/docs/neki/shard-targeting-fanout.md): Limit how broadly statements route, choose where reads run, and target one shard
- [Transactions](https://planetscale.com/docs/neki/transactions.md): Snapshot and commit behavior for transactions that reach more than one shard
- [Reference tables and GSIs](https://planetscale.com/docs/neki/reference-tables-and-gsis.md): Shared data placement and secondary lookup routing
- [Replicator workflows](https://planetscale.com/docs/neki/replication.md): Copy and change streaming for migrations and online schema changes
#### Workflows
- [Data migration](https://planetscale.com/docs/neki/data-migration.md): Table movement, resharding, verification, and traffic cutover
- [Schema changes](https://planetscale.com/docs/neki/schema-changes.md): Native DDL and managed workflows across Neki shards
#### Reference
- [Platform preview limitations](https://planetscale.com/docs/neki/platform-preview-limitations.md): Postgres features and query shapes that Neki does not support during Platform Preview
- [Neki terminology](https://planetscale.com/docs/neki/terminology.md): Definitions for the Postgres, PlanetScale, and Neki concepts used throughout the documentation.
- [Neki error codes](https://planetscale.com/docs/neki/error-codes.md): The numeric codes Neki reports with a not implemented error, the query shapes that trigger them, and what to do instead.
- [Error hints and details](https://planetscale.com/docs/neki/error-hints-and-details.md): How Neki uses the DETAIL and HINT fields of Postgres errors and notices, and why clients should not hide them.
- [EXPLAIN output reference](https://planetscale.com/docs/neki/explain-reference.md): Complete EXPLAIN (NEKI_PLAN) and EXPLAIN (NEKI_PG_PLAN) output for one query in every format
- [Example schema](https://planetscale.com/docs/neki/example-schema.md): The tables and data topology used by the SQL examples in the Neki documentation
### Pricing
- [Neki pricing](https://planetscale.com/docs/neki/pricing.md): How shard, router, storage, backup, and network resources contribute to Neki pricing.
### Platform
- [Postgres extensions](https://planetscale.com/docs/neki/extensions.md): Built-in and community Postgres extensions available on Neki.
- [Back up and restore](https://planetscale.com/docs/neki/backups.md): Create, schedule, and restore backups for Neki database branches.
#### Getting started
- [Neki database dashboard](https://planetscale.com/docs/neki/neki-dashboard.md): Cluster topology, summary statistics, and query performance for a Neki database
- [Neki quickstart](https://planetscale.com/docs/neki/tutorials/planetscale-quick-start-guide.md): Create a single-shard Neki database, connect, and insert data
- [Neki sharding quickstart](https://planetscale.com/docs/neki/tutorials/sharding-quick-start-guide.md): Add a shard and route a new table with a data topology
- [Neki best practices](https://planetscale.com/docs/neki/best-practices.md): Data placement, transaction scope, and workload isolation
#### Connecting
- [Connect to Neki](https://planetscale.com/docs/neki/connecting.md): Postgres clients, roles, router groups, and replica routing
- [Roles and credentials](https://planetscale.com/docs/neki/connecting/roles.md): Create and manage branch-scoped Postgres roles for Neki.
- [PlanetScale Terraform provider](https://planetscale.com/docs/terraform.md): A resource model for Vitess, Neki, and Postgres databases, designed for Terraform and OpenTofu.
- [Web console](https://planetscale.com/docs/neki/web-console.md): Run Postgres queries and DDL from the dashboard.
##### Private connections
- [Connect privately with AWS PrivateLink](https://planetscale.com/docs/neki/connecting/private-connections/aws-privatelink.md): Private connectivity between an AWS VPC and Neki through AWS PrivateLink.
- [Connect privately with GCP Private Service Connect](https://planetscale.com/docs/neki/connecting/private-connections/gcp-private-service-connect.md): Private connectivity between a Google Cloud VPC and Neki through Private Service Connect.
#### Configuration
- [Cluster sizing](https://planetscale.com/docs/neki/cluster-configuration/cluster-sizing.md): Choose and change configuration-profile, admin, and router sizes for a Neki database.
- [Cluster configuration](https://planetscale.com/docs/neki/cluster-configuration.md): Configure Neki admin, routers, configuration profiles, and shards.
- [Configure Neki maintenance windows](https://planetscale.com/docs/neki/cluster-configuration/maintenance-windows.md): Weekly maintenance scheduling for production Neki branches.
- [Configuration parameters](https://planetscale.com/docs/neki/cluster-configuration/parameters.md): Configure Postgres, connection-pool, admin, and router parameters for a Neki database.
- [Database replicas](https://planetscale.com/docs/neki/replicas.md): Use Neki replicas for high availability and read-only traffic.
- [Read-only replicas](https://planetscale.com/docs/neki/read-only-replicas.md): Add Neki read-only replicas to serve long-running reads without using the replicas that take over during failover.
#### Migrate to Neki
- [Import a Postgres database](https://planetscale.com/docs/neki/imports/postgres.md): Import Postgres into Neki with pg_dump and pg_restore
- [Troubleshoot a Neki migration](https://planetscale.com/docs/neki/imports/troubleshooting.md): Resolve discovery, topology-planning, data-movement, validation, and cutover problems.
#### Branching
- [Branching](https://planetscale.com/docs/neki/branching.md): Create development branches, restore from backups, and run production with high availability.
- [Development environments](https://planetscale.com/docs/neki/development-environments.md): Set up empty branches for schema work
Measured from the saved file
Linked document
UTF-8 text size
24.7 KB25337 bytes
Token count
5873o200k_base encoding
Markdown links
173164 distinct URLs
Fenced code blocks
0295 lines in the file
Size measures the captured UTF-8 text, not compressed transfer size. Tokens are counted with a named tokenizer; other models can count differently. Neither measure establishes context compatibility or answer quality.
Project H1
PlanetScale
Opening blockquote
PlanetScale is a relational database platform for Vitess, Neki, and Postgres that gives you scale, performance, and reliability without sacrificing developer experience.
Context architecture
How the content is divided
6 H2 sections organize 173 parsed Markdown links. 153 links point to .md or .markdown paths; 4 link occurrences use another hostname. Linked destinations have not been recursively validated.
H2 section
Links
UTF-8 bytes
Tokens
PlatformLine 5
63
11033
2392
NekiLine 111
60
9553
2264
CLI ReferenceLine 223
41
3705
965
OpenAPI SpecsLine 275
1
34
12
OptionalLine 279 · Optional
4
315
79
IndexesLine 288
4
432
108
Link counts exclude parsed fenced and inline code and resolve relative destinations against the final endpoint. Section sizes cover the text below each H2 until the next H2.
Embedded material
Code, installation and API examples
Fenced blocks
0 closed
Declared languages
No fenced blocks detected
Package-install commands
0 detected in fenced or inline code
Authentication examples
0 fenced lines match API-key, Authorization, Bearer, OAuth or access-token patterns
HTTP request examples
0 fenced lines match request-method patterns
Authentication links
0 links have authentication-related labels
Embedded example text and links to further documentation are counted separately. A code block does not establish that a sample runs or that an authentication flow succeeds.
Publisher prioritization
The Optional section
1 H2 section named “Optional” contain 4 parsed links. 169 links sit outside those sections. That puts 2.3% of the file’s parsed links under Optional.
The community proposal uses Optional by convention for secondary links that can be skipped for a shorter context. This label does not establish that everything outside it is critical, or that the material inside it is deprecated.
Machine-readable routes
MCP references and configuration text
MCP-related text was detected in the captured file. 2 links have MCP-related labels or paths. 0 fenced lines match mcpServers, mcp_servers or an mcp add command.
Whole-file size not established by the bounded response
Token count
Not measured for the whole file
Retrieval scope
Bounded prefix inspected; the whole body was not downloaded
A verified text response establishes a companion at the checked URL. It does not prove the bundle contains all product documentation, that generation is automated, or that it fits an assistant’s context window.
Change evidence
What can be said about freshness
This capture establishes a baseline. Update frequency cannot be determined from one observation.
Linked release and migration material
2 links have release, changelog, deprecation or migration terms in their labels or paths. These provide places to investigate product changes separately.
File changes can reveal documentation edits or navigation changes. They do not by themselves measure product release velocity, accuracy, agent adoption or AI visibility.
Counts use a deterministic parser, not a spec-compliance grade. Unusual Markdown and indented code can fall outside its recognized patterns. See the llms.txt proposal and tokenizer implementation.