Loading…
Supabase
Open-source backend platform providing PostgreSQL databases, authentication, storage, realtime APIs, and serverless functions.
- 230 posts summarised
- latest
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
From their blog
Latest articles
Getting started with the Supabase .NET SDK
The Supabase .NET SDK provides a single C# client for Auth, Database, Storage, Realtime, and Edge Functions; version 8.0.0 moves serialization to System.Text.Json and adds injectable HttpClient with retry. It also ships a dependency injection package for ASP.NET Core that registers the client as scoped via IHttpClientFactory to pool connections. Models derive from BaseModel with table and column attributes; queries use From () with Where filters, and updates require explicit calls without a change tracker, supporting both model-based and query-builder approaches. Authentication covers email/password, OAuth, magic links, phone, and SSO, with auto-refresh tokens attaching to subsequent requests for Row-Level Security. Setup for ASP.NET Core uses AddSupabase, while other apps construct the client manually and call InitializeAsync; the post also distinguishes publishable and anon keys for client apps from secret and service keys that bypass Row-Level Security.
Introducing the unified Supabase .NET SDK
The Supabase .NET SDK v8 is now available, consolidating all packages under a single repository with a unified version number. Previously, packages like Gotrue, Realtime, and the main package were scattered across multiple repositories with separate versions and lifecycles, making upgrades complex. From v8.0.0, all packages—Gotrue, PostgREST, Realtime, Storage, Functions, and the umbrella package—share the same version, and previous repositories are archived as read-only. The jump from v1.x.x to v8.0.0 was necessary because Realtime was already on v7.x.x, and this ensures lockstep versioning going forward. A new dependency injection extension package registers the Supabase client with the .NET service container and lets IHttpClientFactory manage its HttpClient, starting at v8.0.0 as well. The update switches serialization from Newtonsoft.Json to System.Text.Json, adds configurable retry with backoff, accepts publishable and secret API keys, and targets netstandard2.1, with a migration guide available for breaking changes.
How we made the Supabase Select 2026 badge
Supabase gave every Select 2026 attendee a programmable badge based on the Pimoroni Tufty 2350, with an RP2350 microcontroller, color screen, rechargeable battery, Wi-Fi, Bluetooth, and five buttons. A firmware bug drained all batteries during shipping, requiring bulk charging with 30-port USB hubs in 14 batches over 56 hours and individual firmware updates. The venue Wi-Fi failed, so the schedule was synced via a hotspot, two badges at a time, one minute each, totaling seven hours. Attendees have since repurposed the badge into projects including a live flight tracker, an arcade game about database vacuuming, a food finder app, a music note collection game, and a tiny on-device language model. The post provides resources for hacking the badge: a first-app guide, a Claude Code project kit, a virtual badge, guides for C or Rust firmware, and a contest with Supabase credits and conference passes.
Supabase Select 2026 Recap
Supabase announced a code-first approach at its Select 2026 event, enabling developers to store schema and configuration in code so coding agents can set up and modify projects end to end. Local Supabase now runs as native processes without Docker, allowing multiple instances per directory and compatibility with sandboxes like Claude Code. A new MCP server lets application users connect their own agents, authenticating through existing Auth flows and enforcing row-level security on every tool call. Operational tools include Health Check Advisors for error rates, Database Connections for session management, Explorer notebooks for unified SQL and log queries, and query_logs for agent monitoring. Scaling features encompass Multigres for multi-node Postgres high availability, OrioleDB to avoid table bloat and VACUUM, Supabase Pipelines for near real-time data streaming to analytics platforms, and dbarena for transparent benchmarks.
Scale without limits: Multigres, OrioleDB, and dbarena
At Supabase Select, Supabase announced Multigres for high availability and connection pooling, OrioleDB for high performance storage, and dbarena for transparent benchmarking. Multigres is an open source operating system for Postgres that adds scalable connection pooling and automated multi-node failover using a consensus protocol built on synchronous replication, preventing data loss during failover. OrioleDB replaces Postgres’s heap storage with an undo log-based engine that eliminates bloat, VACUUM overhead, and transaction ID wraparound by using 64-bit transaction IDs, delivering up to 1.8x higher throughput in TPC-C-derived benchmarks. dbarena.com is an open benchmarks site that publishes reproducible performance and cost comparisons across managed Postgres providers including Supabase, Amazon RDS, and Google Cloud SQL, with full methodology and raw data. These tools aim to remove scaling limitations at every layer of Postgres, with all improvements being open source and available to the community.
Operate with confidence
At Supabase Select, Supabase announced tools that let coding agents find production problems, test fixes, and report back, with controls for access and permission. A new MCP tool gives agents raw SQL access to project logs, advisor checks now include health signals for error rates across Data API, Auth, Storage, and Edge Functions, and the database connections view shows sessions, long queries, idle-in-transaction, blocked, and lock holders. Notebooks combine saved database or log queries with markdown notes, can be created in the dashboard via the Assistant, pulled locally with supabase notebooks pull, and pushed with supabase notebooks push, and are found in the new Explorer rolling out through October 12. Updated Skills provide a living document of common health, security, performance, and resource signals for agents to watch for and how to monitor them. Supabase Pipelines, available on paid plans, allow replicating data to BigQuery, ClickHouse, DuckLake, or Snowflake.
Build anything: Supabase from code, and an MCP server for your app
Supabase announced tools at Supabase Select that let coding agents manage backend configuration and deployment from code, eliminating the need for dashboard-only changes. Declarative Schemas 2.0 allows agents to edit SQL files as the source of truth, with pg-delta generating migrations, while config.toml holds settings like auth providers that can be pulled back from the dashboard. Local development now runs as native processes without Docker, supporting multiple instances per directory and working in environments like Claude Code’s sandbox, currently in alpha off by default. Supabase Compute provides long-running services in any language alongside the database, with configurable memory and CPU, public or private HTTP endpoints, and deployment via CLI or Management API. The new MCP server lets user agents interact with an app as the signed-in user, respecting existing RLS policies, built on @supabase/server and Supabase Middleware, with a headless app template available.
Supabase is acquiring Turso
Supabase is acquiring Turso to evolve database infrastructure for the massive scale of AI agent-created databases. Supabase already launches over one million databases per week and expects demand to outpace capacity as agents build more software. Turso rebuilt SQLite in Rust, creating a cloud platform where a single server manages millions of databases, loading them on demand and suspending them when idle, avoiding dedicated machines for small workloads. This architecture suits agent workloads needing cheap, on-demand databases, while Postgres remains the path for scaling to production; Turso will continue operating independently with a clear path into Supabase’s ecosystem, and for existing users nothing changes. Glauber Costa will lead the agentic infrastructure effort, and the combined mission is to store the world’s data as agents create more of it.
Supabase is now available in Gemini Enterprise
Supabase is now available as a prebuilt connector in Google Cloud Gemini Enterprise, allowing teams to query and take action on Supabase projects through natural-language prompts. After an organization-level connection, Gemini Enterprise calls the connector for live answers, does not store or index Supabase data, and can combine results with connected tools such as GitHub, Linear, Notion, Slack, and Salesforce. The integration supports questions about tables, database metrics, and table structure, while exposed tools are marked read-only or destructive. Business users connect through the connector menu, whereas Standard, Plus, and Frontline administrators use a client ID and secret in the admin console; the connector is available across all editions.
Enterprise-managed auth for the Supabase MCP server
Supabase has generally released enterprise-managed authentication for its MCP server on Supabase Team and Enterprise plans, built with Anthropic and Okta. The change moves authorization for using Supabase in Claude to the organization's identity provider: an administrator authorizes the connector once, while employees receive access according to their existing Supabase projects and permissions. Each query and management action runs with the individual employee's current role, so developers and read-only members do not receive more access than they have in Supabase directly. Okta groups can restrict access, and onboarding, offboarding, and access reviews can be handled through existing identity-provider workflows rather than individual OAuth approvals; availability requires Okta SSO plus a Claude Team or Enterprise plan, with SCIM provisioning listed as a future roadmap item.
Connect client traces to your logs
supabase-js now supports W3C Trace Context propagation so a client trace can share its trace_id with Supabase API Gateway and Edge Function logs. Previously, browser and server records had no shared identifier, making cross-boundary debugging depend on manually aligning timestamps. When tracePropagation is enabled, the SDK attaches traceparent, tracestate, and baggage to requests for Supabase domains; Supabase preserves the trace_id in generated logs, and W3C-compliant tracers such as OpenTelemetry, Sentry, Datadog, Honeycomb, or Grafana can continue the trace server-side. The setup requires a separately configured tracer, the tracing entry-point import, an active span, and a registered TracerProvider; propagation is sampling-aware by default, adds no OpenTelemetry code to the main bundle, and is available in supabase-js 2.112.0 or later, with CDN/UMD builds excluded.
Supabase is now a connector on Perplexity Computer
Supabase is now available as a connector on Perplexity Computer, allowing the agent to use a Supabase project as a persistent data layer across runs. Computer can read from and write to Postgres tables, answer questions by running queries, retrieve user and payment data for support debugging, and invoke Edge Functions with test payloads. Recurring queries can be scheduled, with results posted to Slack, while workflows can combine Supabase data with Stripe events and route fixes through GitHub pull requests. The announcement presents the connector as a way to keep database work inside Computer’s multi-step workflows across more than 400 apps, without custom glue code.
Postgres Changes gets AND filters, new operators, and column selection
Postgres Changes now supports filters composed across multiple columns, additional operators, and column selection for subscriptions over Postgres tables. It can receive insert, update, and delete events over WebSockets, while comma-separated conditions or the postgresChangesFilter builder combine conditions with AND. New operators include like, ilike, is, match, imatch, isdistinct, and negated forms, while selected payloads always include the table's primary key. Column selection is opt-in, requires @supabase/supabase-js 2.109.0 or newer, and columns must be selectable by the subscribing role; Row Level Security still applies. These changes can lower billable usage because rejected events avoid messages per subscriber and trimmed payloads send fewer egress bytes, although DELETE events carry only the primary key and OR composition is unsupported.
Are Supabase docs agent-friendly? We didn't know, so we checked
Supabase found that coding agents increasingly use its documentation to configure projects, creating risks when pages omit or bury critical instructions. To measure this, the team built an evaluation for the Row Level Security (RLS) guide, running an agent through realistic tasks and grading outcomes with checklist-based and agent-based judges. The initial runs found unauthenticated anon access with write privileges across tables and showed that test guidance was skipped when separated from the policy code. Supabase responded by adding procedural revocation steps, explicit policy snippets, and colocated test examples; the eval then passed the affected checks. The project concludes that agents and humans both benefit from selective-reading-aware structure, clear sections, explicit signposting, and recurring documentation evaluations, with the RLS scenario moving into the public supabase/evals benchmark.
Introducing Supabase Evals
Supabase has open sourced supabase/evals, a benchmark and framework for testing how AI agents build using Supabase. It runs coding agents including Claude Code, Codex, and OpenCode against real tasks such as schema creation, Edge Function debugging, and RLS policy repair, scoring behavior with deterministic checks and LLM-as-a-judge. The framework executes scenarios in hosted-like and local containerized environments through the actual MCP server and CLI, with separate breadth-focused benchmark and depth-focused regression suites, plus a retry after failure. Initial findings show many agents pass broad tasks without skills, while skills improve some scores and documentation use; agents still often choose hand-written migrations, miss newer libraries, and use documentation inconsistently across harnesses.
Sign in with ChatGPT is in beta on Supabase
Supabase is rolling out Sign in with ChatGPT in beta on its login page and through the Supabase plugin in ChatGPT on desktop, web, and mobile. The flow lets new users create a Supabase account with their ChatGPT identity, while existing Supabase accounts with the same email are linked automatically; SSO accounts remain separate. Users can add Supabase from ChatGPT’s plugins directory, authenticate with ChatGPT, review a consent screen, and return to the conversation with the connection enabled. Authentication and plugin authorization remain separate, with access revocable from the Supabase Dashboard, and users must create an organization in the Dashboard before creating projects from ChatGPT. The beta is described as a partnership with OpenAI intended to reduce account setup between ChatGPT or Codex and a Supabase backend.
Observability for every Supabase project with Grafana Cloud
Supabase now offers a one-click Grafana Cloud integration from its Dashboard, with the setup available on every plan, including the free plan. The setup provisions authentication, metric scraping, and a pre-built observability dashboard that tracks more than 200 metrics through Supabase’s Metrics API. Those metrics cover CPU and memory pressure, disk I/O, network traffic, connections and pooler behavior, replication lag, checkpoints, database size, and query statistics, while the same open-source dashboard definitions support self-hosted Grafana, the existing Grafana Cloud integration, and the new setup. The release is focused on metrics and is designed to accommodate logs without architectural changes; support for log drains to Grafana Cloud is already in progress. Users can start with Grafana Cloud’s free tier without a credit card on either side.
Supabase Pipelines is now in Public Alpha
Supabase Pipelines has moved into public alpha as a service for replicating Supabase Postgres data to external analytical systems in near real time. The release adds automatic application of supported schema changes, faster initial synchronization through parallelism, and a destination request form for ClickHouse, Snowflake, and DuckLake; Google BigQuery is the first destination available to everyone in public alpha. Powered by the open-source Rust-based Supabase ETL, Pipelines uses Postgres logical replication to copy existing tables, stream inserts, updates, deletes, and truncates, and resume from the last acknowledged position after interruptions. It provides at-least-once delivery and managed pipeline controls, while remaining an alpha product with ongoing work on throughput, batching, backpressure, broader schema support, and additional destinations.
Unified Logs is now in open beta
Unified Logs enters open beta, bringing events from the API gateway, Postgres, Auth, Storage, PostgREST, Realtime, and connection poolers into one searchable dashboard view. Before this, debugging a single request required separate log pages, service-specific filters, and manual correlation across tabs, which slowed investigation and risked losing context. Users can filter by log type, level, status, method, or pathname, search event messages, share URL-based filter states, stream new events live, and zoom into timeline ranges colored by log level. Clicking a row opens a detail panel that presents network timing, gateway, database query, and Auth blocks alongside raw JSON, while Log Drains forward events to external destinations. The feature is rolling out to all projects during open beta, with the classic Logs Explorer still available and feedback requested.
Searchable field-level encryption on Supabase with CipherStash
CipherStash’s integration for Supabase adds searchable field-level encryption to Postgres applications without requiring a schema change. The encrypted Supabase SDK wrapper encrypts marked fields in the application, stores each value as a JSON payload containing ciphertext and Searchable Encrypted Metadata (SEM), and converts queries to SEM so Postgres can filter, sort, and join without plaintext access. ZeroKMS keeps keys under the customer’s control, while decryption policies determine who can read each value; the source states that neither CipherStash nor Supabase can access plaintext data. The integration supports Supabase.js, Drizzle, and Prisma Next, with a one-command setup, and CipherStash Proxy covers analytics, background workers, and other direct database access through the Postgres wire protocol.
Topics they write about
All topics →Weekly digest
The best engineering reads, once a week.