The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.
TypeScript aialternativeauthdatabasedenoembeddingsexamplefirebasenextjsoauth2pgvectorpostgispostgrespostgresqlpostgrestrealtimesupabasevectorswebsockets
Added a new agency webinar (#43000)
Prashant Sridharan52e2bf63254b
diff --git a/apps/docs/content/guides/database/joins-and-nesting.mdx b/apps/docs/content/guides/database/joins-and-nesting.mdxindex d8fdc4dcfcc..361180a3a6c 100644--- a/apps/docs/content/guides/database/joins-and-nesting.mdx+++ b/apps/docs/content/guides/database/joins-and-nesting.mdx@@ -222,11 +222,11 @@ To filter out parent rows that do not match the related table, use `!inner` on t### What `:` and `!` mean in join syntax-| Syntax | Meaning | Example |-| ---------------------------------- | --------------------------------------------------------------------------------------- | ---------------------------------------- |-| `alias:relation(columns)` | Rename the embedded relation in the response. | `start_scan:scans(id, badge_scan_time)` |-| `relation!inner(columns)` | Use `inner join` behavior for that embedded relation. | `instruments!inner(id, name)` |-| `relation!foreign_key(columns)` | Choose which foreign key relationship to use when multiple foreign keys match the join. | `scans!scan_id_start(id)` |+| Syntax | Meaning | Example |+| ------------------------------- | --------------------------------------------------------------------------------------- | --------------------------------------- |+| `alias:relation(columns)` | Rename the embedded relation in the response. | `start_scan:scans(id, badge_scan_time)` |+| `relation!inner(columns)` | Use `inner join` behavior for that embedded relation. | `instruments!inner(id, name)` |+| `relation!foreign_key(columns)` | Choose which foreign key relationship to use when multiple foreign keys match the join. | `scans!scan_id_start(id)` |### Example data for join types@@ -241,11 +241,11 @@ To filter out parent rows that do not match the related table, use `!inner` on t#### Orchestral sections-| `id` | `name` |-| ---- | ----------- |-| 1 | strings |-| 2 | woodwinds |-| 3 | percussion |+| `id` | `name` |+| ---- | ---------- |+| 1 | strings |+| 2 | woodwinds |+| 3 | percussion |#### Instruments@@ -306,11 +306,13 @@ This query filters on a joined field (`instruments.name`) but still returns all```jsconst { data, error } = await supabase.from('orchestral_sections')- .select(`+ .select(+ `id,name,instruments ( id, name )- `)+ `+ ).eq('instruments.name', 'flute')```@@ -406,9 +408,7 @@ GET https://[REF].supabase.co/rest/v1/orchestral_sections?select=id,name,instrum{"id": 2,"name": "woodwinds",- "instruments": [- { "id": 3, "name": "flute" }- ]+ "instruments": [{ "id": 3, "name": "flute" }]},{"id": 3,@@ -434,11 +434,13 @@ Adding `!inner` filters out parent rows that don't match the joined filter:```jsconst { data, error } = await supabase.from('orchestral_sections')- .select(`+ .select(+ `id,name,instruments!inner ( id, name )- `)+ `+ ).eq('instruments.name', 'flute')```@@ -529,9 +531,7 @@ GET https://[REF].supabase.co/rest/v1/orchestral_sections?select=id,name,instrum{"id": 2,"name": "woodwinds",- "instruments": [- { "id": 3, "name": "flute" }- ]+ "instruments": [{ "id": 3, "name": "flute" }]}]```@@ -552,11 +552,13 @@ Use `joined_table.column` in filters (for example `eq`, `neq`, and `in`):```jsconst { data, error } = await supabase.from('instruments')- .select(`+ .select(+ `id,name,orchestral_sections!inner ( id, name )- `)+ `+ ).eq('orchestral_sections.name', 'woodwinds')```diff --git a/apps/docs/content/guides/platform/read-replicas/getting-started.mdx b/apps/docs/content/guides/platform/read-replicas/getting-started.mdxindex 42dac545148..33e0193ff84 100644--- a/apps/docs/content/guides/platform/read-replicas/getting-started.mdx+++ b/apps/docs/content/guides/platform/read-replicas/getting-started.mdx@@ -17,15 +17,15 @@ Projects must meet these requirements to use Read Replicas:1. Running on AWS.2. Running on at least a [Small compute add-on](/docs/guides/platform/compute-add-ons).- - Read Replicas are started on the same compute instance as the Primary to keep up with changes.+ - Read Replicas are started on the same compute instance as the Primary to keep up with changes.3. Running on Postgres 15+.- - For projects running on older versions of Postgres, you need to [upgrade to the latest platform version](/docs/guides/platform/migrating-and-upgrading-projects#pgupgrade).+ - For projects running on older versions of Postgres, you need to [upgrade to the latest platform version](/docs/guides/platform/migrating-and-upgrading-projects#pgupgrade).4. Not using [legacy logical backups](/docs/guides/platform/backups#point-in-time-recovery)- - Physical backups are automatically enabled if using [Point in time recovery (PITR)](/docs/guides/platform/backups#point-in-time-recovery)+ - Physical backups are automatically enabled if using [Point in time recovery (PITR)](/docs/guides/platform/backups#point-in-time-recovery)## Creating a Read Replicadiff --git a/apps/docs/content/guides/self-hosting/copy-from-platform-s3.mdx b/apps/docs/content/guides/self-hosting/copy-from-platform-s3.mdxindex 2c98be8144f..1665b9aadc6 100644--- a/apps/docs/content/guides/self-hosting/copy-from-platform-s3.mdx+++ b/apps/docs/content/guides/self-hosting/copy-from-platform-s3.mdx@@ -20,7 +20,7 @@ You need:- A working self-hosted Supabase instance with the S3 protocol endpoint enabled - see [Configure S3 Storage](/docs/guides/self-hosting/self-hosted-s3#enable-the-s3-protocol-endpoint)- Your platform project's S3 credentials - generated from the [S3 Configuration](/dashboard/project/_/storage/s3) page- Matching buckets created on your self-hosted instance-{/* supa-mdx-lint-disable-next-line Rule003Spelling */}+ {/* supa-mdx-lint-disable-next-line Rule003Spelling */}- [rclone](https://rclone.org/install/) installed on the machine running the copy## Step 1: Get platform S3 credentials@@ -50,22 +50,24 @@ If you already restored your platform database to self-hosted using the [restoreTo list your platform buckets, connect to your platform database and run:```sql-SELECT id, name, public FROM storage.buckets ORDER BY name;+select id, name, public from storage.buckets order by name;```Then create matching buckets on your self-hosted instance. Connect to your self-hosted database and run:```sql-INSERT INTO storage.buckets (id, name, public)-VALUES+insert into storage.buckets (id, name, public)+values('your-storage-bucket', 'your-storage-bucket', false)-ON CONFLICT (id) DO NOTHING;+on conflict (id) do nothing;```Repeat for each bucket, setting `public` to `true` or `false` as appropriate.{/* supa-mdx-lint-disable-next-line Rule003Spelling */}+## Step 3: Configure rclone+{/* supa-mdx-lint-disable-next-line Rule003Spelling */}Create or edit your rclone configuration file (`~/.config/rclone/rclone.conf`):@@ -139,14 +141,16 @@ Open Studio on your self-hosted instance and browse the storage buckets to confiIf you see `SignatureDoesNotMatch` when connecting to either remote:- **Platform**: Regenerate S3 access keys from your project's Storage Settings. Ensure the endpoint URL includes `/storage/v1/s3`.-{/* supa-mdx-lint-disable-next-line Rule003Spelling */}+ {/* supa-mdx-lint-disable-next-line Rule003Spelling */}- **Self-hosted**: Verify that `REGION`, `S3_PROTOCOL_ACCESS_KEY_ID` and `S3_PROTOCOL_ACCESS_KEY_SECRET` in `.env` file match your rclone config.### Bucket not found+{/* supa-mdx-lint-disable-next-line Rule003Spelling */}If rclone reports that a bucket doesn't exist on the self-hosted side, create it first - see [Step 2](#step-2-create-buckets-on-self-hosted). The S3 protocol does not auto-create buckets on copy.### Timeouts on large files+{/* supa-mdx-lint-disable-next-line Rule003Spelling */}For very large files, increase rclone's timeout:diff --git a/apps/docs/content/guides/self-hosting/self-hosted-s3.mdx b/apps/docs/content/guides/self-hosting/self-hosted-s3.mdxindex 37ada206d74..248746f8670 100644--- a/apps/docs/content/guides/self-hosting/self-hosted-s3.mdx+++ b/apps/docs/content/guides/self-hosting/self-hosted-s3.mdx@@ -6,8 +6,9 @@ subtitle: 'Enable S3-compatible client endpoint and set up an S3 backend for selSelf-hosted Supabase Storage has two independent S3-related features:{/* supa-mdx-lint-disable-next-line Rule003Spelling */}+- **S3 protocol endpoint** - an S3-compatible API that Storage exposes at `/storage/v1/s3`. This allows standard S3 tools like `rclone` and the AWS CLI to interact with your Storage instance.-{/* supa-mdx-lint-disable-next-line Rule003Spelling */}+ {/* supa-mdx-lint-disable-next-line Rule003Spelling */}- **S3 backend** - where Storage keeps data. By default, files are stored on the local filesystem. You can switch to an S3-compatible service (AWS S3, MinIO, etc.) for durability, scalability, or to use existing infrastructure.You can configure either feature independently. For example, you can enable the S3 protocol endpoint to use `rclone` while keeping the default file-based storage, or switch to an S3 backend without enabling the S3 protocol endpoint.@@ -42,7 +43,9 @@ s3://your-storage-bucket )```{/* supa-mdx-lint-disable-next-line Rule003Spelling */}+### Test with rclone+```bash( set -a && \source .env > /dev/null 2>&1 && \@@ -70,7 +73,7 @@ storage:GLOBAL_S3_BUCKET: your-s3-bucket-or-dirnameGLOBAL_S3_ENDPOINT: https://your-s3-endpointGLOBAL_S3_PROTOCOL: https- GLOBAL_S3_FORCE_PATH_STYLE: "true"+ GLOBAL_S3_FORCE_PATH_STYLE: 'true'AWS_ACCESS_KEY_ID: your-access-key-idAWS_SECRET_ACCESS_KEY: your-secret-access-keyREGION: your-region@@ -81,7 +84,9 @@ Depending on your setup, you may need to adjust these values - for example, to u{/* supa-mdx-lint-disable-next-line Rule001HeadingCase */}{/* supa-mdx-lint-disable-next-line Rule003Spelling */}+### Using MinIO+{/* supa-mdx-lint-disable-next-line Rule003Spelling */}An overlay `docker-compose.s3.yml` configuration can be added to enable MinIO container and provide an S3-compatible API for Storage backend:@@ -109,6 +114,7 @@ storage:For AWS S3, you do not need `GLOBAL_S3_ENDPOINT` or `GLOBAL_S3_FORCE_PATH_STYLE` - the Storage S3 client automatically resolves the endpoint from the region and uses virtual-hosted-style URLs, which is what AWS S3 expects. These variables are only needed for non-AWS S3-compatible providers.### S3-compatible providers+{/* supa-mdx-lint-disable-next-line Rule003Spelling */}Use the same configuration as MinIO, but point to your provider's endpoint, e.g.:@@ -124,6 +130,7 @@ storage:## Verify{/* supa-mdx-lint-disable-next-line Rule003Spelling */}+- Open Studio and upload a file to a bucket. List the file using the AWS CLI or `rclone` to confirm the S3 endpoint works.- If using an S3 backend: confirm the file appears in your S3 provider's console.diff --git a/apps/docs/content/guides/telemetry/log-drains.mdx b/apps/docs/content/guides/telemetry/log-drains.mdxindex 94a025230ef..f05a4e6f73f 100644--- a/apps/docs/content/guides/telemetry/log-drains.mdx+++ b/apps/docs/content/guides/telemetry/log-drains.mdx@@ -245,7 +245,6 @@ Ensure the AWS account tied to the Access Key ID has permissions to write to the</Admonition>-## OpenTelemetry protocol (OTLP)Logs are sent to any OTLP-compatible endpoint using the OpenTelemetry Protocol over HTTP with Protocol Buffers encoding.diff --git a/apps/www/_events/2026-03-19-agency-webinar-ai-prototyping-production.mdx b/apps/www/_events/2026-03-19-agency-webinar-ai-prototyping-production.mdxnew file mode 100644index 00000000000..a5cc2c4a718--- /dev/null+++ b/apps/www/_events/2026-03-19-agency-webinar-ai-prototyping-production.mdx@@ -0,0 +1,40 @@+---+title: 'Ship Fast, Stay Safe: AI Prototyping That Survives Production'+meta_title: 'Ship Fast, Stay Safe: AI Prototyping That Survives Production'+subtitle: >-+ Learn how top agencies balance velocity with control when using AI coding tools to build production applications on Supabase+meta_description: >-+ Learn how top agencies balance AI prototyping speed with production safety. Database schema design, RLS policies, validation practices, and client handoff strategies.+type: webinar+onDemand: false+date: '2026-03-19T09:00:00.000-07:00'+timezone: America/Los_Angeles+duration: 45 mins+categories:+ - webinar+main_cta:+ {+ url: 'https://attendee.gotowebinar.com/register/5606981989518150747',+ target: '_blank',+ label: 'Register now',+ }+speakers: 'seth_kramer,dave_wilson'+---++AI coding tools have made prototyping almost instant. Agencies now send working demos to clients within minutes of a kickoff call. But speed creates new risks: databases with no row-level security, permissions that break under load, and prototypes that fall apart the moment they hit production.++Join agency leaders and Supabase as they share how top agencies balance velocity with control. Learn when to let AI move fast, and where experienced developers still need to step in.++## Key takeaways++- Why leading agencies design database schemas and RLS policies before touching the UI++- When to use visual AI builders for speed vs code-first tools for control++- How to prevent AI tools from making breaking changes to production environments++- Lightweight validation practices that preserve velocity without sacrificing safety++- How to hand projects off to clients without handing over production risk++Join us live to participate in the Q&A. Can't make it? We'll send you a link to the recording.diff --git a/apps/www/public/rss.xml b/apps/www/public/rss.xmlindex ee7d8c3ebfc..bd8ffb5024d 100644--- a/apps/www/public/rss.xml+++ b/apps/www/public/rss.xml@@ -4,15 +4,43 @@<link>https://supabase.com</link><description>Latest news from Supabase</description><language>en</language>- <lastBuildDate>Tue, 03 Feb 2026 00:00:00 -0700</lastBuildDate>+ <lastBuildDate>Fri, 13 Feb 2026 00:00:00 -0700</lastBuildDate><atom:link href="https://supabase.com/rss.xml" rel="self" type="application/rss+xml"/><item>+ <guid>https://supabase.com/blog/supabase-incident-on-february-12-2026</guid>+ <title>Supabase incident on February 12, 2026</title>+ <link>https://supabase.com/blog/supabase-incident-on-february-12-2026</link>+ <description>A detailed account of the February 12 outage in us-east-2, what caused it, and the steps we are taking to prevent it from happening again.</description>+ <pubDate>Fri, 13 Feb 2026 00:00:00 -0700</pubDate>+</item>+<item>+ <guid>https://supabase.com/blog/hydra-joins-supabase</guid>+ <title>Hydra joins Supabase</title>+ <link>https://supabase.com/blog/hydra-joins-supabase</link>+ <description>The Hydra team, maintainers of pg_duckdb, is joining Supabase to focus on Postgres + Analytics and Open Warehouse Architecture.</description>+ <pubDate>Tue, 10 Feb 2026 00:00:00 -0700</pubDate>+</item>+<item>+ <guid>https://supabase.com/blog/x-twitter-oauth-2-provider</guid>+ <title>X / Twitter OAuth 2.0 is now available for Supabase Auth</title>+ <link>https://supabase.com/blog/x-twitter-oauth-2-provider</link>+ <description>You can now add "Sign in with X" to your application using the new X / Twitter (OAuth 2.0) provider in Supabase Auth.</description>+ <pubDate>Fri, 06 Feb 2026 00:00:00 -0700</pubDate>+</item>+<item><guid>https://supabase.com/blog/bknd-joins-supabase</guid><title>BKND joins Supabase</title><link>https://supabase.com/blog/bknd-joins-supabase</link><description>Dennis Senn, creator of BKND, is joining Supabase to build a Lite offering for agentic workloads.</description><pubDate>Tue, 03 Feb 2026 00:00:00 -0700</pubDate></item>+<item>+ <guid>https://supabase.com/blog/supabase-is-now-an-official-claude-connector</guid>+ <title>Supabase is now an official Claude connector</title>+ <link>https://supabase.com/blog/supabase-is-now-an-official-claude-connector</link>+ <description>Connect your Supabase projects to Claude and manage your entire database infrastructure by telling Claude what you need.</description>+ <pubDate>Tue, 03 Feb 2026 00:00:00 -0700</pubDate>+</item><item><guid>https://supabase.com/blog/supabase-privatelink-available</guid><title>Supabase PrivateLink is now available</title>