--- title: "Supabase" description: "12 posts about Supabase, summarised, each linking to the original." --- # Supabase > 12 posts about Supabase, summarised, each linking to the original. ## Articles ### [Getting started with the Supabase .NET SDK](https://yomu.fyi/post/getting-started-with-the-supabase-net-sdk.md) - Company: [Supabase](https://yomu.fyi/company/supabase.md) - Author: guillaume\_faas - Published: Oct 26, 2026 - Type: Tutorial 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](https://yomu.fyi/post/introducing-the-unified-supabase-net-sdk.md) - Company: [Supabase](https://yomu.fyi/company/supabase.md) - Author: guillaume\_faas - Published: Oct 19, 2026 - Type: Announcement 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 a new branch gets its config, migrations, and functions](https://yomu.fyi/post/how-a-new-branch-gets-its-config-migrations-and-functions.md) - Company: [Supabase](https://yomu.fyi/company/supabase.md) - Author: qiao - Published: Oct 15, 2026 - Type: Explainer Supabase branches are independent projects that require settings, schema, and edge functions to be set up before use. When a branch is created, configuration copies main project settings including Postgres, Auth, and Realtime config, then applies them with a single Postgres restart via walg\_enable; Auth secrets do not carry over. Migrations come from the git repo for GitHub-connected branches or from the main project’s migration history for gitless branches; each file runs as one transaction in pipeline mode. Edge functions are copied from the main project at creation in parallel with configuration, and on each push only changed functions are redeployed using Brotli compression and SHA-256 checksums. If a step fails, it shows as DEAD and stops dependent steps, while PAUSED indicates a warning that does not block subsequent steps. ### [Sync real-time Stripe data to Supabase with Stripe Data Pipeline](https://yomu.fyi/post/sync-real-time-stripe-data-to-supabase-with-stripe-data-pipeline.md) - Company: [Supabase](https://yomu.fyi/company/supabase.md) - Author: gregor\_vand, saba\_pochkhua, staaldraad - Published: Oct 15, 2026 - Type: Announcement Stripe’s Data Pipeline now adds Postgres as a destination, enabling developers to sync Stripe data directly into their Supabase project without maintaining webhooks or working around API rate limits. Setup occurs entirely in the Stripe Dashboard: under Reporting, Data management, users select Data Pipeline, choose Postgres and Supabase, and authorize the connection. Stripe backfills historical records and continuously syncs charges, refunds, disputes, customers, subscriptions, and invoices into a dedicated stripe\_sdp schema in the user’s Postgres database. A dedicated stripe\_sdp role with scoped permissions, JWT direct connections using short-lived tokens, and enforced SSL ensure the database password is never exposed to Stripe. Developers can then query the synced tables with standard SQL, join them with application data, and implement features like MRR calculations, churn analysis, or subscription-based feature gating without extra API calls. ### [A local Supabase project per agent, with or without Docker](https://yomu.fyi/post/a-local-supabase-project-per-agent-with-or-without-docker.md) - Company: [Supabase](https://yomu.fyi/company/supabase.md) - Author: jgoux, wenbo - Published: Oct 14, 2026 - Type: Announcement The Supabase CLI v2.119.0 introduces an experimental native runtime that runs all 13 services as plain processes without Docker, reducing startup time by over 80% and idle memory by 89%. It also supports multiple local projects on one machine via git worktrees, each with its own Postgres, Storage, Edge Functions, and MCP server on auto-assigned ports. This allows each coding agent to have an independent database to reset and test against without affecting others, making a project per worktree practical on a laptop. Remote branches now inherit configuration from their base project and are ready nearly five times faster, with function bundles copied in parallel. The native runtime runs on Linux and macOS, and Docker remains the default when present, but the CLI automatically selects native when Docker is absent. ### [How we made the Supabase Select 2026 badge](https://yomu.fyi/post/how-we-made-the-supabase-select-2026-badge.md) - Company: [Supabase](https://yomu.fyi/company/supabase.md) - Author: sam\_meech\_ward - Published: Oct 14, 2026 - Type: Tutorial 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](https://yomu.fyi/post/supabase-select-2026-recap.md) - Company: [Supabase](https://yomu.fyi/company/supabase.md) - Author: oli\_rice, inian, jonny - Published: Oct 2, 2026 - Type: Announcement 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](https://yomu.fyi/post/scale-without-limits-multigres-orioledb-and-dbarena.md) - Company: [Supabase](https://yomu.fyi/company/supabase.md) - Author: joe\_sciarrino, alexander\_korotkov, daniel\_mitterdorfer, aditya\_maruvada - Published: Oct 2, 2026 - Type: Announcement 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](https://yomu.fyi/post/operate-with-confidence.md) - Company: [Supabase](https://yomu.fyi/company/supabase.md) - Author: steven\_eubank, joshenlim, cemal\_kilic, riccardo\_busetti, joe\_sciarrino - Published: Oct 2, 2026 - Type: Announcement 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](https://yomu.fyi/post/build-anything-supabase-from-code-and-an-mcp-server-for-your-app.md) - Company: [Supabase](https://yomu.fyi/company/supabase.md) - Author: wenbo, laktek, jgoux, avallete, rand\_arete, katerina\_skroumpelou - Published: Oct 2, 2026 - Type: Announcement 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](https://yomu.fyi/post/supabase-is-acquiring-turso.md) - Company: [Supabase](https://yomu.fyi/company/supabase.md) - Author: paul\_copplestone - Published: Oct 2, 2026 - Type: Announcement 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](https://yomu.fyi/post/supabase-is-now-available-in-gemini-enterprise.md) - Company: [Supabase](https://yomu.fyi/company/supabase.md) - Author: shaziya\_bandukia, elsa\_heffernan - Published: Sep 9, 2026 - Type: Announcement 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.