Skip to content

The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.

chore(www): add blog cross-links and fix outdated links (2026 posts) (#51769)

Kody Jackson97df2685690b
diff --git a/apps/www/_blog/2026-01-07-supabase-security-2025-retro.mdx b/apps/www/_blog/2026-01-07-supabase-security-2025-retro.mdx
index 290085f37ba..587e4690843 100644
--- a/apps/www/_blog/2026-01-07-supabase-security-2025-retro.mdx
+++ b/apps/www/_blog/2026-01-07-supabase-security-2025-retro.mdx
@@ -14,7 +14,7 @@ imgThumb: 2026/security-retro/thumb.png
This post covers security changes made to the Supabase platform in 2025 and what to expect in 2026. Some changes may be breaking.
-Postgres Row Level Security (RLS) is powerful but can be complex for developers new to the pattern. Most of the changes in 2025 focused on safer defaults and better tooling to make security more accessible.
+Postgres [Row Level Security](/docs/guides/database/postgres/row-level-security) (RLS) is powerful but can be complex for developers new to the pattern. Most of the changes in 2025 focused on safer defaults and better tooling to make security more accessible.
We'll cover what shipped in 2025 and outline planned improvements for 2026.
@@ -139,7 +139,7 @@ Security Advisors scan your project for misconfigurations using [Splinter](https
The dashboard includes an Assistant that helps fix security issues detected by Security Advisors. When viewing alerts, you can ask the Assistant to generate and apply RLS policies. Describe your security requirements in plain text and the Assistant will generate the corresponding policy SQL. The Assistant can also suggest improvements for policies and configurations. This helps developers write correct RLS policies more quickly.
-Security Advisors are also available through our MCP server, allowing developers to scan and fix all security issues from their development environment with a simple command. This integrates security checks directly into your workflow.
+Security Advisors are also available through our [MCP server](/docs/guides/ai-tools/mcp), allowing developers to scan and fix all security issues from their development environment with a simple command. This integrates security checks directly into your workflow.
## Column-level security
@@ -163,7 +163,7 @@ Column-level security works independently from RLS. You can use both together: R
zoomable={true}
/>
-[Custom claims](/docs/guides/database/postgres/custom-claims-and-role-based-access-control-rbac) let you add metadata to JWTs for role-based access control (RBAC). Instead of writing RLS policies for each table, you can embed role information in the authentication token and check it in your policies. This works well if you're migrating from traditional RBAC systems or prefer centralized role management.
+[Custom claims](/docs/guides/api/custom-claims-and-role-based-access-control-rbac) let you add metadata to JWTs for role-based access control (RBAC). Instead of writing RLS policies for each table, you can embed role information in the authentication token and check it in your policies. This works well if you're migrating from traditional RBAC systems or prefer centralized role management.
## VPC / Private Link on AWS
diff --git a/apps/www/_blog/2026-01-08-introducing-trae-solo-integration.mdx b/apps/www/_blog/2026-01-08-introducing-trae-solo-integration.mdx
index d673e91af26..eb8e5eab675 100644
--- a/apps/www/_blog/2026-01-08-introducing-trae-solo-integration.mdx
+++ b/apps/www/_blog/2026-01-08-introducing-trae-solo-integration.mdx
@@ -43,7 +43,7 @@ View your database tables, explore schemas, and run queries without switching to
### Manage storage buckets
-Browse your Supabase Storage buckets directly from TRAE. Upload, organize, and manage files as part of your development workflow.
+Browse your [Supabase Storage](/storage) buckets directly from TRAE. Upload, organize, and manage files as part of your development workflow.
![Storage bucket management in TRAE SOLO](/images/blog/2026-01-08-introducing-trae-solo-integration/2.webp)
@@ -75,7 +75,7 @@ Getting started with Supabase in TRAE SOLO is straightforward:
2. **Assign a project.** Select which Supabase project to associate with your TRAE project.
3. **Start building.** Access your database, storage, auth, and more directly from the IDE.
-TRAE uses the [Supabase Management API](https://supabase.com/docs/reference/api/introduction) as well as the [Supabase MCP Server](https://supabase.com/docs/guides/getting-started/mcp).
+TRAE uses the [Supabase Management API](https://supabase.com/docs/reference/api/introduction) as well as the [Supabase MCP Server](https://supabase.com/docs/guides/ai-tools/mcp).
## From idea to deployment with SOLO Builder
diff --git a/apps/www/_blog/2026-01-15-read-replicas-vs-bigger-compute.mdx b/apps/www/_blog/2026-01-15-read-replicas-vs-bigger-compute.mdx
index 0e626148e93..1dd409fa8ec 100644
--- a/apps/www/_blog/2026-01-15-read-replicas-vs-bigger-compute.mdx
+++ b/apps/www/_blog/2026-01-15-read-replicas-vs-bigger-compute.mdx
@@ -116,7 +116,7 @@ Supabase offers [compute tiers](/docs/guides/platform/compute-and-disk) from Mic
Before scaling hardware, check that your queries use indexes effectively. An index is like the index at the back of a book. Instead of reading every page to find a topic, you look it up in the index and jump straight to the right page. Postgres works the same way. Without an index, Postgres reads every row in a table to find matching data. This is called a sequential scan. With an index, Postgres looks up which rows match and jumps directly to them. The difference can be dramatic: a query that takes 30 seconds without an index might take 30 milliseconds with one.
-Run `EXPLAIN ANALYZE` on slow queries to see if Postgres is using indexes or doing sequential scans. If you see "Seq Scan" on a large table, you probably need an index. The [Database Advisor](/docs/guides/database/database-advisors) in your Supabase Dashboard can also identify missing indexes and other performance issues automatically.
+Run `EXPLAIN ANALYZE` on slow queries to see if Postgres is using indexes or doing sequential scans. If you see "Seq Scan" on a large table, you probably need an index. The [Database Advisor](/docs/guides/observability/advisors) in your Supabase Dashboard can also identify missing indexes and other performance issues automatically.
**Quick index guidelines:**
diff --git a/apps/www/_blog/2026-01-21-postgres-best-practices-for-ai-agents.mdx b/apps/www/_blog/2026-01-21-postgres-best-practices-for-ai-agents.mdx
index bceb83637a3..dad9f1127a2 100644
--- a/apps/www/_blog/2026-01-21-postgres-best-practices-for-ai-agents.mdx
+++ b/apps/www/_blog/2026-01-21-postgres-best-practices-for-ai-agents.mdx
@@ -14,7 +14,7 @@ date: '2026-01-21'
toc_depth: 2
---
-We are releasing a series of Agent Skills for [Postgres Best Practices](https://github.com/supabase/agent-skills) to teach AI agents how to write better Postgres code. AI coding agents are good at writing code. They struggle with writing _correct_ code for systems they don't understand.
+We are releasing a series of [Agent Skills](/docs/guides/ai-tools/ai-skills) for [Postgres Best Practices](https://github.com/supabase/agent-skills) to teach AI agents how to write better Postgres code. AI coding agents are good at writing code. They struggle with writing _correct_ code for systems they don't understand.
Postgres is one of those systems. It has decades of features, edge cases, and performance characteristics that matter in production. An agent might generate a query that works but creates a full table scan. It might suggest an index that makes writes slower. It might miss Row Level Security entirely.
@@ -120,7 +120,7 @@ Our support team, database advisors, and documentation already contain this know
## How this fits with the Supabase MCP server
-If you've used the [Supabase MCP server](https://supabase.com/docs/guides/getting-started/mcp), you know it lets AI agents connect directly to your Supabase project. Agents can create tables, run queries, manage schemas, and configure settings through natural language.
+If you've used the [Supabase MCP server](https://supabase.com/docs/guides/ai-tools/mcp), you know it lets AI agents connect directly to your Supabase project. Agents can create tables, run queries, manage schemas, and configure settings through natural language.
The MCP server gives agents the _ability_ to work with your database. These best practices teach them to do it _correctly_.
diff --git a/apps/www/_blog/2026-01-27-supabase-privatelink-available.mdx b/apps/www/_blog/2026-01-27-supabase-privatelink-available.mdx
index 00c27885be8..2828c713bbc 100644
--- a/apps/www/_blog/2026-01-27-supabase-privatelink-available.mdx
+++ b/apps/www/_blog/2026-01-27-supabase-privatelink-available.mdx
@@ -49,7 +49,7 @@ PrivateLink is not necessary for every use case. If you're building a side proje
Supabase PrivateLink is in Beta with some constraints:
- **AWS environments required.** This initial release supports connections to AWS VPCs via PrivateLink. Your workloads need to run in AWS to use PrivateLink.
-- **Database connections only.** PrivateLink works for Postgres and PgBouncer connections. It does not cover the Supabase API, Storage, Auth, or Realtime services. Those still use public endpoints. To establish PrivateLink with a Read Replica, reach out to your account rep.
+- **Database connections only.** PrivateLink works for Postgres and PgBouncer connections. It does not cover the Supabase API, Storage, Auth, or Realtime services. Those still use public endpoints. To establish PrivateLink with a [Read Replica](/docs/guides/platform/read-replicas), reach out to your account rep.
- **Same region required.** Your AWS VPC must be in the same region as your Supabase project.
- **Team or Enterprise plan required.** PrivateLink is available on Team and Enterprise plans.
diff --git a/apps/www/_blog/2026-02-03-supabase-is-now-an-official-claude-connector.mdx b/apps/www/_blog/2026-02-03-supabase-is-now-an-official-claude-connector.mdx
index afcb6ea4b8b..51cef4da1c7 100644
--- a/apps/www/_blog/2026-02-03-supabase-is-now-an-official-claude-connector.mdx
+++ b/apps/www/_blog/2026-02-03-supabase-is-now-an-official-claude-connector.mdx
@@ -17,7 +17,7 @@ toc_depth: 2
The Supabase MCP server is now listed on Claude's official connectors. Connect your Supabase projects to Claude and manage your entire database infrastructure by telling Claude what you need.
-With the Supabase MCP server, you can execute SQL queries, modify schemas, deploy edge functions, manage branches, and troubleshoot your projects without leaving your conversation with Claude.
+With the Supabase MCP server, you can execute SQL queries, modify schemas, deploy edge functions, manage [branches](/docs/guides/deployment/branching), and troubleshoot your projects without leaving your conversation with Claude.
Ask Claude to check security advisors on your project and fix any issues. Request a schema change and Claude executes it. Deploy an edge function with a single prompt.
@@ -52,4 +52,4 @@ The connector works on all Supabase plans and all paid Claude plans (Pro, Team,
If you don't have a Supabase account yet, start your project for free at [supabase.com](https://supabase.com/). Then connect it to Claude and manage your projects by describing what you need.
-Read the documentation at [supabase.com/docs/guides/getting-started/mcp](https://supabase.com/docs/guides/getting-started/mcp).
+Read the [documentation](https://supabase.com/docs/guides/ai-tools/mcp) to learn more.
diff --git a/apps/www/_blog/2026-02-04-hydra-joins-supabase.mdx b/apps/www/_blog/2026-02-04-hydra-joins-supabase.mdx
index b0d6d2cb938..416b713462e 100644
--- a/apps/www/_blog/2026-02-04-hydra-joins-supabase.mdx
+++ b/apps/www/_blog/2026-02-04-hydra-joins-supabase.mdx
@@ -22,7 +22,7 @@ Hydra co-developed [`pg_duckdb`](https://github.com/duckdb/pg_duckdb), a popular
Joe's work on Hydra pioneered the modern lakebase architecture before most even considered it possible.
-Last year, Supabase started looking at warehousing, announcing Analytics Buckets to store data in Iceberg format in S3. This year, Hydra and `pg_duckdb` will make it easier than ever to get fast analytics on large data volumes in Postgres.
+Last year, Supabase started looking at warehousing, announcing [Analytics Buckets](/docs/guides/storage/analytics/introduction) to store data in Iceberg format in S3. This year, Hydra and `pg_duckdb` will make it easier than ever to get fast analytics on large data volumes in Postgres.
Joe will oversee our Open Warehouse Architecture initiative and help push our Postgres + Analytics roadmap forward.
diff --git a/apps/www/_blog/2026-02-06-x-twitter-oauth-2-provider.mdx b/apps/www/_blog/2026-02-06-x-twitter-oauth-2-provider.mdx
index 3faf08ee7f1..0c3ad560263 100644
--- a/apps/www/_blog/2026-02-06-x-twitter-oauth-2-provider.mdx
+++ b/apps/www/_blog/2026-02-06-x-twitter-oauth-2-provider.mdx
@@ -12,7 +12,7 @@ date: '2026-02-06'
toc_depth: 2
---
-You can now add "Sign in with X" to your application using the new **X / Twitter (OAuth 2.0)** provider in Supabase Auth.
+You can now add "Sign in with X" to your application using the new **X / Twitter (OAuth 2.0)** provider in [Supabase Auth](/auth).
## What's new
diff --git a/apps/www/_blog/2026-03-05-log-drains-now-available-on-pro.mdx b/apps/www/_blog/2026-03-05-log-drains-now-available-on-pro.mdx
index 97571a2f737..5bc2381e95e 100644
--- a/apps/www/_blog/2026-03-05-log-drains-now-available-on-pro.mdx
+++ b/apps/www/_blog/2026-03-05-log-drains-now-available-on-pro.mdx
@@ -59,7 +59,7 @@ Send logs to Sentry. Search and filter Supabase logs next to your application er
Sentry recently launched their Structured Logs product with trace-connected logging. When you send Supabase logs to Sentry, your database errors appear in the same trace as your frontend exceptions. You can follow a slow query from the user-facing error it caused all the way back to the Postgres execution. This is particularly valuable if you already use Sentry for error tracking and want a unified debugging experience.
-[Sentry setup guide](/docs/guides/platform/log-drains#sentry)
+[Sentry setup guide](/docs/guides/observability/log-drains#sentry)
### Grafana Loki
@@ -67,7 +67,7 @@ Send logs to Grafana Loki. Query them with LogQL in your existing Grafana dashbo
Loki works well for teams running Grafana for infrastructure monitoring. You can create alerts on specific error patterns, build log-based metrics for SLOs, and correlate database events with system metrics like CPU and memory. Stream labels automatically include the log source, so filtering by Postgres, Auth, Storage, or Edge Functions requires no additional configuration.
-[Loki setup guide](/docs/guides/platform/log-drains#grafana-loki)
+[Loki setup guide](/docs/guides/observability/log-drains#loki)
### Datadog
@@ -75,7 +75,7 @@ Send logs to Datadog. Use Log Management for search and dashboards. Connect logs
Datadog excels at anomaly detection and ML-powered alerting. You can configure monitors that trigger when Postgres error rates spike or when auth failures exceed normal patterns. The integration works especially well for teams that want to trace slow API calls from their frontend through Supabase and into the database, seeing exactly where latency accumulates.
-[Datadog setup guide](/docs/guides/platform/log-drains#datadog)
+[Datadog setup guide](/docs/guides/observability/log-drains#datadog)
### AWS S3
@@ -83,7 +83,7 @@ Send logs to S3 for low-cost archival. Query historical data with Athena when yo
S3 is the most economical option for long-term retention. Store years of logs for pennies per gigabyte. This destination is useful for compliance requirements, post-incident analysis, or organizations that want to own their log data without paying for real-time indexing they rarely use.
-[S3 setup guide](/docs/guides/platform/log-drains#amazon-s3)
+[S3 setup guide](/docs/guides/observability/log-drains#amazon-s3)
### Axiom
@@ -91,7 +91,7 @@ Send logs to Axiom for fast searches across high-volume data without expensive i
Axiom handles bursty, high-volume workloads well. If you run many Edge Functions or have database traffic that spikes unpredictably, Axiom provides real-time search without the per-GB costs adding up as quickly as traditional SIEM tools.
-[Axiom setup guide](/docs/guides/platform/log-drains#axiom)
+[Axiom setup guide](/docs/guides/observability/log-drains#axiom)
### Generic HTTP endpoint
@@ -99,7 +99,7 @@ Send logs to any HTTP endpoint when you need full control or when we do not have
You can point logs at your own Edge Function to transform, filter, or route them. Some teams use this to enrich logs with business context before forwarding to a final destination. Others use it to split logs between multiple tools based on severity or source type.
-[Generic HTTP endpoint setup guide](/docs/guides/platform/log-drains#generic-http-endpoint)
+[Generic HTTP endpoint setup guide](/docs/guides/observability/log-drains#generic-http-endpoint)
## How it works
@@ -120,11 +120,11 @@ Supabase sends logs in small batches over HTTP. Your vendor stores and indexes t
- $0.20 per million events
- $0.09 per GB egress
-For full billing details, see the [usage guide](/docs/guides/platform/log-drains#pricing).
+For full billing details, see the [usage guide](/docs/guides/observability/log-drains#pricing).
## Getting started
Read the log drains documentation, select a destination, and set up your first drain:
-- [Log drains documentation](/docs/guides/platform/log-drains)
-- [Usage and billing guide](/docs/guides/platform/log-drains#pricing)
+- [Log drains documentation](/docs/guides/observability/log-drains)
+- [Usage and billing guide](/docs/guides/observability/log-drains#pricing)
diff --git a/apps/www/_blog/2026-03-05-supabase-storage-performance-security-reliability-updates.mdx b/apps/www/_blog/2026-03-05-supabase-storage-performance-security-reliability-updates.mdx
index 7d5afd57f10..69a8a70728d 100644
--- a/apps/www/_blog/2026-03-05-supabase-storage-performance-security-reliability-updates.mdx
+++ b/apps/www/_blog/2026-03-05-supabase-storage-performance-security-reliability-updates.mdx
@@ -15,7 +15,7 @@ imgThumb: 'https://zhfonblqamxferhoguzj.supabase.co/functions/v1/generate-og?tem
toc_depth: 3
---
-Today, we're shipping a large set of updates to Supabase Storage that improve performance at scale, close security vulnerabilities, and reduce the most common causes of support issues. These changes affect every project using Storage, and they are live in all regions now.
+Today, we're shipping a large set of updates to [Supabase Storage](/storage) that improve performance at scale, close security vulnerabilities, and reduce the most common causes of support issues. These changes affect every project using Storage, and they are live in all regions now.
Storage has grown a lot. Projects now hold tens of millions of objects, and that scale exposed real problems: write performance degraded under concurrent uploads, certain SQL patterns could accidentally orphan objects, and a path traversal vulnerability existed in the file backend. We knew about these problems from support tickets and our own benchmarks. This release fixes all of them.
@@ -88,4 +88,4 @@ These changes are live for all projects. No code changes are required.
- [Storage documentation](https://supabase.com/docs/guides/storage)
- [Start a new project](https://supabase.com/dashboard)
-- [Self-hosting Storage](https://supabase.com/docs/guides/self-hosting/storage)
+- [Self-hosting Storage](https://supabase.com/docs/guides/self-hosting/storage/config)
diff --git a/apps/www/_blog/2026-03-19-supabase-joins-the-stripe-projects-developer-preview.mdx b/apps/www/_blog/2026-03-19-supabase-joins-the-stripe-projects-developer-preview.mdx
index 70575cd1219..f7724ca13c4 100644
--- a/apps/www/_blog/2026-03-19-supabase-joins-the-stripe-projects-developer-preview.mdx
+++ b/apps/www/_blog/2026-03-19-supabase-joins-the-stripe-projects-developer-preview.mdx
@@ -18,7 +18,7 @@ Supabase is part of the [Stripe Projects](https://projects.dev/) developer previ
AI Agents need a fast way to provision infrastructure, with deterministic steps and real credentials. They cannot click through a browser or guess at setup docs.
-Stripe Projects offers a standard provisioning workflow for AI Agents and humans. One command handles account setup, resource provisioning, and credential delivery. Credentials land in your environment in a format that both humans and agents can use. Your Supabase account and dashboard stay yours and are always accessible.
+[Stripe Projects](/docs/guides/integrations/stripe-projects) offers a standard provisioning workflow for AI Agents and humans. One command handles account setup, resource provisioning, and credential delivery. Credentials land in your environment in a format that both humans and agents can use. Your Supabase account and dashboard stay yours and are always accessible.
We worked closely with Stripe as a co-design partner on the integration spec. That means provisioning a Supabase project through Stripe Projects is deterministic and repeatable. Whether you run it yourself or an agent runs it for you, the steps are the same.
diff --git a/apps/www/_blog/2026-04-01-supabase-docs-over-ssh.mdx b/apps/www/_blog/2026-04-01-supabase-docs-over-ssh.mdx
index 57f49f4d746..56d7be6a601 100644
--- a/apps/www/_blog/2026-04-01-supabase-docs-over-ssh.mdx
+++ b/apps/www/_blog/2026-04-01-supabase-docs-over-ssh.mdx
@@ -19,7 +19,7 @@ We're launching [supabase.sh](https://supabase.sh), a public SSH server that giv
ssh supabase.sh
```
-Coding agents don't know what they don't know. Without access to the latest docs, they guess - and often recommend non-existent APIs, run incorrect CLI commands, or skip steps like enabling RLS. What's the best way to get up-to-date docs in front of them?
+Coding agents don't know what they don't know. Without access to the latest docs, they guess - and often recommend non-existent APIs, run incorrect CLI commands, or skip steps like enabling [RLS](/docs/guides/database/postgres/row-level-security). What's the best way to get up-to-date docs in front of them?
If you watch a coding agent work through a codebase, you'll see the same tools over and over: `grep`, `find`, `ls`, `cat`. These models are trained heavily on bash and they treat the file system as their primary interface for exploration.
@@ -51,7 +51,7 @@ We applied the same pattern to documentation - the files served over SSH are the
## Why bash instead of search?
-The [Supabase MCP server](https://supabase.com/docs/guides/getting-started/mcp) already ships a `search_docs` tool - hybrid keyword and semantic search over our docs. It works, but the agent has to know what to ask for up front. It can't browse, skim, or stumble onto something useful by itself.
+The [Supabase MCP server](https://supabase.com/docs/guides/ai-tools/mcp) already ships a `search_docs` tool - hybrid keyword and semantic search over our docs. It works, but the agent has to know what to ask for up front. It can't browse, skim, or stumble onto something useful by itself.
Bash gives agents the ability to explore without a predefined query. They can list all pages on a topic, search across multiple files at once, and read parts of a page before deciding whether it's relevant. Search is more opaque - the agent asks a question and gets back results without the ability to explore or navigate. With bash, it can `grep` across docs, `cat` specific files, and use `head` and `tail` to skim without bloating its context window.
diff --git a/apps/www/_blog/2026-04-07-supabase-agent-skills.mdx b/apps/www/_blog/2026-04-07-supabase-agent-skills.mdx
index 10c6ac950d5..588c33c067b 100644
--- a/apps/www/_blog/2026-04-07-supabase-agent-skills.mdx
+++ b/apps/www/_blog/2026-04-07-supabase-agent-skills.mdx
@@ -17,7 +17,7 @@ toc_depth: 2
Today we're releasing Supabase Agent Skills, an open-source set of instructions that teach AI coding agents how to build on Supabase correctly. If you use Claude Code, Codex, GitHub Copilot, Cursor, or any of the agents that support [Agent Skills Open Standard](https://agentskills.io/), you can install the skill in one command and get better results on every Supabase task.
-AI agents already know a lot about Supabase. We hit [100k stars on GitHub](https://supabase.com/blog/100000-github-stars), and most models have seen plenty of Supabase code in their training data. But knowing about Supabase and using it correctly are two different things. We kept seeing agents skip RLS policies on exposed schemas, hallucinate CLI commands that don't exist (like `supabase db execute`), create views without `security_invoker = true` (which silently bypasses RLS), and ignore the docs entirely, relying on training data that may be months out of date.
+AI agents already know a lot about Supabase. We hit [100k stars on GitHub](https://supabase.com/blog/100000-github-stars), and most models have seen plenty of Supabase code in their training data. But knowing about Supabase and using it correctly are two different things. We kept seeing agents skip [RLS](/docs/guides/database/postgres/row-level-security) policies on exposed schemas, hallucinate CLI commands that don't exist (like `supabase db execute`), create views without `security_invoker = true` (which silently bypasses RLS), and ignore the docs entirely, relying on training data that may be months out of date.
This is a follow-up to our earlier work on [Postgres best practices for AI agents](https://supabase.com/blog/postgres-best-practices-for-ai-agents). That release focused on general Postgres patterns. Supabase Agent Skills goes further: it covers all Supabase products, encodes security requirements inline, and teaches agents to check the docs before implementing anything.
@@ -91,7 +91,7 @@ Supabase enables agents to access databases through both the MCP server and the
To address this, the skill introduces an opinionated approach to schema management. Instead of relying on migration-based workflows for every change, agents are encouraged to modify the schema directly using the `execute_sql` MCP tool or the `supabase db query` CLI command. This avoids creating a new migration entry for every DDL operation and enables faster iteration during development.
-Once the agent determines that the schema has stabilized, it should run the [Supabase database advisors](https://supabase.com/docs/guides/database/database-advisors) to catch potential security or performance issues early. Only after passing these checks should the agent formalize the changes by committing a migration.
+Once the agent determines that the schema has stabilized, it should run the [Supabase database advisors](https://supabase.com/docs/guides/observability/advisors) to catch potential security or performance issues early. Only after passing these checks should the agent formalize the changes by committing a migration.
<Admonition type="caution">
@@ -202,7 +202,7 @@ Claude Code users can also install as a plugin:
claude plugin marketplace add supabase/agent-skills
```
-- [Supabase Agent Skills Docs](https://supabase.com/docs/guides/getting-started/ai-skills)
+- [Supabase Agent Skills Docs](https://supabase.com/docs/guides/ai-tools/ai-skills)
- [GitHub repo](https://github.com/supabase/agent-skills)
Found something the skill should cover? [Open an issue](https://github.com/supabase/agent-skills/issues) on the repo. We read each one.
diff --git a/apps/www/_blog/2026-04-08-custom-oauth-oidc-providers.mdx b/apps/www/_blog/2026-04-08-custom-oauth-oidc-providers.mdx
index 1dae3261348..a90077e19ef 100644
--- a/apps/www/_blog/2026-04-08-custom-oauth-oidc-providers.mdx
+++ b/apps/www/_blog/2026-04-08-custom-oauth-oidc-providers.mdx
@@ -15,9 +15,9 @@ date: '2026-04-08'
toc_depth: 2
---
-Supabase Auth ships with over 20 built-in social providers: Google, GitHub, Apple, and more. But what about your company's SAML-to-OIDC bridge? A regional identity provider required for compliance? Your self-hosted GitHub Enterprise? Until now, if your identity provider wasn't on the built-in list, you were stuck.
+[Supabase Auth](/auth) ships with over 20 built-in social providers: Google, GitHub, Apple, and more. But what about your company's SAML-to-OIDC bridge? A regional identity provider required for compliance? Your self-hosted GitHub Enterprise? Until now, if your identity provider wasn't on the built-in list, you were stuck.
-Today we're launching **Custom OIDC Providers**, letting you connect any standards-compliant OpenID Connect identity provider to your Supabase project. Once configured, custom providers work just like built-in ones: same sign-in flow, same client libraries, same RLS enforcement.
+Today we're launching **Custom OIDC Providers**, letting you connect any standards-compliant OpenID Connect identity provider to your Supabase project. Once configured, custom providers work just like built-in ones: same sign-in flow, same client libraries, same [RLS](/docs/guides/database/postgres/row-level-security) enforcement.
## Why We Built This
diff --git a/apps/www/_blog/2026-04-14-stripe-sync-engine-transfer.mdx b/apps/www/_blog/2026-04-14-stripe-sync-engine-transfer.mdx
index b4bdeda76bd..d247813753c 100644
--- a/apps/www/_blog/2026-04-14-stripe-sync-engine-transfer.mdx
+++ b/apps/www/_blog/2026-04-14-stripe-sync-engine-transfer.mdx
@@ -24,7 +24,7 @@ In December 2025, we announced a one-click integration that brought the Stripe S
Stripe engineers contributed directly to the repo: incremental sync using cursor-based pagination, JSONB storage with generated columns, multi-account support for [Stripe Connect](https://stripe.com/connect) platforms, and a new CLI with proper event ordering.
-A key part of that collaboration was Stripe's work on automatic, incremental backfilling using Supabase Cron and Queue. This is what made it possible to ingest all of your existing Stripe data into Postgres reliably and at scale, and what unlocked the dashboard integration.
+A key part of that collaboration was Stripe's work on automatic, incremental backfilling using [Supabase Cron](/docs/guides/cron) and [Queue](/docs/guides/queues). This is what made it possible to ingest all of your existing Stripe data into Postgres reliably and at scale, and what unlocked the dashboard integration.
Both teams kept iterating after launch on reliability, install flows, and expanded Stripe object support. The result is a more stable, more capable integration than either team would have shipped alone.
diff --git a/apps/www/_blog/2026-05-04-branching-without-git-is-now-the-default.mdx b/apps/www/_blog/2026-05-04-branching-without-git-is-now-the-default.mdx
index 9d58ceb026c..d373291cb1b 100644
--- a/apps/www/_blog/2026-05-04-branching-without-git-is-now-the-default.mdx
+++ b/apps/www/_blog/2026-05-04-branching-without-git-is-now-the-default.mdx
@@ -18,7 +18,7 @@ Branching without Git is now the default for all Supabase projects.
Supabase has supported database branching through a git-based workflow since [Launch Week X](https://supabase.com/blog/supabase-branching). That workflow connects your GitHub repo to Supabase, tracks migrations in version control, and creates preview branches automatically when you open a pull request. It works well for teams that manage their database schema as code. But it requires a GitHub connection, which rules out anyone who doesn't work that way.
-[Branching 2.0](https://supabase.com/blog/branching-2-0) removed that requirement. You create a branch from the dashboard, make changes using the SQL Editor or Table Editor, review a schema diff, and merge. No git configuration required. It shipped behind a feature preview. Today, that preview is gone.
+[Branching 2.0](https://supabase.com/blog/branching-2-0) removed that requirement. You create a branch from the dashboard, make changes using the [SQL Editor](/features/sql-editor) or Table Editor, review a schema diff, and merge. No git configuration required. It shipped behind a feature preview. Today, that preview is gone.
Branching without Git is on by default for every project. It adds a second path for developers who want to iterate on their schema without setting up a Git integration. Both approaches are fully supported, and you can switch between them or use them together. If you're already using git-based branching, nothing changes.
@@ -91,7 +91,7 @@ pg-delta is alpha software. If you discover any bugs related to diff review, ple
## Built for AI workflows
-Every branch created through the Supabase MCP server uses dashboard branching automatically. When an AI tool needs to iterate on your database schema, it can create a branch, make changes, and merge, all without touching git. The branch exists for as long as the agent needs it and gets cleaned up when the work is done.
+Every branch created through the [Supabase MCP server](/docs/guides/ai-tools/mcp) uses dashboard branching automatically. When an AI tool needs to iterate on your database schema, it can create a branch, make changes, and merge, all without touching git. The branch exists for as long as the agent needs it and gets cleaned up when the work is done.
## Getting started
diff --git a/apps/www/_blog/2026-05-06-introducing-supabase-server.mdx b/apps/www/_blog/2026-05-06-introducing-supabase-server.mdx
index 4f1a7776bb2..86f5061778e 100644
--- a/apps/www/_blog/2026-05-06-introducing-supabase-server.mdx
+++ b/apps/www/_blog/2026-05-06-introducing-supabase-server.mdx
@@ -15,9 +15,9 @@ imgThumb: 'introducing-supabase-server/thumb.png'
toc_depth: 2
---
-Today we're releasing `@supabase/server` in public beta.
+Today we're releasing [`@supabase/server`](https://supabase.com/docs/reference/server) in public beta.
-This is a new package that handles auth verification, client setup, request context, and common server-side boilerplate for you. It works across Edge Functions, Vercel Functions, Cloudflare Workers, Hono and Bun.
+This is a new package that handles auth verification, client setup, request context, and common server-side boilerplate for you. It works across [Edge Functions](/docs/guides/functions), Vercel Functions, Cloudflare Workers, Hono and Bun.
<div className="video-container">
<iframe
@@ -34,7 +34,7 @@ We anonymously analyzed 25,000 deployed Edge Functions and saw the same pattern
Most functions needed to:
- Create a Supabase client with `SUPABASE_ANON_KEY`
-- Create another admin client with `SUPABASE_SERVICE_ROLE_KEY` that can bypass Row Level Security
+- Create another admin client with `SUPABASE_SERVICE_ROLE_KEY` that can bypass [Row Level Security](/docs/guides/database/postgres/row-level-security)
- Verify the JWT
- Parse claims
- Handle CORS
diff --git a/apps/www/_blog/2026-05-08-supabase-is-now-an-official-chatgpt-app.mdx b/apps/www/_blog/2026-05-08-supabase-is-now-an-official-chatgpt-app.mdx
index b5ac1a8f0ef..18cdd1a7296 100644
--- a/apps/www/_blog/2026-05-08-supabase-is-now-an-official-chatgpt-app.mdx
+++ b/apps/www/_blog/2026-05-08-supabase-is-now-an-official-chatgpt-app.mdx
@@ -16,7 +16,7 @@ toc_depth: 2
Supabase is now an official app in ChatGPT. Connect your Supabase projects and manage your entire database infrastructure by telling ChatGPT what you need.
-With the Supabase ChatGPT app, you can execute SQL queries, modify schemas, deploy edge functions, manage branches, and troubleshoot your projects without leaving your conversation with ChatGPT.
+With the Supabase ChatGPT app, you can execute SQL queries, modify schemas, deploy edge functions, manage [branches](/docs/guides/deployment/branching), and troubleshoot your projects without leaving your conversation with ChatGPT.
Ask ChatGPT to check security advisors on your project and fix any issues. Request a schema change and ChatGPT executes it. Deploy an edge function with a single prompt.
@@ -52,4 +52,4 @@ The app works on all Supabase plans and paid ChatGPT plans (Plus, Pro, Team, Ent
If you don't have a Supabase account yet, start your project for free at [supabase.com](https://supabase.com/). Then connect it to ChatGPT and manage your projects by describing what you need.
-Read the documentation at [supabase.com/docs/guides/getting-started/mcp](https://supabase.com/docs/guides/getting-started/mcp).
+Read the documentation at [supabase.com/docs/guides/getting-started/mcp](https://supabase.com/docs/guides/ai-tools/mcp).
diff --git a/apps/www/_blog/2026-05-26-protecting-your-supabase-projects-from-npm-supply-chain-attacks.mdx b/apps/www/_blog/2026-05-26-protecting-your-supabase-projects-from-npm-supply-chain-attacks.mdx
index 59922bbd219..27194bb191c 100644
--- a/apps/www/_blog/2026-05-26-protecting-your-supabase-projects-from-npm-supply-chain-attacks.mdx
+++ b/apps/www/_blog/2026-05-26-protecting-your-supabase-projects-from-npm-supply-chain-attacks.mdx
@@ -17,7 +17,7 @@ toc_depth: 3
There has been a growing trend of supply chain attacks on Node Package Manager (NPM). In addition, we have seen other creative attacks, including a typosquat package named `supabase-javascript` that appeared on npm, copying our name to phish developers. We reported it. npm took it down a few hours later, long enough that the package picked up real downloads.
-If you build on Supabase, this matters to you. Edge Functions pull from npm. The Supabase CLI is on npm. `supabase-js`, `@supabase/ssr`, and `@supabase/server` are all on npm. Any of these is a credential leak waiting for the wrong update to land.
+If you build on Supabase, this matters to you. [Edge Functions](/docs/guides/functions) pull from npm. The [Supabase CLI](/docs/guides/local-development/cli/getting-started) is on npm. `supabase-js`, `@supabase/ssr`, and `@supabase/server` are all on npm. Any of these is a credential leak waiting for the wrong update to land.
This post lays out what we are doing about it and what you should do today.
diff --git a/apps/www/_blog/2026-06-04-multigres-v0-1-alpha.mdx b/apps/www/_blog/2026-06-04-multigres-v0-1-alpha.mdx
index cbb130de63c..a331942521f 100644
--- a/apps/www/_blog/2026-06-04-multigres-v0-1-alpha.mdx
+++ b/apps/www/_blog/2026-06-04-multigres-v0-1-alpha.mdx
@@ -21,7 +21,7 @@ This is an open-source-only release. Multigres for Supabase is coming soon.
Multigres is a scalable operating system for Postgres: it holistically manages your Postgres instances and gives you sharding, connection pooling, automatic failover, and backup orchestration.
-Postgres at scale is operationally complex: You need to manage read replicas, failovers, connection limits, backups, and more. Multigres handles these chores as a single cohesive system. And when the time comes to scale, Multigres will help you shard your database and scale it horizontally.
+Postgres at scale is operationally complex: You need to manage [read replicas](/docs/guides/platform/read-replicas), failovers, connection limits, backups, and more. Multigres handles these chores as a single cohesive system. And when the time comes to scale, Multigres will help you shard your database and scale it horizontally.
The v0.1 alpha introduces advanced connection pooling, automatic failovers, and a Kubernetes operator for deployment.
diff --git a/apps/www/_blog/2026-06-04-supabase-series-f.mdx b/apps/www/_blog/2026-06-04-supabase-series-f.mdx
index 8ed1c52c877..42fc04584e6 100644
--- a/apps/www/_blog/2026-06-04-supabase-series-f.mdx
+++ b/apps/www/_blog/2026-06-04-supabase-series-f.mdx
@@ -24,11 +24,11 @@ The round is for three things:
Today we're releasing [Multigres v0.1 alpha](/blog/multigres-v0-1-alpha). It’s open source and self-hostable.
-Postgres is hard to run at scale. Multigres is a scalable operating system for Postgres that provides high availability and operational simplicity. In a future release it will provide Vitess-grade horizontal scaling.
+Postgres is hard to run at scale. [Multigres](https://supabase.com/docs/guides/database/multigres) is a scalable operating system for Postgres that provides high availability and operational simplicity. In a future release it will provide Vitess-grade horizontal scaling.
The alpha status is to signal that it’s ready to try, but not yet production-ready. We’ll get there in a few months. If you’re running a large Postgres workload you can [apply to be a Multigres partner](https://supabase.link/mg-partner) and help shape the direction of Multigres.
-Multigres will be available on the platform when it moves out of alpha. Together with our work on OrioleDB (targeting production-readiness this year), we believe that we will have a complete Postgres solution that solves many hairy Postgres problems, including bloat, connection pooling, and Jepsen-level high availability. Sharding is also on the menu - we'll share more details later.
+Multigres will be available on the platform when it moves out of alpha. Together with our work on [OrioleDB](/features/orioledb) (targeting production-readiness this year), we believe that we will have a complete Postgres solution that solves many hairy Postgres problems, including bloat, connection pooling, and Jepsen-level high availability. Sharding is also on the menu - we'll share more details later.
## Supabase growth
diff --git a/apps/www/_blog/2026-06-30-agentic-coding-on-supabase-with-opencode.mdx b/apps/www/_blog/2026-06-30-agentic-coding-on-supabase-with-opencode.mdx
index a97aa18063e..7127af128d4 100644
--- a/apps/www/_blog/2026-06-30-agentic-coding-on-supabase-with-opencode.mdx
+++ b/apps/www/_blog/2026-06-30-agentic-coding-on-supabase-with-opencode.mdx
@@ -17,7 +17,7 @@ toc_depth: 2
The OpenCode integration for Supabase is now available.
-Type `/supabase`, authenticate, and your agent can work with Supabase account/project management APIs plus bundled Supabase skills. For database, Edge Functions, logs, and other project-scoped capabilities, the plugin guides users through connecting Supabase MCP. _Requires OpenCode 1.3.4 or later._
+Type `/supabase`, authenticate, and your agent can work with Supabase account/project management APIs plus bundled Supabase skills. For database, Edge Functions, logs, and other project-scoped capabilities, the plugin guides users through connecting [Supabase MCP](/docs/guides/ai-tools/mcp). _Requires OpenCode 1.3.4 or later._
[OpenCode](https://opencode.ai/) is an open source AI coding agent with more than 180,000 GitHub stars and 7.5M monthly active users. It runs in your terminal, IDE, or desktop, supports 75+ LLM providers, and lets you run multiple agents in parallel on the same project.
@@ -31,7 +31,7 @@ Once connected, the integration can:
- List your Supabase organizations and projects
- Create new Supabase projects from your coding session
- Open the Supabase MCP setup flow for a chosen project
-- Bundle Supabase agent skills so your agent gets Supabase-specific guidance without a separate install step
+- Bundle Supabase [agent skills](/docs/guides/ai-tools/ai-skills) so your agent gets Supabase-specific guidance without a separate install step
<div className="video-container">
<iframe
diff --git a/apps/www/_blog/2026-07-09-searchable-field-level-encryption-with-cipherstash.mdx b/apps/www/_blog/2026-07-09-searchable-field-level-encryption-with-cipherstash.mdx
index 5705bf419a0..fc1f8c3c32a 100644
--- a/apps/www/_blog/2026-07-09-searchable-field-level-encryption-with-cipherstash.mdx
+++ b/apps/www/_blog/2026-07-09-searchable-field-level-encryption-with-cipherstash.mdx
@@ -15,7 +15,7 @@ date: '2026-07-09T10:00:00'
toc_depth: 2
---
-The [CipherStash integration](https://supabase.com/partners/integrations/cipherstash?utm_source=supabase_announcement_post&utm_medium=blog&utm_campaign=launch) for Supabase is now available.
+The [CipherStash integration](https://supabase.com/partners/catalog/cipherstash?utm_source=supabase_announcement_post&utm_medium=blog&utm_campaign=launch) for Supabase is now available.
[CipherStash](https://cipherstash.com/?utm_source=supabase_announcement_post&utm_medium=blog&utm_campaign=launch) is a Data Level Access Control (DLAC) platform for applications built on Postgres. DLAC extends traditional access control, which typically operates at the row or table level, down to individual encrypted values, so policies are enforced at decryption rather than at the query layer.
@@ -56,4 +56,4 @@ For cases where the SDK isn't a fit, such as analytics jobs, admin tooling, back
## Get started
-→ [Add CipherStash to your Supabase project](https://supabase.com/partners/integrations/cipherstash?utm_source=supabase_announcement_post&utm_medium=blog&utm_campaign=launch)
+→ [Add CipherStash to your Supabase project](https://supabase.com/partners/catalog/cipherstash?utm_source=supabase_announcement_post&utm_medium=blog&utm_campaign=launch)
diff --git a/apps/www/_blog/2026-07-16-unified-logs-open-beta.mdx b/apps/www/_blog/2026-07-16-unified-logs-open-beta.mdx
index e13cdc6de2f..d4e715fe523 100644
--- a/apps/www/_blog/2026-07-16-unified-logs-open-beta.mdx
+++ b/apps/www/_blog/2026-07-16-unified-logs-open-beta.mdx
@@ -45,7 +45,7 @@ Click a row to open the detail panel. Instead of a wall of JSON, you see the req
## Send logs anywhere
-Unified Logs is for debugging inside the dashboard. When you want to keep logs long term or pull them into your own observability tooling, set up a [Log Drain](https://supabase.com/docs/guides/platform/log-drains) and forward events to the destination of your choice.
+Unified Logs is for debugging inside the dashboard. When you want to keep logs long term or pull them into your own observability tooling, set up a [Log Drain](https://supabase.com/docs/guides/observability/log-drains) and forward events to the destination of your choice.
## Try it
diff --git a/apps/www/_blog/2026-07-21-supabase-pipelines-public-alpha.mdx b/apps/www/_blog/2026-07-21-supabase-pipelines-public-alpha.mdx
index 5c8369322cb..4723bb33e77 100644
--- a/apps/www/_blog/2026-07-21-supabase-pipelines-public-alpha.mdx
+++ b/apps/www/_blog/2026-07-21-supabase-pipelines-public-alpha.mdx
@@ -16,11 +16,11 @@ toc_depth: 2
> **Update: October 2, 2026.** BigQuery, ClickHouse, DuckLake, and Snowflake are now available in public alpha. The destination early-access form has been retired. To get started, see the [destination guides](/docs/guides/database/replication#supported-destinations). The original announcement follows.
-Today we're moving **Supabase Pipelines** into public alpha. The biggest addition is schema change support: Pipelines can now detect supported schema changes in your source tables and apply them to the destination automatically. This release also brings a faster initial sync and a new destination request form for ClickHouse, Snowflake, and DuckLake.
+Today we're moving [**Supabase Pipelines**](/features/supabase-pipelines) into public alpha. The biggest addition is schema change support: Pipelines can now detect supported schema changes in your source tables and apply them to the destination automatically. This release also brings a faster initial sync and a new destination request form for ClickHouse, Snowflake, and DuckLake.
Supabase Pipelines replicates your Supabase Postgres data to external analytical systems in near real time. It is powered by [Supabase ETL](https://github.com/supabase/etl), our open source change-data-capture pipeline written in Rust. Supabase ETL reads changes from Postgres through logical replication, copies existing table data, streams inserts, updates, deletes, and truncates, and writes them to your destination.
-The first destination available to everyone in public alpha is **Google BigQuery**.
+The first destination available to everyone in public alpha is [**Google BigQuery**](https://supabase.com/docs/guides/database/replication/pipelines/bigquery).
## Why Supabase Pipelines?
@@ -97,9 +97,9 @@ We want Supabase Pipelines to connect Supabase Postgres to the systems your team
We're opening a [destination request form](https://supabase.com/go/supabase-pipelines-new-destinations) for:
-- ClickHouse
-- Snowflake
-- DuckLake
+- [ClickHouse](https://supabase.com/docs/guides/database/replication/pipelines/clickhouse)
+- [Snowflake](https://supabase.com/docs/guides/database/replication/pipelines/snowflake)
+- [DuckLake](https://supabase.com/docs/guides/database/replication/pipelines/ducklake)
This form helps us prioritize the next destinations based on real use cases: scale, data volume, expected latency, destination setup, and how teams want to query replicated data.
@@ -137,4 +137,4 @@ Supabase Pipelines is available in public alpha on all paid plans, from the Supa
Create a pipeline, choose BigQuery as your destination, select the tables you want to replicate, and start moving your Postgres data into your warehouse.
-To explore the underlying technology, visit the open-source [Supabase ETL repository](https://github.com/supabase/etl). If you want to understand when to use Supabase Pipelines instead of Realtime, read [Realtime or Pipelines? How to choose the right tool](https://supabase.com/blog/realtime-or-etl-how-to-choose-the-right-tool).
+To explore the underlying technology, visit the open-source [Supabase ETL repository](https://github.com/supabase/etl). If you want to understand when to use Supabase Pipelines instead of Realtime, read [Realtime or Pipelines? How to choose the right tool](https://supabase.com/blog/realtime-or-pipelines-how-to-choose-the-right-tool).
diff --git a/apps/www/_blog/2026-07-23-observability-for-every-supabase-project-with-grafana-cloud.mdx b/apps/www/_blog/2026-07-23-observability-for-every-supabase-project-with-grafana-cloud.mdx
index f5e32a66ea8..ce5462bf621 100644
--- a/apps/www/_blog/2026-07-23-observability-for-every-supabase-project-with-grafana-cloud.mdx
+++ b/apps/www/_blog/2026-07-23-observability-for-every-supabase-project-with-grafana-cloud.mdx
@@ -17,7 +17,7 @@ toc_depth: 2
The [Grafana Cloud integration](https://supabase.com/dashboard/project/_/integrations/grafana-cloud/overview?utm_source=supabase-announcement&utm_medium=blog&utm_campaign=supabase_grafana_cloud_one_click_integration_launch) is available in Supabase. You've been able to connect Supabase to Grafana Cloud for years, and now you can connect to it instantly with the push of a button.
-From your Supabase Dashboard, in a single click, you get a fully-configured Grafana Cloud instance with authentication, metric scraping, and a pre-built observability dashboard already set up on any plan, including free.
+From your Supabase Dashboard, in a single click, you get a fully-configured [Grafana Cloud](/docs/guides/observability/metrics/grafana-cloud) instance with authentication, metric scraping, and a pre-built observability dashboard already set up on any plan, including free.
[Grafana Cloud](https://grafana.com/products/cloud/) is the AI-powered open observability cloud built on open source and open standards. Used by developers everywhere, the full-stack observability platform helps you improve the reliability of your applications, resolve incidents quickly, and optimize your telemetry to reduce noise and costs.
@@ -43,7 +43,7 @@ The integration ships with a pre-built Grafana Cloud dashboard for tracking more
- Scheduled and requested checkpoints
- Database size and query stats
-The integration reads from Supabase's [Metrics API](https://supabase.com/docs/guides/telemetry/metrics). It's one place to monitor your entire stack, whether that's your database, your servers, or anything else your team already tracks in Grafana Cloud.
+The integration reads from Supabase's [Metrics API](https://supabase.com/docs/guides/observability/metrics). It's one place to monitor your entire stack, whether that's your database, your servers, or anything else your team already tracks in Grafana Cloud.
The dashboards are [open source](https://github.com/supabase/supabase-grafana) and work the same everywhere. The same dashboard definitions power self-hosted Grafana, the existing Grafana Cloud integration, and the new one-click setup. No matter how you connect, you're viewing the same dashboards.
diff --git a/apps/www/_blog/2026-07-29-sign-in-with-chatgpt-beta.mdx b/apps/www/_blog/2026-07-29-sign-in-with-chatgpt-beta.mdx
index d5252b8e012..0d4c14417a4 100644
--- a/apps/www/_blog/2026-07-29-sign-in-with-chatgpt-beta.mdx
+++ b/apps/www/_blog/2026-07-29-sign-in-with-chatgpt-beta.mdx
@@ -58,5 +58,5 @@ Supabase is a launch partner for OpenAI's Sign in with ChatGPT beta. Developers
## Get started with Sign in with ChatGPT
-- [Sign in to Supabase with ChatGPT](https://supabase.com/sign-in)
+- [Sign in to Supabase with ChatGPT](https://supabase.com/dashboard/sign-in)
- [Add Supabase in ChatGPT](https://chatgpt.com/apps/supabase/asdk_app_69d3e5ee6a708191baa733f7b8931995)
diff --git a/apps/www/_blog/2026-07-31-introducing-supabase-evals.mdx b/apps/www/_blog/2026-07-31-introducing-supabase-evals.mdx
index 9c7bb6a5a91..337cab783fc 100644
--- a/apps/www/_blog/2026-07-31-introducing-supabase-evals.mdx
+++ b/apps/www/_blog/2026-07-31-introducing-supabase-evals.mdx
@@ -22,7 +22,7 @@ Today we're open sourcing [`supabase/evals`](https://github.com/supabase/evals),
## Why we built this
-Agents are becoming a primary way people build with Supabase, interacting through our CLI, MCP server, agent skills, and docs. We needed a way to understand how agents perform across all of these Supabase surfaces, not just one tool in isolation. By tracking where agents stumble, we can make intentional fixes and verify they hold instead of regressing, and test new features confidently before shipping.
+Agents are becoming a primary way people build with Supabase, interacting through our [CLI](/docs/guides/local-development/cli/getting-started), [MCP server](/docs/guides/ai-tools/mcp), [agent skills](/docs/guides/ai-tools/ai-skills), and docs. We needed a way to understand how agents perform across all of these Supabase surfaces, not just one tool in isolation. By tracking where agents stumble, we can make intentional fixes and verify they hold instead of regressing, and test new features confidently before shipping.
## How we approached it
diff --git a/apps/www/_blog/2026-08-05-postgres-changes-filters-and-column-selection.mdx b/apps/www/_blog/2026-08-05-postgres-changes-filters-and-column-selection.mdx
index a9b394a3f41..caf3c124a64 100644
--- a/apps/www/_blog/2026-08-05-postgres-changes-filters-and-column-selection.mdx
+++ b/apps/www/_blog/2026-08-05-postgres-changes-filters-and-column-selection.mdx
@@ -91,7 +91,7 @@ Realtime [bills on messages](https://supabase.com/docs/guides/realtime/pricing)
## Things to know
- Column selection requires `@supabase/supabase-js` 2.109.0 or newer. The filter changes work with the client library you already have.
-- The columns you list must be selectable by the subscribing role. Row Level Security still applies.
+- The columns you list must be selectable by the subscribing role. [Row Level Security](/docs/guides/database/postgres/row-level-security) still applies.
- DELETE events only carry the row's primary key, so column filters can't be evaluated on deletes.
- Only AND composition shipped in this release. OR is not supported.
diff --git a/apps/www/_blog/2026-10-02-select-2026-build-anything.mdx b/apps/www/_blog/2026-10-02-select-2026-build-anything.mdx
index 36e00f547ba..8abf1a3b469 100644
--- a/apps/www/_blog/2026-10-02-select-2026-build-anything.mdx
+++ b/apps/www/_blog/2026-10-02-select-2026-build-anything.mdx
@@ -71,4 +71,4 @@ We also built a [headless app template](https://supabase.com/library/docs/tansta
- Agent-ready local development: update the [Supabase CLI](https://supabase.com/docs/guides/local-development/cli/getting-started), then add `[experimental]` and `stack = true` to `supabase/config.toml`, or set `SUPABASE_EXPERIMENTAL_STACK=1`.
- Declarative Schemas 2.0: put your schema in `supabase/schemas/*.sql`, run `supabase db schema declarative sync` to generate and apply the migration locally, then run `supabase db push`. Existing projects: add `[experimental.pgdelta]` and `enabled = true` to `supabase/config.toml`. [Docs](https://supabase.com/docs/guides/local-development/declarative-database-schemas).
- Supabase Compute: in private alpha. [Join the waitlist](https://supabase.com/compute).
-- Your app's MCP server: get your project into code with `supabase pull`, then run `npx shadcn@latest add @supabase/mcp-server` from the [MCP server block](https://supabase.com/library/docs/headless/mcp). It needs asymmetric signing keys and the Supabase Auth OAuth server turned on.
+- Your app's MCP server: get your project into code with `supabase pull`, then run `npx shadcn@latest add @supabase/mcp-server` from the [MCP server block](https://supabase.com/library/docs/headless/mcp). It needs asymmetric signing keys and the Supabase Auth [OAuth server](/docs/guides/auth/oauth-server) turned on.
diff --git a/apps/www/_blog/2026-10-02-select-2026-operate-with-confidence.mdx b/apps/www/_blog/2026-10-02-select-2026-operate-with-confidence.mdx
index e0fae3ac57b..8f79e6f1378 100644
--- a/apps/www/_blog/2026-10-02-select-2026-operate-with-confidence.mdx
+++ b/apps/www/_blog/2026-10-02-select-2026-operate-with-confidence.mdx
@@ -29,7 +29,7 @@ For an agent to confidently operate a project:
### query_logs
-Previously your agents were limited in what logs they could access via our MCP. We’ve introduced a new MCP tool that gives your agents raw access to your project logs via SQL, which enables more in-depth and precise investigations.
+Previously your agents were limited in what logs they could access via our [MCP](/docs/guides/ai-tools/mcp). We’ve introduced a new MCP tool that gives your agents raw access to your project logs via SQL, which enables more in-depth and precise investigations.
### More advisor checks
diff --git a/apps/www/_blog/2026-10-02-select-2026-scale-without-limits.mdx b/apps/www/_blog/2026-10-02-select-2026-scale-without-limits.mdx
index 08ba9dcc9ed..b5b8253f854 100644
--- a/apps/www/_blog/2026-10-02-select-2026-scale-without-limits.mdx
+++ b/apps/www/_blog/2026-10-02-select-2026-scale-without-limits.mdx
@@ -14,7 +14,7 @@ imgThumb: 'select-2026-scale-without-limits/thumb.png'
toc_depth: 2
---
-Today at Supabase Select, we announced Multigres for high availability and scalable connection pooling, and OrioleDB for high performance storage. We launched dbarena, an open benchmarks site for comparing managed Postgres providers’ performance results and costs.
+Today at Supabase Select, we announced [Multigres](/blog/multigres-vitess-for-postgres) for high availability and scalable connection pooling, and [OrioleDB](/features/orioledb) for high performance storage. We launched dbarena, an open benchmarks site for comparing managed Postgres providers’ performance results and costs.
Every Supabase project starts with a single Postgres database. As your project grows, vertically upgrading the database’s available RAM & CPU resources can help, but it isn’t a solution to every challenge.
@@ -56,7 +56,7 @@ Many developers are familiar with basic Primary / Standby HA architecture and it
Multigres runs three Postgres nodes across availability zones in one region, so losing one zone doesn't take your database down. You don't need to change your application code to move to Multigres.
-You can also add read replicas and gateways for more read throughput and client connections. During the alpha, our team adds them for you.
+You can also add [read replicas](/docs/guides/platform/read-replicas) and gateways for more read throughput and client connections. During the alpha, our team adds them for you.
Multigres is in private alpha, by invite. It works with Supabase Auth, Storage, and Edge Functions, and it's built for testing during the alpha, not production workloads. [Request access](https://supabase.com/go/multigres-early-access).
diff --git a/apps/www/_blog/2026-10-02-supabase-select-2026-recap.mdx b/apps/www/_blog/2026-10-02-supabase-select-2026-recap.mdx
index ac676a592e5..f51fa4ec393 100644
--- a/apps/www/_blog/2026-10-02-supabase-select-2026-recap.mdx
+++ b/apps/www/_blog/2026-10-02-supabase-select-2026-recap.mdx
@@ -38,7 +38,7 @@ Run web services and agents in any language next to your database, with no limit
### Your app's MCP server
-Let your users connect their own agents to your app. The server runs as an Edge Function next to your data, users sign in through your existing Auth flow, and every tool call runs as that user, with your RLS policies deciding what it can reach. It's separate from the official Supabase MCP server, and it's built on `@supabase/server` and the new Supabase Middleware, which also work on their own in any server code that needs to know who is signed in. [Add the MCP server block](https://supabase.com/library/docs/headless/mcp).
+Let your users connect their own agents to your app. The server runs as an Edge Function next to your data, users sign in through your existing Auth flow, and every tool call runs as that user, with your [RLS](/docs/guides/database/postgres/row-level-security) policies deciding what it can reach. It's separate from the official [Supabase MCP server](/docs/guides/ai-tools/mcp), and it's built on `@supabase/server` and the new Supabase Middleware, which also work on their own in any server code that needs to know who is signed in. [Add the MCP server block](https://supabase.com/library/docs/headless/mcp).
Learn more in [Build anything: Supabase from code, and an MCP server for your app](https://supabase.com/blog/select-2026-build-anything).
diff --git a/apps/www/_blog/2026-10-13-declarative-schemas-2-0-pg-delta.mdx b/apps/www/_blog/2026-10-13-declarative-schemas-2-0-pg-delta.mdx
index 752078253c2..0ca893fdaf7 100644
--- a/apps/www/_blog/2026-10-13-declarative-schemas-2-0-pg-delta.mdx
+++ b/apps/www/_blog/2026-10-13-declarative-schemas-2-0-pg-delta.mdx
@@ -13,7 +13,7 @@ imgThumb: 'select-rewind-2026-declarative-schemas-2-blog/thumb.png'
toc_depth: 2
---
-On October 2 at Supabase Select we shipped Declarative Schemas 2.0. The Supabase CLI now generates migrations with `pg-delta`, a Postgres diff tool we wrote and open sourced, in place of `migra`, the technology behind our original implementation. Generated migrations now include RLS policy changes, grants, view settings, partitions, domains, and objects that extensions manage.
+On October 2 at Supabase Select we shipped Declarative Schemas 2.0. The [Supabase CLI](/docs/guides/local-development/cli/getting-started) now generates migrations with `pg-delta`, a Postgres diff tool we wrote and open sourced, in place of `migra`, the technology behind our original implementation. Generated migrations now include RLS policy changes, grants, view settings, partitions, domains, and objects that extensions manage.
Declarative schemas [first launched in April 2025](https://supabase.com/blog/declarative-schemas). You keep your schema in SQL files under `supabase/schemas/`, edit them, and the CLI writes the migration. In 2.0 that workflow is the same: edit a file, generate the migration, review it, and apply it. New CLI projects get 2.0 by default. Existing projects opt in with one config block.
diff --git a/apps/www/_blog/2026-10-13-ship-changes-to-your-supabase-backend-with-grok-bot.mdx b/apps/www/_blog/2026-10-13-ship-changes-to-your-supabase-backend-with-grok-bot.mdx
index 53d3a612f63..7d1d3f2c992 100644
--- a/apps/www/_blog/2026-10-13-ship-changes-to-your-supabase-backend-with-grok-bot.mdx
+++ b/apps/www/_blog/2026-10-13-ship-changes-to-your-supabase-backend-with-grok-bot.mdx
@@ -14,7 +14,7 @@ imgThumb: '2026-10-13-ship-changes-to-your-supabase-backend-with-grok-bot/thumb.
toc_depth: 2
---
-Supabase is joining the SpaceXAI Partner Network. With Grok Bot connected to Cursor, anyone on your team can request a change in chat, and Cursor builds and runs it against your Supabase backend through the [Supabase MCP server](https://supabase.com/docs/guides/getting-started/mcp).
+Supabase is joining the SpaceXAI Partner Network. With Grok Bot connected to Cursor, anyone on your team can request a change in chat, and Cursor builds and runs it against your Supabase backend through the [Supabase MCP server](https://supabase.com/docs/guides/ai-tools/mcp).
Grok Bot takes a request from the person who needs it, in the place they already work, and hands it to Cursor as scoped engineering work. Cursor writes and runs the code, and through the Supabase MCP server, it can query the database, inspect the schema, read logs, and deploy Supabase Edge Functions, all inside the one Supabase project where the data already lives.
@@ -40,7 +40,7 @@ The person asking doesn't need to know which project holds the answer or which t
## Add a security check to the loop
-Agents already verify their own changes: after an `apply_migration`, 81% of sessions follow up with a query or `list_tables` to confirm the change landed. `get_advisors` goes further and scans the project for issues like tables missing Row Level Security or unindexed foreign keys, which matters when requests can come from anyone and ship automatically.
+Agents already verify their own changes: after an `apply_migration`, 81% of sessions follow up with a query or `list_tables` to confirm the change landed. `get_advisors` goes further and scans the project for issues like tables missing [Row Level Security](/docs/guides/database/postgres/row-level-security) or unindexed foreign keys, which matters when requests can come from anyone and ship automatically.
A simple Cursor rule makes the scan part of every schema change:
@@ -62,5 +62,5 @@ Developers found the Supabase integration on their own, and it consistently rank
## Get started
-- [Connect the Supabase MCP server](https://supabase.com/docs/guides/getting-started/mcp)
+- [Connect the Supabase MCP server](https://supabase.com/docs/guides/ai-tools/mcp)
- New to Supabase? [Start your project for free](https://supabase.com/dashboard), then connect it to Cursor