October 2026 Summaries
23 posts from Supabase
Filter
Month:
Year:
Post Summaries
Back to Blog
DBArena is a Supabase-sponsored website publishing reproducible benchmarks of hosted PostgreSQL services, initially comparing Supabase Postgres with default storage and OrioleDB, Amazon RDS for PostgreSQL, and Google Cloud SQL for PostgreSQL across up to seven compute tiers. It measures throughput, price-performance, and p95 latency using a TPC-C-derived workload under cache-fitting and disk-intensive scenarios, with providers matched by vCPU count and I/O configuration while retaining default database settings. Tests use PostgreSQL 17, direct TLS connections, 30-minute warmups, 60-minute measurement periods, concurrency sweeps to identify peak throughput, and three successful fresh-environment runs whose median is published. Results include raw data, configurations, commands, metadata, and open-source tooling to enable independent reruns, with the first release containing 62 results from more than 750 runs conducted between September 25 and October 1, 2026. The project notes limitations including its single maximum-throughput workload, one tested region per cloud, list-price cost comparisons, vCPU-based matching rather than memory matching, and differing load-generator placement options among providers.
Oct 31, 2026
857 words in the original blog post.
Supabase Explorer is a feature-preview query editor that unifies database and log analysis within the Dashboard, allowing users to query either source in SQL and view results as tables or charts. Its Notebook format combines saved query cells, visualizations, and Markdown notes into reusable investigation records that store queries rather than results, enabling current data to be retrieved whenever they are rerun. Explorer also integrates Supabase Assistant, which can translate natural-language requests into editable SQL and Markdown notebook cells, while requiring approval for every creation or edit. Notebooks can also be written manually without AI, stored in a project’s supabase folder, version-controlled through repositories and pull requests, and synchronized between local environments and the Dashboard using beta CLI pull and push commands. Available to all projects through the Dashboard’s Feature Previews settings, Explorer replaces the existing SQL Editor when enabled.
Oct 31, 2026
599 words in the original blog post.
Supabase has launched Multigres in private alpha to provide managed high availability for paid-plan projects through three-node Postgres clusters distributed across availability zones, automatic failover, and integrated connection pooling. Built as an Apache 2.0 open-source system by the team behind Vitess, Multigres operates around standard Postgres rather than modifying it, managing routing, replication, backups, pooling, and failover while retaining a standard connection string and compatibility with most Supabase services. Its consensus-based approach uses synchronous replication so writes are acknowledged only after reaching enough nodes to survive a failure, aiming to prevent acknowledged commits from being lost during promotion of a new primary. The alpha is free for up to two projects per organization but is not intended for production, lacks SLA coverage, Realtime support, point-in-time recovery, cross-region replicas, resizing, and migration paths to or from standard projects; it is currently limited to newly created projects in East US and cannot be combined with OrioleDB.
Oct 30, 2026
926 words in the original blog post.
Supabase is now integrated with Make, an AI automation platform used by more than 400,000 organizations to create visual workflows across over 3,000 apps. Users can connect Supabase through pre-built API modules for repeatable tasks such as querying databases or writing Postgres records, or through Make’s MCP Client and AI agents for structured access to database content, logs, project management, and Edge Function deployment. The integration supports workflows built visually or described in natural language through Make’s Maia assistant, allowing teams to use live Supabase data without exports or nightly synchronization processes. Make records scenario runs and agent tool calls for auditability, while Supabase MCP tools are labeled as read-only or destructive to clarify their potential impact. Setup requires a Make account and Supabase project, with MCP Client access available on every Make plan.
Oct 29, 2026
509 words in the original blog post.
Supabase has introduced OrioleDB, an open-source Postgres storage engine, as a public beta option for new projects on all plans at standard Postgres pricing, though it is not yet recommended for production. Designed to address limitations of Postgres’s default heap storage, OrioleDB uses undo logs, 64-bit transaction IDs, index-organized tables, lock-free page reads, and copy-on-write checkpoints to reduce table bloat, lessen VACUUM dependence, and improve performance under update-heavy or high-concurrency workloads. Supabase’s public DBArena benchmarks found that OrioleDB delivered the strongest throughput per dollar when datasets exceeded memory capacity, reaching roughly 1.8 times the transactions per minute of standard Supabase Postgres on an 8XL instance, while gains were smaller for memory-resident and read-mostly workloads. It is suited to frequently updated data such as inventory, orders, queues, and sessions, but users are encouraged to benchmark their own workloads, particularly when relying on non-B-tree indexes. The beta can only be selected during new project creation and supports core managed features, but lacks point-in-time recovery and some extensions and commands, cannot coexist with Multigres, and is not yet available for self-hosted Supabase.
Oct 29, 2026
1,154 words in the original blog post.
Supabase Compute has launched in private alpha, allowing developers to run AI agents, long-running background jobs, APIs, WebSocket services, data synchronization tasks, and Docker-based applications within the same Supabase project as their data. Available initially only for projects in the us-west-2 region, Compute provides full Linux environments with Node, Deno, or custom Dockerfile support and configurable instances offering either 2 GB memory with 1 vCPU or 4 GB with 2 vCPUs. Services can be public or private, deployed through the Supabase CLI or alpha Management API endpoints, access project secrets, and expose logs in the Supabase dashboard. Supabase positions the feature as an alternative to deploying workloads requiring more resources, longer execution times, or different languages on separate platforms, citing Dreambase’s reported reduction in median Postgres query latency from 65 ms to 2.9 ms. The alpha is intended for evaluation rather than production, lacks autoscaling, GPUs, persistent disks, and AI-agent sandboxes, and requires long-running state to be saved in Postgres because services may restart at any time.
Oct 28, 2026
488 words in the original blog post.
Supabase has introduced generally available scoped Personal Access Tokens, allowing users to limit tokens to specific organizations or projects, permissions, and expiration dates rather than granting full account access by default. Users can create tokens tailored to individual tools such as coding agents or deployment scripts, select minimal permissions, review associated API endpoints and MCP tools, and assess risk based on scope and write access. Token capabilities remain constrained by the creator’s current account role, so access is automatically lost or restored as the user’s own permissions change. Scoped tokens work with the Management API, MCP server, and CLI through bearer authentication, although some CLI workflows and database-password-based commands have distinct permission behavior. Existing full-access tokens remain functional without a deprecation deadline, but Supabase recommends replacing them with narrowly scoped tokens for future integrations.
Oct 27, 2026
996 words in the original blog post.
Supabase introduced an MCP Server block that lets developers expose their application’s actions as Model Context Protocol tools for use in clients such as ChatGPT and Claude, while preserving each customer’s existing Supabase identity and Row Level Security permissions. The generated Edge Function includes MCP handling, OAuth authentication middleware, a caller identity tool, and a structure for registering custom tools, allowing developers to use user-scoped Supabase queries without service role keys. Tools can access databases, Edge Functions, APIs, and external services, but Supabase recommends retaining business rules in shared application logic. A Sizzle demonstration showed customers using MCP to retrieve products and generate video ads directly within an AI conversation, with optional embedded interfaces through MCP Apps that can reuse existing React components. To deploy the feature, developers configure asymmetric signing keys, OAuth 2.1 and dynamic client registration, add a consent page, disable the Edge Function’s built-in JWT check for unauthenticated discovery requests, and connect agents to the deployed server URL.
Oct 24, 2026
1,118 words in the original blog post.
Supabase .NET SDK v8 consolidates all related packages, including Gotrue, PostgREST, Realtime, Storage, Functions, and the main Supabase package, into a single repository with synchronized versioning and coordinated releases. The move to v8 establishes lockstep versioning after previously independent package lifecycles, making compatibility and upgrades clearer despite the unusually large version jump from the main package’s v1 series. A new Supabase.Extensions.DependencyInjection package supports ASP.NET Core integration by registering the Supabase client in the .NET service container and allowing IHttpClientFactory to manage its HTTP client. Other updates include migration from Newtonsoft.Json to System.Text.Json, configurable retry-with-backoff support across service packages, support for publishable and secret API keys, and a netstandard2.1 target for all packages. Because v8 introduces breaking changes, a migration guide and detailed release notes are available to assist existing users with upgrading.
Oct 22, 2026
424 words in the original blog post.
Supabase .NET SDK version 8.0.0 provides a C# interface to Supabase Auth, Database, Storage, Realtime, and Edge Functions, with a new ASP.NET Core dependency injection package that registers reusable scoped clients through IHttpClientFactory to avoid connection-pool exhaustion. The release moves serialization from Newtonsoft.Json to System.Text.Json, adds injectable HttpClient support and optional retry backoff, and requires .NET Core 3.0 or later because it targets .NET Standard 2.1. Developers can install the all-in-one Supabase package or individual service packages, map database tables to BaseModel-derived C# classes with attributes, and perform filtered queries, inserts, updates, and deletes through HTTP-based calls rather than Entity Framework-style change tracking. Outside ASP.NET Core, applications should create and initialize one reusable client, configure session storage if sign-in persistence is needed, and enable options such as automatic token refresh and Realtime connections. The SDK also supports email-password authentication, other Auth methods, and Storage uploads, while advising publishable or anon keys for distributed client applications and restricting secret or service keys, which can bypass Row Level Security, to server-side use.
Oct 22, 2026
1,330 words in the original blog post.
Supabase has introduced five “Operate with confidence” features aimed at helping coding agents monitor and troubleshoot production projects before users report issues. Agent prompts can run on demand or on schedules through tools such as Claude, Codex, and Cursor to check health, security, performance, and resource usage, reporting only new or worsening findings with thresholds, measurements, and suggested next steps. These prompts use a read-only, project-scoped Supabase MCP connection and require saved alert state to distinguish recurring issues from new ones. Supporting releases include the query_logs MCP tool for read-only analysis of up to 24 hours of logs, updated Supabase agent skills that direct agents to current observability documentation, a Health tab in Advisors for abnormal error rates across services, and a Database Connections dashboard for identifying and managing blocked, long-running, idle, or locking database sessions.
Oct 21, 2026
964 words in the original blog post.
Supabase announced @supabase/middleware at Supabase Select on October 2, a free MIT-licensed TypeScript library for composing type-safe per-request middleware across Web Fetch-compatible runtimes and frameworks including Hono, H3, Elysia, NestJS, and TanStack Start. It builds on @supabase/server by allowing concerns such as CORS, JWT verification, feature flags, Supabase clients, Postgres connections, and OAuth protected-resource handling to be arranged in an ordered pipeline, where entries can add typed context, stop requests with responses, or modify outgoing responses. Pipelines can run unchanged on environments such as Supabase Edge Functions, Vercel Functions, Cloudflare Workers, Deno, Bun, and modern Node.js, although individual middleware may have runtime limitations such as Postgres TCP support. Framework bridges let developers reuse Fetch-standard middleware within framework-specific middleware systems through small project-local adapter files. The package also provides defineMiddleware for creating reusable custom entries with TypeScript checks for dependency order and duplicate context keys, while middleware can be published as versioned packages for use across projects.
Oct 17, 2026
2,162 words in the original blog post.
Supabase branches operate as independent projects that become ready after configuration, database schema migrations, and Edge Function deployment are completed, typically in parallel and usually within about 20 seconds. GitHub-connected branches use configuration files, migrations, seeds, and functions from the associated repository branch, while gitless branches derive schema and functions from the main Supabase project. Branch setup copies most project settings, including Postgres, Auth, API, Realtime, Storage, SSL, and network controls, while excluding Auth secrets; configuration is optimized to minimize restarts and repository settings can override copied settings. Git-based workflows run sequential cloning, pulling, health checks, configuration, migrations, seeding, and deployment on each push, whereas gitless branches use a shorter pull-and-migrate process. Migrations are applied transactionally per file, preserving atomicity and detailed error reporting, while Edge Functions are copied initially and later redeployed only when their compressed bundles or JWT settings change. Workflow statuses indicate progress, warnings, successes, and failures, with dependent steps halted after critical failures, and branch logs in the dashboard provide troubleshooting details.
Oct 16, 2026
1,679 words in the original blog post.
Stripe Data Pipeline now supports Supabase as a PostgreSQL destination, allowing businesses to backfill and continuously synchronize Stripe data such as charges, customers, subscriptions, invoices, refunds, and disputes directly into a dedicated database schema. Configured through the Stripe Dashboard, the integration eliminates the need to maintain webhooks, manage API limits, or store a separate copy of Stripe’s evolving data model, while enabling standard SQL queries and joins with application data. Supabase prepares connected projects with a schema-scoped role, short-lived JWT-based credentials, and enforced SSL so Stripe does not receive a persistent database password. The integration can support use cases including subscription-based feature gating, payment and product-usage analysis, and revenue metrics such as MRR and churn. It builds on earlier Stripe-Supabase collaborations, including the Stripe Sync Engine, a Stripe foreign data wrapper, and project provisioning through the Stripe CLI, while Stripe Atlas companies can receive Supabase credits.
Oct 16, 2026
704 words in the original blog post.
Supabase CLI v2.119.0 introduces an experimental local development engine that allows multiple isolated Supabase projects to run simultaneously across Git worktrees, giving coding agents separate databases, services, ports, and credentials without manual coordination. Projects can start only the services they need, reducing startup times, download sizes, and idle memory use substantially, while a native runtime enables all 13 Supabase services to run as local processes without Docker on supported Linux and Apple Silicon macOS systems. Docker remains the default and is recommended for multiple projects on one laptop, whereas the native runtime is aimed at individual sandbox or CI environments. Remote branches created for pull requests now inherit relevant project configuration and deployed Edge Functions while excluding secrets and production data by default, reducing median readiness time from 102 seconds to 21 seconds. Users can enable the experimental stack through an environment variable or configuration setting, while branch performance improvements are already available to all projects.
Oct 16, 2026
853 words in the original blog post.
Supabase Select 2026 in San Francisco distributed programmable badges based on the Pimoroni Tufty 2350, featuring an RP2350 microcontroller, color display, rechargeable battery, Wi-Fi, Bluetooth, and five configurable buttons. Although the badges served as animated name tags with schedules and games during the conference, preparing 800 units proved difficult after a firmware bug drained their batteries in transit, requiring extensive charging, firmware updates, and individual schedule synchronization; venue Wi-Fi also failed, preventing planned synchronized animations, announcements, and leaderboards. Despite these challenges, attendees and remote participants repurposed the devices for projects including a flight tracker, restaurant finder, arcade games, and locally run language models. Supabase encourages further development through USB-based guides, browser-based virtual badges, AI-assisted project tooling, and options to work in C or Rust, while offering a contest for projects shared with the #SelectBadge hashtag.
Oct 15, 2026
1,261 words in the original blog post.
Supabase’s Declarative Schemas 2.0 replaces the migra-based migration diff engine with pg-delta, an open-source PostgreSQL catalog-driven tool that generates SQL migrations from schema files while expanding support for RLS policy alterations, grants, view settings, comments, roles, domains, partitions, publications, extension-managed objects, and more. Developers define SQL schemas under `supabase/schemas`, use the CLI to compare them with migration history in temporary shadow databases, review the generated migration, and apply it, with dependency ordering handled automatically rather than through manually ordered files. New CLI projects use pg-delta by default, while existing projects can opt in through an experimental configuration setting and require Supabase CLI 2.119 or newer. pg-delta warns about unsupported objects and can fail CI in strict-coverage mode, but generated migrations still require careful review because changes such as column renames may be expressed as destructive drop-and-add operations. The engine does not generally manage table data, storage buckets, zero-downtime deployment orchestration, ORM integrations, or PostgreSQL versions earlier than 14, though it handles some extension configuration stored as rows through extension APIs. Available independently on npm for comparing PostgreSQL 14 through 18 databases, pg-delta remains in alpha and is also used internally by Supabase for branch merge diffs, schema exports, and production drift detection.
Oct 14, 2026
2,466 words in the original blog post.
Supabase has joined the SpaceXAI Partner Network to integrate its MCP server with Cursor and Grok Bot, enabling team members to submit requests through chat while Cursor performs scoped engineering work directly against a Supabase project. Through the integration, Cursor can inspect schemas, query databases, review logs, deploy Edge Functions, and validate changes, with Supabase reporting that agents commonly conduct iterative investigation and correction rather than stopping after a single query. Analysis of millions of Cursor tool calls found that 92% of database queries are followed by another query, while 79% of failed queries are retried and only about 2% of errors end a session. The integration is designed to let nontechnical requesters initiate work without identifying the relevant project or tables, while Cursor locates project context and examines schemas. Supabase also recommends automated security and performance reviews after schema migrations using its advisor tool, which can identify concerns such as missing Row Level Security or unindexed foreign keys. The partnership formalizes an integration that had already become a popular community plugin, and users can begin by connecting the Supabase MCP server to Cursor.
Oct 14, 2026
536 words in the original blog post.
Supabase announced tools designed to help coding agents investigate production issues, test fixes in isolated environments, and operate with more controlled permissions. New capabilities include raw project-log access through an MCP SQL tool, expanded Advisor health checks for abnormal error rates across core services, and a Database Connections view for identifying long-running, blocked, idle, or locking queries and managing their sessions. Supabase also introduced Notebooks, which combine reusable database or log queries with notes and can be created, synchronized, and run by developers or agents through the dashboard and CLI. Updated agent skills provide guidance on monitoring health, security, performance, and resource signals, while improvements to project code representation and local runtimes support testing changes before pull requests. Security controls include enterprise-managed MCP authentication via Okta, scoped read-only-by-default personal access tokens, and MCP confirmation prompts for paid resources or potentially destructive SQL actions. Additionally, Supabase Pipelines, now in public alpha for paid plans, replicate Postgres data to analytical destinations such as BigQuery, ClickHouse, DuckLake, and Snowflake in near real time to reduce analytics workloads on primary databases.
Oct 03, 2026
904 words in the original blog post.
Supabase is joining with Turso to develop database infrastructure for AI agents, which are increasingly creating large numbers of applications, prototypes, and associated databases. Existing products will continue independently, with Supabase focused on Postgres for scalable production workloads and Turso focused on SQLite for lightweight, on-demand databases. Turso’s Rust-based SQLite cloud architecture can operate millions of databases from a single server by loading and suspending them as needed, making low-cost per-agent databases more practical. The companies plan to provide a consistent developer experience from experimentation through production while maintaining their shared commitments to open source and developer-focused infrastructure. Turso’s team, including cofounders Glauber Costa and Pekka Enberg, will join Supabase, with Costa leading the agentic infrastructure initiative.
Oct 03, 2026
398 words in the original blog post.
Supabase announced agent-focused tools that move backend development workflows into repositories, enabling coding agents to edit SQL schemas and project configuration, generate migrations through the new pg-delta diff engine, synchronize dashboard changes with code, and test changes locally. Local Supabase can now run as native processes without Docker and supports separate stacks for multiple directories or worktrees, though the feature is currently in alpha. The company also introduced Supabase Compute, a private-alpha platform for deploying persistent web services, agents, background jobs, and sandboxes with configurable resources, Linux environments, public or private networking, CLI and API management, and integration with existing Supabase services. In addition, developers can add customizable MCP servers to their applications so users’ AI agents can act on their behalf while authenticating normally and remaining constrained by Row Level Security policies; Supabase provides an Edge Function-based implementation, supporting libraries, middleware, and a headless agent-first application template.
Oct 03, 2026
915 words in the original blog post.
Supabase announced a code-first platform strategy at Supabase Select, aiming to let developers and coding agents manage application backends, monitoring, and scaling through repository-based schemas and configuration. New capabilities include native local development without Docker, Declarative Schemas 2.0 with generated migrations, private-alpha Supabase Compute for long-running services, and tools for embedding an MCP server in applications so users’ agents can access data under existing authentication and row-level security rules. Operational additions include agent prompts for read-only health, security, performance, and resource checks; expanded Advisors; database connection visibility and controls; direct log querying for agents; a unified Explorer workspace and shareable Notebooks; enterprise-managed MCP authentication, scoped access tokens, and confirmation prompts for potentially costly or destructive agent actions. Supabase also introduced near-real-time Postgres data pipelines to analytics platforms, while its scaling roadmap includes private-alpha Multigres for multi-node PostgreSQL high availability, public-beta OrioleDB as a storage engine intended to reduce bloat and VACUUM requirements, and dbarena, an open benchmarking initiative that publishes methods, data, and cost-performance results.
Oct 03, 2026
979 words in the original blog post.
Supabase announced three initiatives aimed at addressing different Postgres scaling challenges: Multigres, OrioleDB, and dbarena. Multigres is an open-source Postgres operating system, built by the Vitess team, that combines scalable connection pooling with automated multi-node failover using synchronous replication and consensus to preserve committed writes, and it is currently available through a private alpha. OrioleDB is an open-source Postgres storage engine in public beta that replaces traditional heap storage with an undo-log approach intended to eliminate table bloat, VACUUM overhead, and transaction ID wraparound while improving concurrency and throughput; Supabase reports up to 1.8 times higher throughput in its published benchmark. dbarena is a public benchmarking site that compares managed Postgres offerings from Supabase, Amazon RDS, and Google Cloud SQL using reproducible methods, raw data, cost-normalized performance measures, latency, and infrastructure specifications.
Oct 03, 2026
907 words in the original blog post.