# Supabase

Supabase is a Postgres development platform providing databases, authentication, data APIs, edge functions, realtime data, storage, and vector embeddings.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Do you need BYOC? A guide for technical leaders

DevFeed: [Do you need BYOC? A guide for technical leaders](<https://devfeed.tech/articles/do-you-need-byoc-a-guide-for-technical-leaders-146527.md>)

Original publisher: [Read original article](<https://turso.tech/blog/do-you-need-byoc-a-guide-for-technical-leaders>)

Author: Jeff Olson

Published: 2026-11-19T00:00:00Z

Content type: article

Language: en

Sources: [Turso](<https://devfeed.tech/sources/turso-blog.md>)

Topics: [Turso](<https://devfeed.tech/topics/turso.md>), [Supabase](<https://devfeed.tech/topics/supabase.md>), [Platform API](<https://devfeed.tech/topics/platform-api.md>)

Tags: [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [aws](<https://devfeed.tech/tags/aws.md>), [byoc](<https://devfeed.tech/tags/byoc.md>), [byoc-deployment](<https://devfeed.tech/tags/byoc-deployment.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [customer](<https://devfeed.tech/tags/customer.md>), [database](<https://devfeed.tech/tags/database.md>), [databases](<https://devfeed.tech/tags/databases.md>), [deals](<https://devfeed.tech/tags/deals.md>), [decision](<https://devfeed.tech/tags/decision.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [device](<https://devfeed.tech/tags/device.md>), [devices](<https://devfeed.tech/tags/devices.md>), [embedded](<https://devfeed.tech/tags/embedded.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [field](<https://devfeed.tech/tags/field.md>), [file](<https://devfeed.tech/tags/file.md>), [finance](<https://devfeed.tech/tags/finance.md>), [guide](<https://devfeed.tech/tags/guide.md>), [saas](<https://devfeed.tech/tags/saas.md>), [security](<https://devfeed.tech/tags/security.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>), [supabase](<https://devfeed.tech/tags/supabase.md>), [turso](<https://devfeed.tech/tags/turso.md>)

### AI overview

For Turso, BYOC fits when both requirements apply: data must stay in your or your customer's AWS or GCP account, and you need a database per agent, user, tenant, or device. Turso Cloud BYOC runs Turso Cloud's managed layer in that account, using the same API and workflows while keeping data within the chosen boundary; the text says Turso cannot access it. It avoids the provisioning, routing, scaling, and backup work of self-hosting, and supports hosted service for most customers with BYOC deployments for those that require their own account. If data can live with Turso, Turso Cloud is the hosted option for small, separate databases. For offline device apps, Embedded Turso runs as a library and can pair with a cloud option for syncing. Supabase is presented for one or a handful of shared databases, or workloads requiring Postgres, with Auth, APIs, Realtime, Functions, Storage, and vector embeddings. Spark is described as not yet available.

### Source excerpt

BYOC is a common request in enterprise deals. This guide helps you check whether your team needs it, and maps your answers to Turso Cloud, Turso Cloud BYOC, Embedded Turso, or Supabase.

## Connect Supabase, Box, Calendly, and more to Copilot

DevFeed: [Connect Supabase, Box, Calendly, and more to Copilot](<https://devfeed.tech/articles/connect-supabase-box-calendly-and-more-to-copilot-141429.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-11-18-connect-supabase-box-calendly-and-more-to-copilot>)

Author: Allison

Published: 2026-11-18T22:04:50Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [AI connector platforms](<https://devfeed.tech/topics/ai-connector-platforms.md>), [Supabase](<https://devfeed.tech/topics/supabase.md>)

Tags: [box](<https://devfeed.tech/tags/box.md>), [calendly](<https://devfeed.tech/tags/calendly.md>), [connect](<https://devfeed.tech/tags/connect.md>), [connectors](<https://devfeed.tech/tags/connectors.md>), [content](<https://devfeed.tech/tags/content.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [improvement](<https://devfeed.tech/tags/improvement.md>), [supabase](<https://devfeed.tech/tags/supabase.md>)

### AI overview

Eight GitHub-verified MCP connectors are available to Copilot in public preview: Box, Buildkite, Calendly, ClickUp, Mixpanel, Supabase, Webflow, and Wix. They let Copilot work with each service--for example, investigate a failed Buildkite build and fix code in the same session, or inspect a Supabase schema before writing a migration. Connect through Customize in the Copilot app, `/mcp` in Copilot CLI, the Agents window in VS Code, or the Copilot customization page on github.com. The connectors are available on all Copilot plans; Business and Enterprise require an admin to enable the `Editor preview features` policy. Enterprises with individually listed MCP allowlists must add the new connectors, and some services require separate enablement by their own administrators.

### Source excerpt

You can now connect eight more services to Copilot using GitHub-verified MCP servers, or connectors, available in public preview. New services you can connect Box: Search and manage content, and... The post Connect Supabase, Box, Calendly, and more to Copilot appeared first on The GitHub Blog.

## Set up Supabase for every Expo environment in one command

DevFeed: [Set up Supabase for every Expo environment in one command](<https://devfeed.tech/articles/set-up-supabase-for-every-expo-environment-in-one-command-126749.md>)

Original publisher: [Read original article](<https://supabase.com/blog/set-up-supabase-for-every-expo-environment-in-one-command>)

Author: Grant Huston; Tyler Shukert; Shaziya Bandukia; Elsa Heffernan

Published: 2026-11-10T07:00:00Z

Content type: release

Language: en

Sources: [Supabase](<https://devfeed.tech/sources/supabase-blog.md>)

Topics: [Expo](<https://devfeed.tech/topics/expo.md>), [Supabase](<https://devfeed.tech/topics/supabase.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [account](<https://devfeed.tech/tags/account.md>), [agent](<https://devfeed.tech/tags/agent.md>), [app](<https://devfeed.tech/tags/app.md>), [backend](<https://devfeed.tech/tags/backend.md>), [build](<https://devfeed.tech/tags/build.md>), [cli](<https://devfeed.tech/tags/cli.md>), [command](<https://devfeed.tech/tags/command.md>), [database](<https://devfeed.tech/tags/database.md>), [environment](<https://devfeed.tech/tags/environment.md>), [logs](<https://devfeed.tech/tags/logs.md>), [next](<https://devfeed.tech/tags/next.md>), [one](<https://devfeed.tech/tags/one.md>), [security](<https://devfeed.tech/tags/security.md>), [security-findings](<https://devfeed.tech/tags/security-findings.md>), [separate](<https://devfeed.tech/tags/separate.md>), [set](<https://devfeed.tech/tags/set.md>), [supabase](<https://devfeed.tech/tags/supabase.md>), [up](<https://devfeed.tech/tags/up.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Run `eas integrations:supabase:connect` with eas-cli 21.8.0 or newer in an Expo-linked project to create a Supabase project, install its SDK, and write keys to Expo's Production, Preview, and Development environments. Using `--environment preview` creates a separate Supabase project and keys for Preview, keeping its builds and updates on preview data while Production data remains untouched; Development can use a local Supabase stack. The EAS CLI also runs Supabase Security and Performance Advisors and displays findings, such as disabled Row Level Security or missing foreign-key indexes, alongside build logs. Commands run without prompts and return JSON, supporting agent-driven setup. The excerpt describes the integration and its environment separation, but does not provide independent evaluation of its behavior.

### Source excerpt

Set up a Supabase backend for your Expo app in one EAS CLI command, with a separate database per environment and security findings next to your build logs.

## Supabase From a Pentester's Perspective: Methodology and Where the Real Risks Hide

DevFeed: [Supabase From a Pentester's Perspective: Methodology and Where the Real Risks Hide](<https://devfeed.tech/articles/supabase-from-a-pentester-s-perspective-methodology-and-where-the-real-risks-hide-109761.md>)

Original publisher: [Read original article](<https://www.cobalt.io/blog/supabase-from-a-pentesters-perspective-methodology-and-where-the-real-risks-hide>)

Author: Lukasz Wierzbicki

Published: 2026-10-30T17:39:23Z

Content type: tutorial

Language: en

Sources: [Cobalt](<https://devfeed.tech/sources/blog-4.md>)

Topics: [Supabase](<https://devfeed.tech/topics/supabase.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [LocalStorage](<https://devfeed.tech/topics/localstorage.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [api](<https://devfeed.tech/tags/api.md>), [api-access](<https://devfeed.tech/tags/api-access.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [attack-surface](<https://devfeed.tech/tags/attack-surface.md>), [auth](<https://devfeed.tech/tags/auth.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [automation](<https://devfeed.tech/tags/automation.md>), [backend](<https://devfeed.tech/tags/backend.md>), [boundary](<https://devfeed.tech/tags/boundary.md>), [cobalt-core](<https://devfeed.tech/tags/cobalt-core.md>), [methodology](<https://devfeed.tech/tags/methodology.md>), [pentester](<https://devfeed.tech/tags/pentester.md>), [perspective](<https://devfeed.tech/tags/perspective.md>), [risks](<https://devfeed.tech/tags/risks.md>), [supabase](<https://devfeed.tech/tags/supabase.md>)

### AI overview

Supabase's public client key is expected; the real risk is weak authorization, missing or overly permissive Row Level Security (RLS), exposed privileged keys, or unsafe storage settings. The pentest method starts by finding project configuration and service endpoints in client code and traffic, then probing REST, Auth, Storage, functions, and other enabled services. Test known records across unauthenticated and authenticated users, vary queries and identifiers, and check reads and writes across roles to build an authorization matrix. Extend checks to storage, Realtime, functions, and common web risks such as rate limits, token storage, and privileged function logic. Defenders should keep service_role keys server-side, test access rules across resources and roles, review storage exposure, and correlate platform logs for broad queries or unusual access patterns.

### Source excerpt

Methodology and where the real risks hide.

## Introducing DBArena: open, reproducible benchmarks for hosted Postgres

DevFeed: [Introducing DBArena: open, reproducible benchmarks for hosted Postgres](<https://devfeed.tech/articles/introducing-dbarena-open-reproducible-benchmarks-for-hosted-postgres-109686.md>)

Original publisher: [Read original article](<https://supabase.com/blog/introducing-dbarena>)

Author: Aditya Maruvada; Daniel Mitterdorfer

Published: 2026-10-30T07:00:00Z

Content type: release

Language: en

Sources: [Supabase](<https://devfeed.tech/sources/supabase-blog.md>)

Topics: [Supabase](<https://devfeed.tech/topics/supabase.md>)

Tags: [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [cloud-sql](<https://devfeed.tech/tags/cloud-sql.md>), [latency](<https://devfeed.tech/tags/latency.md>), [methodology](<https://devfeed.tech/tags/methodology.md>), [open](<https://devfeed.tech/tags/open.md>), [performance](<https://devfeed.tech/tags/performance.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [providers](<https://devfeed.tech/tags/providers.md>), [public](<https://devfeed.tech/tags/public.md>)

### AI overview

DBArena publishes reproducible hosted Postgres benchmarks comparing Supabase Postgres with default storage and with beta OrioleDB, Amazon RDS for PostgreSQL, and Google Cloud SQL for PostgreSQL Enterprise. Tests use Postgres 17, provider defaults, matched vCPU counts and I/O, and report throughput, throughput per monthly list-price dollar, and p95 latency under cache-fit and disk-reading workloads. A TPC-C-derived workload runs without think time; results are medians of three successful fresh-environment runs at peak client concurrency after warmup. Public result files include commands and configuration, and open-source tools support reruns. The initial results cover up to seven compute tiers and two cloud regions. The excerpt notes limits: one workload, no think time, list prices without discounts, matching by vCPU rather than memory, and provider-specific load-generator placement; the workload is not compliant with published TPC-C benchmark requirements.

### Source excerpt

DBArena benchmarks hosted Postgres providers on price-performance, with a public methodology.

## Multigres private alpha: automatic failover for Supabase Postgres

DevFeed: [Multigres private alpha: automatic failover for Supabase Postgres](<https://devfeed.tech/articles/multigres-private-alpha-automatic-failover-for-supabase-postgres-107147.md>)

Original publisher: [Read original article](<https://supabase.com/blog/multigres-private-alpha>)

Author: Aditya Maruvada; Manan Gupta

Published: 2026-10-29T07:00:00Z

Content type: release

Language: en

Sources: [Supabase](<https://devfeed.tech/sources/supabase-blog.md>)

Topics: [Supabase](<https://devfeed.tech/topics/supabase.md>), [Raft](<https://devfeed.tech/topics/raft.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2025](<https://devfeed.tech/tags/2025.md>), [3](<https://devfeed.tech/tags/3.md>), [after](<https://devfeed.tech/tags/after.md>), [algorithm](<https://devfeed.tech/tags/algorithm.md>), [all](<https://devfeed.tech/tags/all.md>), [alpha](<https://devfeed.tech/tags/alpha.md>), [also](<https://devfeed.tech/tags/also.md>), [apache](<https://devfeed.tech/tags/apache.md>), [apache-2-0](<https://devfeed.tech/tags/apache-2-0.md>), [api](<https://devfeed.tech/tags/api.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [automatic](<https://devfeed.tech/tags/automatic.md>), [failover](<https://devfeed.tech/tags/failover.md>), [organizations](<https://devfeed.tech/tags/organizations.md>), [plan](<https://devfeed.tech/tags/plan.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [private](<https://devfeed.tech/tags/private.md>), [supabase](<https://devfeed.tech/tags/supabase.md>)

### AI overview

Multigres runs Supabase Postgres across three nodes in one region and uses consensus with synchronous replication so a write is acknowledged only after enough nodes hold it to survive a failure. If the primary fails, surviving nodes agree on committed writes before promoting a replica; the gateway can hold incoming requests during the transition. Built-in pooling tracks session state per query, allocates connection budgets fairly across database users, and deduplicates prepared statements. Paid-plan organizations can request private-alpha access, then enable high availability when creating a project; it is free for up to two projects per organization during alpha. The excerpt says alpha projects lack an uptime SLA and Realtime or point-in-time recovery, are limited to East US, and cannot be resized or converted back through a managed path. Multigres cannot be combined with OrioleDB.

### Source excerpt

Multigres brings automatic failover to Supabase Postgres, in private alpha for organizations on a paid plan.

## Automate your Supabase backend with Make

DevFeed: [Automate your Supabase backend with Make](<https://devfeed.tech/articles/automate-your-supabase-backend-with-make-105586.md>)

Original publisher: [Read original article](<https://supabase.com/blog/automate-your-supabase-backend-with-make>)

Author: Elsa Heffernan

Published: 2026-10-28T07:00:00Z

Content type: release

Language: en

Sources: [Supabase](<https://devfeed.tech/sources/supabase-blog.md>)

Topics: [Supabase](<https://devfeed.tech/topics/supabase.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-assistant](<https://devfeed.tech/tags/ai-assistant.md>), [ai-automation](<https://devfeed.tech/tags/ai-automation.md>), [api](<https://devfeed.tech/tags/api.md>), [automation](<https://devfeed.tech/tags/automation.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [crm](<https://devfeed.tech/tags/crm.md>), [data](<https://devfeed.tech/tags/data.md>), [database](<https://devfeed.tech/tags/database.md>), [edge](<https://devfeed.tech/tags/edge.md>), [functions](<https://devfeed.tech/tags/functions.md>), [help-desk](<https://devfeed.tech/tags/help-desk.md>), [integration](<https://devfeed.tech/tags/integration.md>), [logs](<https://devfeed.tech/tags/logs.md>), [make](<https://devfeed.tech/tags/make.md>), [projects](<https://devfeed.tech/tags/projects.md>), [supabase](<https://devfeed.tech/tags/supabase.md>)

### AI overview

Make connects Supabase to visual automation scenarios and AI agents through pre-built API apps or its MCP Client. The API apps use project credentials for repeatable workflow steps; MCP connects by signing in with OAuth and approving access, then selecting a tool and mapping its inputs. Available actions include querying database data, reading logs, deploying Edge Functions, and managing projects. MCP tools are labeled read-only or destructive before a scenario runs, and Make records scenario runs and agent tool calls in a history that users can inspect. The MCP Client is included on every Make plan; setup for the pre-built apps is in Make's app directory.

### Source excerpt

Connect Supabase to Make with OAuth and bring your database, Edge Functions, logs, and projects into automated scenarios and AI agents.

## OrioleDB public beta: a Postgres storage engine for update-heavy tables

DevFeed: [OrioleDB public beta: a Postgres storage engine for update-heavy tables](<https://devfeed.tech/articles/orioledb-public-beta-a-postgres-storage-engine-for-update-heavy-tables-105587.md>)

Original publisher: [Read original article](<https://supabase.com/blog/orioledb-public-beta>)

Author: Aditya Maruvada; Daniel Mitterdorfer; Alexander Korotkov; Artur Zakirov

Published: 2026-10-28T07:00:00Z

Content type: release

Language: en

Sources: [Supabase](<https://devfeed.tech/sources/supabase-blog.md>)

Topics: [Supabase](<https://devfeed.tech/topics/supabase.md>), [rdbms](<https://devfeed.tech/topics/rdbms.md>), [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>)

Tags: [beta](<https://devfeed.tech/tags/beta.md>), [engine](<https://devfeed.tech/tags/engine.md>), [open](<https://devfeed.tech/tags/open.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [public-beta](<https://devfeed.tech/tags/public-beta.md>), [storage](<https://devfeed.tech/tags/storage.md>), [storage-engine](<https://devfeed.tech/tags/storage-engine.md>), [tables](<https://devfeed.tech/tags/tables.md>), [update](<https://devfeed.tech/tags/update.md>)

### AI overview

OrioleDB is in public beta on Supabase plans as an alternative Postgres storage engine, but it is not ready for production and has no SLA. It replaces heap versions and dead tuples with an automatically reclaimed undo log; stores rows in the primary-key index; and uses copy-on-write checkpoints, row-level WAL, and lock-free page reads. These mechanisms can reduce vacuum work, index writes, lookup reads, and checkpoint I/O. In Supabase's published TPC-C-derived workload, OrioleDB led throughput per dollar when data exceeded memory; on an 8XL instance it reached about 1.8x heap throughput. With data in memory the advantage was smaller, and heap led at Small. Results depend on workload: frequent updates or deletes, large datasets, concurrency, and primary-key lookups may benefit more; read-mostly in-memory workloads or experimental non-B-tree indexes may not. Benchmark your workload. OrioleDB must be selected when creating a project, cannot be added or removed later, and lacks Point-in-Time Recovery. The beta also has unsupported commands and extensions, and is not available in self-hosted Supabase.

### Source excerpt

OrioleDB, an open-source storage engine for Postgres, is in public beta on every Supabase plan.

## ReviveDB: Supabase backups restore-tested against the source schema

DevFeed: [ReviveDB: Supabase backups restore-tested against the source schema](<https://devfeed.tech/articles/revivedb-supabase-backups-restore-tested-against-the-source-schema-105463.md>)

Original publisher: [Read original article](<https://www.postgresql.org/about/news/revivedb-supabase-backups-restore-tested-against-the-source-schema-3422/>)

Published: 2026-10-28T00:00:00Z

Content type: article

Language: en

Sources: [PostgreSQL news](<https://devfeed.tech/sources/postgresql-news.md>)

Topics: [Supabase](<https://devfeed.tech/topics/supabase.md>), [backups](<https://devfeed.tech/topics/backups.md>), [Disaster Recovery](<https://devfeed.tech/topics/disaster-recovery.md>), [database-consistency](<https://devfeed.tech/topics/database-consistency.md>)

Tags: [auth](<https://devfeed.tech/tags/auth.md>), [backups](<https://devfeed.tech/tags/backups.md>), [database](<https://devfeed.tech/tags/database.md>), [edge](<https://devfeed.tech/tags/edge.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [files](<https://devfeed.tech/tags/files.md>), [functions](<https://devfeed.tech/tags/functions.md>), [indexes](<https://devfeed.tech/tags/indexes.md>), [inventory](<https://devfeed.tech/tags/inventory.md>), [policies](<https://devfeed.tech/tags/policies.md>), [policy](<https://devfeed.tech/tags/policy.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [project](<https://devfeed.tech/tags/project.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [restore](<https://devfeed.tech/tags/restore.md>), [row-level-security](<https://devfeed.tech/tags/row-level-security.md>), [schema](<https://devfeed.tech/tags/schema.md>), [supabase](<https://devfeed.tech/tags/supabase.md>), [supabase-backups](<https://devfeed.tech/tags/supabase-backups.md>)

### AI overview

ReviveDB backs up Supabase projects on Postgres 17 outside Supabase and verifies each database backup by restoring it to a temporary PostgreSQL database, then comparing its schema and objects with a source inventory. Checks include tables, row counts, columns, constraints, indexes, sequences, views, functions, triggers, RLS policies, grants and extensions, since matching row counts alone can miss lost constraints or policies. Each run uses a short-lived, read-only Postgres role that can also read rows protected by row-level security. A recovery point includes Auth data, Storage files and Edge Functions, and can be restored to a new Supabase project or to the original after rehearsal on a copy.

### Source excerpt

ReviveDB backs up Supabase projects on Postgres 17 outside Supabase, and restores every database backup into a temporary PostgreSQL database before it counts as verified. The restore is compared with an inventory of the source: tables, rows, columns, constraints, indexes, sequences, views, functions, triggers, RLS policies, grants and extensions. Row counts alone miss a restore that loses a constraint or a policy. Each backup run uses its own short-lived, read-only Postgres role that also reads rows behind row-level security. The same recovery point holds Auth data, Storage files and Edge Functions. A recovery point restores into a new Supabase project, or into the original after a rehearsal on a copy. Free for one project: https://revivedb.dev

## Supabase Compute: run your agents inside your project

DevFeed: [Supabase Compute: run your agents inside your project](<https://devfeed.tech/articles/supabase-compute-run-your-agents-inside-your-project-102719.md>)

Original publisher: [Read original article](<https://supabase.com/blog/supabase-compute-private-alpha>)

Author: Lakshan Perera; Nyannyacha; Matt Johnston; Francesco Sansalvadore

Published: 2026-10-27T07:00:00Z

Content type: release

Language: en

Sources: [Supabase](<https://devfeed.tech/sources/supabase-blog.md>)

Topics: [Supabase](<https://devfeed.tech/topics/supabase.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [alpha](<https://devfeed.tech/tags/alpha.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [background](<https://devfeed.tech/tags/background.md>), [cli](<https://devfeed.tech/tags/cli.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [compute](<https://devfeed.tech/tags/compute.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [dockerfile](<https://devfeed.tech/tags/dockerfile.md>), [embedding](<https://devfeed.tech/tags/embedding.md>), [environment](<https://devfeed.tech/tags/environment.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [jobs](<https://devfeed.tech/tags/jobs.md>), [private](<https://devfeed.tech/tags/private.md>), [supabase](<https://devfeed.tech/tags/supabase.md>)

### AI overview

Supabase Compute runs agents, APIs, and background jobs inside a Supabase project's Linux environment, keeping workloads near project data. It supports Node, Deno, or Dockerfile deployments, with services sized at 2 GB/1 vCPU or 4 GB/2 vCPUs and configured through the Supabase CLI (v2.120.0 or later); alpha Management API endpoints can also deploy, list, and delete services. The private alpha is for evaluation, may change or end, and is limited to projects in us-west-2. Services may restart, so long-running work should be saved to Postgres; they receive all project secrets. There is no autoscaling, GPU, or persistent disk. Public services suspend when idle, while private services keep running. Sandboxes for AI agents are not included.

### Source excerpt

Supabase Compute is in private alpha and runs your agents and background jobs inside your Supabase project.

## Three layers, all config: how DigitalOcean Managed Agents enforce NVIDIA OpenShell-aligned boundaries

DevFeed: [Three layers, all config: how DigitalOcean Managed Agents enforce NVIDIA OpenShell-aligned boundaries](<https://devfeed.tech/articles/three-layers-all-config-how-digitalocean-managed-agents-enforce-nvidia-openshell-aligned-boundaries-100676.md>)

Original publisher: [Read original article](<https://www.digitalocean.com/blog/managed-agents-enforce-nvidia-openshell>)

Author: Rohit Bhattacharjee

Published: 2026-10-26T17:21:41Z

Content type: article

Language: en

Sources: [DigitalOcean](<https://devfeed.tech/sources/digitalocean.md>)

Topics: [Digital Ocean](<https://devfeed.tech/topics/digital-ocean.md>), [Agent Harness](<https://devfeed.tech/topics/agent-harness.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [human in the loop agent](<https://devfeed.tech/topics/human-in-the-loop-agent.md>), [Supabase](<https://devfeed.tech/topics/supabase.md>), [OpenShell](<https://devfeed.tech/topics/openshell.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [agents-in-production](<https://devfeed.tech/tags/agents-in-production.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-native](<https://devfeed.tech/tags/ai-native.md>), [config](<https://devfeed.tech/tags/config.md>), [data](<https://devfeed.tech/tags/data.md>), [database](<https://devfeed.tech/tags/database.md>), [digitalocean](<https://devfeed.tech/tags/digitalocean.md>), [digitalocean-managed-agents](<https://devfeed.tech/tags/digitalocean-managed-agents.md>), [embeddings](<https://devfeed.tech/tags/embeddings.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [managed](<https://devfeed.tech/tags/managed.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [nvidia](<https://devfeed.tech/tags/nvidia.md>), [nvidia-openshell](<https://devfeed.tech/tags/nvidia-openshell.md>), [openshell](<https://devfeed.tech/tags/openshell.md>), [partner-news](<https://devfeed.tech/tags/partner-news.md>)

### AI overview

A DigitalOcean Managed Agent migrated huffl's production backend from Supabase, handling a database with 31 tables and 145,432 rows, three storage buckets, and about 31,000 vector embeddings. The excerpt says the agent provisioned the database, loaded access policies, mapped Supabase features to DigitalOcean equivalents, and verified data table by table. DigitalOcean Managed Agents is in public preview, without an SLA and subject to preview terms. Its Harness Runtime gives each session a Firecracker microVM that can pause, resume, and fork; Action Gateway provides a managed MCP endpoint to more than 16,000 tools, brokers credentials at call time, and offers human approval for sensitive actions. The platform is described as open by default, letting users bring their own harness, model, or key. The excerpt cuts off before describing the three boundary layers in detail.

### Source excerpt

A few weeks ago, we handed an AI agent one of the scariest jobs in infrastructure: moving huffl's production backend from Supabase to DigitalOcean. huffl.ai is a real product. Underneath it sits 31 tables, 145,432 rows, three storage buckets, and about 31,000 vector embeddings. A DigitalOcean Managed Agent did the migration, directed from a phone in plain chat. It provisioned the database, loaded the access policies, mapped every Supabase feature to its DigitalOcean counterpart, and verified the data table by table. There is something magical about watching that happen. A message typed while waiting for coffee. A decision made between meetings. No laptop, no terminal, no maintenance window. By the end of the week the backend had moved, and nobody worked a late night. But magic is not a security model. For days, the agent had the run of two clouds and touched production data the entire time. What is worth examining is how it stayed inside its boundaries while doing it: how to hand an agent that much power without handing it a key, and how to draw lines it cannot cross. Three layers. All config. What is DigitalOcean Managed Agents? DigitalOcean Managed Agents is our platform for running AI agents in production, now in public preview, so you don't have to build the plumbing yourself. Public preview products are provided without a service level agreement and are subject to the DigitalOcean preview terms; features may change or be withdrawn before general availability. DigitalOcean Harness Runtime gives every session its own Firecracker microVM, and sessions keep running, pause, resume, and fork even after you close your laptop. Action Gateway gives agents one managed MCP endpoint to more than 16,000 tools as of October 2026, with credentials brokered at the moment of the call and human approval available for sensitive actions. It runs on the DigitalOcean AI-Native Cloud and is open by default, so you bring your own harness, model, or key. Here's how it stayed inside its

## Give your Supabase app its own MCP server

DevFeed: [Give your Supabase app its own MCP server](<https://devfeed.tech/articles/give-your-supabase-app-its-own-mcp-server-96182.md>)

Original publisher: [Read original article](<https://supabase.com/blog/give-your-supabase-app-its-own-mcp-server>)

Author: Raúl Barroso; Greg Richardson; Saxon Fletcher

Published: 2026-10-22T07:00:00Z

Content type: tutorial

Language: en

Sources: [Supabase](<https://devfeed.tech/sources/supabase-blog.md>)

Topics: [Supabase](<https://devfeed.tech/topics/supabase.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [Web app](<https://devfeed.tech/topics/webapp.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [actions](<https://devfeed.tech/tags/actions.md>), [ads](<https://devfeed.tech/tags/ads.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [apps](<https://devfeed.tech/tags/apps.md>), [auth](<https://devfeed.tech/tags/auth.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [backends](<https://devfeed.tech/tags/backends.md>), [browser](<https://devfeed.tech/tags/browser.md>), [call](<https://devfeed.tech/tags/call.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [rls](<https://devfeed.tech/tags/rls.md>), [server](<https://devfeed.tech/tags/server.md>), [supabase](<https://devfeed.tech/tags/supabase.md>), [tool](<https://devfeed.tech/tags/tool.md>), [user](<https://devfeed.tech/tags/user.md>)

### AI overview

Supabase's MCP Server block lets customers use app actions from ChatGPT, Claude, or other compatible clients while each tool call uses the signed-in user's identity, so Postgres RLS policies govern accessible rows. Install the block to add an Edge Function with an MCP handler, authentication middleware, and a sample identity tool; register app-specific tools using the supplied user-scoped Supabase client. OAuth handles sign-in and consent, and setup requires asymmetric signing keys, the OAuth 2.1 server, dynamic client registration, a consent page, the correct Auth Site URL, and disabling the function's built-in JWT check for discovery requests. Tools can call database functions, Edge Functions, or existing APIs; business rules should remain in shared application logic. The helpers also support standard Web Request/Response backends such as Cloudflare Workers. MCP Apps can display reused app UI in clients that support the extension. The excerpt describes a Sizzle demo but does not establish broader client compatibility beyond those stated.

### Source excerpt

Every tool call runs as the signed-in user, so the RLS you already wrote decides what each agent reaches.

## BackupDrill: open-source Supabase Postgres backups with automated restore drills

DevFeed: [BackupDrill: open-source Supabase Postgres backups with automated restore drills](<https://devfeed.tech/articles/backupdrill-open-source-supabase-postgres-backups-with-automated-restore-drills-95073.md>)

Original publisher: [Read original article](<https://www.postgresql.org/about/news/backupdrill-open-source-supabase-postgres-backups-with-automated-restore-drills-3413/>)

Published: 2026-10-22T00:00:00Z

Content type: article

Language: en

Sources: [PostgreSQL news](<https://devfeed.tech/sources/postgresql-news.md>)

Topics: [Supabase](<https://devfeed.tech/topics/supabase.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [alerts](<https://devfeed.tech/tags/alerts.md>), [automated](<https://devfeed.tech/tags/automated.md>), [backup](<https://devfeed.tech/tags/backup.md>), [backups](<https://devfeed.tech/tags/backups.md>), [cli](<https://devfeed.tech/tags/cli.md>), [container](<https://devfeed.tech/tags/container.md>), [dump](<https://devfeed.tech/tags/dump.md>), [email](<https://devfeed.tech/tags/email.md>), [engine](<https://devfeed.tech/tags/engine.md>), [free](<https://devfeed.tech/tags/free.md>), [github](<https://devfeed.tech/tags/github.md>), [indexes](<https://devfeed.tech/tags/indexes.md>), [latest](<https://devfeed.tech/tags/latest.md>), [mit](<https://devfeed.tech/tags/mit.md>), [npm](<https://devfeed.tech/tags/npm.md>), [open](<https://devfeed.tech/tags/open.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [restore](<https://devfeed.tech/tags/restore.md>), [supabase](<https://devfeed.tech/tags/supabase.md>)

### AI overview

BackupDrill checks whether Supabase Postgres backups can actually be restored: its drill restores the latest snapshot into a throwaway PostgreSQL container, verifies the archive checksum and restore completion, checks post-data objects and table presence, flags tables that previously held data if they are empty, and records restore time. The excerpt says the MIT-licensed CLI supports Supabase-hosted PostgreSQL, dumps the public schema by default, and allows additional schemas. A hosted service runs the same engine on a schedule and emails alerts for failed backups or drills; a free plan is available.

### Source excerpt

BackupDrill backs up Supabase Postgres databases to a bucket you own, then restores each backup into a throwaway PostgreSQL instance to check it restores. Most teams find out whether their pg_dump backups work on the day they need them. BackupDrill makes that check a routine step. What it does: Runs pg_dump (custom format) against a Supabase project and streams the archive to any S3-compatible bucket (AWS S3, Cloudflare R2, Backblaze B2, Wasabi), with a checksummed manifest. Storage files can be copied into the same snapshot. backupdrill drill restores the latest snapshot into a throwaway PostgreSQL container with pg_restore. It checks the archive checksum, that pg_restore completed, that post-data objects such as indexes, constraints and triggers were created, that every table is present and that tables which held data are not empty, and it records how long the restore took. Backups are plain pg_dump archives, so stock pg_restore can restore them without BackupDrill. It refuses to run a pg_dump whose major version is older than the server's. Supabase currently runs PostgreSQL 15 to 17. Scope: Supabase-hosted PostgreSQL only for now; the public schema is dumped by default and other schemas can be added. The CLI is MIT-licensed: https://github.com/backupdrill/cli (npm package: backupdrill). The hosted service at https://backupdrill.com runs the same engine on a schedule, with restore drills and email alerts when a backup or drill fails. It has a free plan.

## Sync real-time Stripe data to Supabase with Stripe Data Pipeline

DevFeed: [Sync real-time Stripe data to Supabase with Stripe Data Pipeline](<https://devfeed.tech/articles/sync-real-time-stripe-data-to-supabase-with-stripe-data-pipeline-88089.md>)

Original publisher: [Read original article](<https://supabase.com/blog/stripe-data-pipeline-now-syncs-real-time-data-to-supabase>)

Author: Gregor Vand; Saba Pochkhua; Etienne Stalmans

Published: 2026-10-15T07:00:00Z

Content type: release

Language: en

Sources: [Supabase](<https://devfeed.tech/sources/supabase-blog.md>)

Topics: [Supabase](<https://devfeed.tech/topics/supabase.md>), [Firestore](<https://devfeed.tech/topics/firestore.md>)

Tags: [data](<https://devfeed.tech/tags/data.md>), [data-pipeline](<https://devfeed.tech/tags/data-pipeline.md>), [database](<https://devfeed.tech/tags/database.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [stripe](<https://devfeed.tech/tags/stripe.md>), [supabase](<https://devfeed.tech/tags/supabase.md>)

### AI overview

Stripe Data Pipeline now syncs payment, customer, subscription, and other Stripe data directly to Supabase Postgres. It backfills historical records and keeps them updated without requiring teams to maintain webhooks or work around API rate limits. The article describes the setup, schema-scoped access and short-lived credentials, and ways to query the synced data alongside application data for subscription checks and revenue metrics.

### Source excerpt

Sync real-time Stripe data to Supabase from the Stripe Dashboard. Data Pipeline backfills and keeps it in sync, with no webhooks or rate limits to manage.

## Supabase Middleware: composable, reusable middleware for Web Fetch handlers

DevFeed: [Supabase Middleware: composable, reusable middleware for Web Fetch handlers](<https://devfeed.tech/articles/supabase-middleware-composable-reusable-middleware-for-web-fetch-handlers-88789.md>)

Original publisher: [Read original article](<https://supabase.com/blog/supabase-middleware>)

Author: Tomás Pozo; Katerina Skroumpelou

Published: 2026-10-15T07:00:00Z

Content type: article

Language: en

Sources: [Supabase](<https://devfeed.tech/sources/supabase-blog.md>)

Topics: [middleware](<https://devfeed.tech/topics/middleware.md>), [Supabase](<https://devfeed.tech/topics/supabase.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>)

Tags: [middleware](<https://devfeed.tech/tags/middleware.md>), [supabase](<https://devfeed.tech/tags/supabase.md>), [type-safe](<https://devfeed.tech/tags/type-safe.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

Supabase introduces @supabase/middleware, a TypeScript library for composing reusable, type-safe middleware for Web Fetch handlers. Pipelines can run across fetch-compatible runtimes and integrate with frameworks through small bridge files. The article shows middleware for CORS, JWT claims, scoped Supabase clients, OAuth discovery for MCP servers, and custom request logic.

### Source excerpt

Type-safe, composable middleware for Web Fetch handlers. Write it once, use it on any fetch runtime or inside a framework.

## How a new branch gets its config, migrations, and functions

DevFeed: [How a new branch gets its config, migrations, and functions](<https://devfeed.tech/articles/how-a-new-branch-gets-its-config-migrations-and-functions-88087.md>)

Original publisher: [Read original article](<https://supabase.com/blog/how-a-new-branch-gets-its-config-migrations-and-functions>)

Author: Qiao Han

Published: 2026-10-15T07:00:00Z

Content type: tutorial

Language: en

Sources: [Supabase](<https://devfeed.tech/sources/supabase-blog.md>)

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Supabase](<https://devfeed.tech/topics/supabase.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [cli](<https://devfeed.tech/tags/cli.md>), [database](<https://devfeed.tech/tags/database.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [github](<https://devfeed.tech/tags/github.md>), [github-integration](<https://devfeed.tech/tags/github-integration.md>), [migrations](<https://devfeed.tech/tags/migrations.md>)

### AI overview

The article explains how Supabase preview branches receive configuration, database migrations, and Edge Functions. It describes how GitHub-connected and gitless branches source their inputs, how workflow steps run and retry, how migrations execute transactionally, and how function deployments skip unchanged bundles.

### Source excerpt

What runs when you create a branch: which settings are copied, where your migrations and functions come from, and what order the steps run in.

## A local Supabase project per agent, with or without Docker

DevFeed: [A local Supabase project per agent, with or without Docker](<https://devfeed.tech/articles/a-local-supabase-project-per-agent-with-or-without-docker-88088.md>)

Original publisher: [Read original article](<https://supabase.com/blog/local-supabase-project-per-agent-with-or-without-docker>)

Author: Julien Goux; Wen Bo Xie

Published: 2026-10-14T07:00:00Z

Content type: release

Language: en

Sources: [Supabase](<https://devfeed.tech/sources/supabase-blog.md>)

Topics: [Supabase](<https://devfeed.tech/topics/supabase.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Local AI](<https://devfeed.tech/topics/local-ai.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [build](<https://devfeed.tech/tags/build.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cli](<https://devfeed.tech/tags/cli.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [container](<https://devfeed.tech/tags/container.md>), [git](<https://devfeed.tech/tags/git.md>), [supabase](<https://devfeed.tech/tags/supabase.md>)

### AI overview

Supabase CLI v2.119.0 adds support for multiple local projects, including one per Git worktree, so coding agents can work with isolated databases and services. It also introduces an experimental native runtime for supported Linux and macOS systems without Docker, while local services start on demand and use less memory. Remote branches now inherit project configuration and are created faster.

### Source excerpt

Run several local Supabase projects on one machine, one per coding agent, with or without Docker. Faster starts, less memory, and branches ready in seconds.

## Under the hood, off the hot path: How D1 scales to millions of databases

DevFeed: [Under the hood, off the hot path: How D1 scales to millions of databases](<https://devfeed.tech/articles/under-the-hood-off-the-hot-path-how-d1-scales-to-millions-of-databases-86353.md>)

Original publisher: [Read original article](<https://blog.cloudflare.com/d1-control-plane/>)

Author: Lambros Petrou

Published: 2026-10-13T16:20:18Z

Content type: article

Language: en

Sources: [Cloudflare Blog](<https://devfeed.tech/sources/cloudflare-blog.md>)

Topics: [control-plane](<https://devfeed.tech/topics/control-plane.md>), [Supabase](<https://devfeed.tech/topics/supabase.md>), [database-optimization](<https://devfeed.tech/topics/database-optimization.md>), [Service fabric](<https://devfeed.tech/topics/service-fabric.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [caching](<https://devfeed.tech/tags/caching.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [d1](<https://devfeed.tech/tags/d1.md>), [databases](<https://devfeed.tech/tags/databases.md>), [deep-dive](<https://devfeed.tech/tags/deep-dive.md>), [developer-platform](<https://devfeed.tech/tags/developer-platform.md>), [edge-database](<https://devfeed.tech/tags/edge-database.md>), [scale](<https://devfeed.tech/tags/scale.md>), [sql](<https://devfeed.tech/tags/sql.md>), [workers](<https://devfeed.tech/tags/workers.md>)

### AI overview

Cloudflare describes how it scaled D1's control plane to support millions of managed SQLite databases while keeping query traffic off centralized components. The article explains edge routing, Workers KV and Hyperdrive caching, self-correcting database heartbeats, asynchronous usage processing, and pre-aggregation to reduce database load and write contention.

### Source excerpt

A deep dive into how D1 architected its control plane to scale and manage millions of databases, while keeping data plane query operations at the edge. We share guiding principles on how to build on the Developer Platform effectively.

## Postgres at Open House NYC

DevFeed: [Postgres at Open House NYC](<https://devfeed.tech/articles/postgres-at-open-house-nyc-86381.md>)

Original publisher: [Read original article](<https://clickhouse.com/blog/postgres-at-open-house-nyc>)

Author: Sai Srirampur; Kaushik Iska

Published: 2026-10-13T15:35:19Z

Content type: news

Language: en

Sources: [ClickHouse Blog](<https://devfeed.tech/sources/clickhouse-blog.md>)

Topics: [Heroku Postgres](<https://devfeed.tech/topics/heroku-postgres.md>), [Supabase](<https://devfeed.tech/topics/supabase.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [alloydb](<https://devfeed.tech/tags/alloydb.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-sql](<https://devfeed.tech/tags/cloud-sql.md>), [cloud-storage](<https://devfeed.tech/tags/cloud-storage.md>), [postgres](<https://devfeed.tech/tags/postgres.md>)

### AI overview

ClickHouse describes an integrated Postgres and ClickHouse stack for transactional and analytical workloads, including Managed Postgres, native CDC, the WalShadow replication engine, and a chdb Postgres extension. It reports WalShadow benchmark results and a live demo, and announces private preview availability on Google Cloud.

### Source excerpt

At Open House NYC, we showed how ClickHouse Managed Postgres and ClickHouse work as one stack, with a live WalShadow demo replicating Postgres into ClickHouse in under a second, plus the same-week Google Cloud and chdb extension launches.

## Ship changes to your Supabase backend with Grok Bot

DevFeed: [Ship changes to your Supabase backend with Grok Bot](<https://devfeed.tech/articles/ship-changes-to-your-supabase-backend-with-grok-bot-86233.md>)

Original publisher: [Read original article](<https://supabase.com/blog/ship-changes-to-your-supabase-backend-with-grok-bot>)

Author: Nick Littman; Elsa Heffernan; Shaziya Bandukia

Published: 2026-10-13T07:00:00Z

Content type: article

Language: en

Sources: [Supabase](<https://devfeed.tech/sources/supabase-blog.md>)

Topics: [Supabase](<https://devfeed.tech/topics/supabase.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [function calling](<https://devfeed.tech/topics/function-calling.md>), [Kiro](<https://devfeed.tech/topics/kiro.md>), [Discord](<https://devfeed.tech/topics/discord.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [cursor](<https://devfeed.tech/tags/cursor.md>), [database](<https://devfeed.tech/tags/database.md>), [grok-bot](<https://devfeed.tech/tags/grok-bot.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [payments](<https://devfeed.tech/tags/payments.md>), [performance](<https://devfeed.tech/tags/performance.md>), [supabase](<https://devfeed.tech/tags/supabase.md>)

### AI overview

Supabase describes an integration in which Grok Bot accepts change requests in chat and Cursor performs scoped work on a Supabase backend through the Supabase MCP server. The article explains how Cursor can inspect schemas and logs, query databases, deploy Edge Functions, and verify changes with security and performance checks.

### Source excerpt

Supabase joins the SpaceXAI Partner Network: request a change in chat with Grok Bot, and Cursor builds and runs it on your Supabase backend.

## Introducing the unified Supabase .NET SDK

DevFeed: [Introducing the unified Supabase .NET SDK](<https://devfeed.tech/articles/introducing-the-unified-supabase-net-sdk-85140.md>)

Original publisher: [Read original article](<https://supabase.com/blog/introducing-the-unified-supabase-net-sdk>)

Author: Guillaume Faas

Published: 2026-10-12T10:25:54.609005Z

Content type: release

Language: en

Sources: [Supabase](<https://devfeed.tech/sources/supabase-blog.md>)

Topics: [Supabase](<https://devfeed.tech/topics/supabase.md>), [.NET](<https://devfeed.tech/topics/net.md>), [versioning](<https://devfeed.tech/topics/versioning.md>), [ASP.NET Core](<https://devfeed.tech/topics/asp-net-core.md>)

Tags: [dependency-injection](<https://devfeed.tech/tags/dependency-injection.md>), [migration](<https://devfeed.tech/tags/migration.md>), [net-sdk](<https://devfeed.tech/tags/net-sdk.md>)

### AI overview

Supabase .NET SDK v8 consolidates its packages into one repository with synchronized version numbers. It adds a dependency injection extension, switches serialization to System.Text.Json, and introduces configurable retries with backoff. A migration guide covers breaking changes.

### Source excerpt

The Supabase .NET libraries move to a single repo, with a unified version number.

## Getting started with the Supabase .NET SDK

DevFeed: [Getting started with the Supabase .NET SDK](<https://devfeed.tech/articles/getting-started-with-the-supabase-net-sdk-85139.md>)

Original publisher: [Read original article](<https://supabase.com/blog/getting-started-with-the-supabase-dotnet-sdk>)

Author: Guillaume Faas

Published: 2026-10-12T10:25:54.609005Z

Content type: tutorial

Language: en

Sources: [Supabase](<https://devfeed.tech/sources/supabase-blog.md>)

Topics: [Supabase](<https://devfeed.tech/topics/supabase.md>), [C#](<https://devfeed.tech/topics/csharp.md>), [.NET](<https://devfeed.tech/topics/net.md>), [ASP.NET Core](<https://devfeed.tech/topics/asp-net-core.md>), [SDK](<https://devfeed.tech/topics/sdk.md>), [Quasar](<https://devfeed.tech/topics/quasar.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [asp-net](<https://devfeed.tech/tags/asp-net.md>), [asp-net-core](<https://devfeed.tech/tags/asp-net-core.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [connection-pool](<https://devfeed.tech/tags/connection-pool.md>), [console](<https://devfeed.tech/tags/console.md>), [database](<https://devfeed.tech/tags/database.md>), [dependency-injection](<https://devfeed.tech/tags/dependency-injection.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [net-sdk](<https://devfeed.tech/tags/net-sdk.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [supabase](<https://devfeed.tech/tags/supabase.md>), [unity](<https://devfeed.tech/tags/unity.md>)

### AI overview

This tutorial introduces the Supabase .NET SDK and its version 8.0.0 changes, then demonstrates setup and common operations in C#. It explains dependency injection and HttpClient reuse in ASP.NET Core, client initialization in other app types, and working with database queries, authentication, and file storage. It also advises using publishable or anon keys in client applications and keeping secret or service keys on the server.

### Source excerpt

How to set up and use the Supabase C# client in .NET, for ASP.NET Core, Console Apps, Desktop, Unity and Mobile.

## Five Supabase Backup Failure Modes and How to Restore-Test for Them

DevFeed: [Five Supabase Backup Failure Modes and How to Restore-Test for Them](<https://devfeed.tech/articles/five-supabase-backup-failure-modes-and-how-to-restore-test-for-them-85088.md>)

Original publisher: [Read original article](<https://hackernoon.com/five-supabase-backup-failure-modes-and-how-to-restore-test-for-them?source=rss>)

Author: Super Lede

Published: 2026-10-11T21:12:20Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [backups](<https://devfeed.tech/topics/backups.md>), [Supabase](<https://devfeed.tech/topics/supabase.md>), [Disaster Recovery](<https://devfeed.tech/topics/disaster-recovery.md>)

Tags: [backup](<https://devfeed.tech/tags/backup.md>), [backup-verification](<https://devfeed.tech/tags/backup-verification.md>), [checksums](<https://devfeed.tech/tags/checksums.md>), [cli](<https://devfeed.tech/tags/cli.md>), [cron](<https://devfeed.tech/tags/cron.md>), [database](<https://devfeed.tech/tags/database.md>), [database-recovery](<https://devfeed.tech/tags/database-recovery.md>), [database-restore-testing](<https://devfeed.tech/tags/database-restore-testing.md>), [docker](<https://devfeed.tech/tags/docker.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [pg-dump](<https://devfeed.tech/tags/pg-dump.md>), [postgresql-backups](<https://devfeed.tech/tags/postgresql-backups.md>), [restore](<https://devfeed.tech/tags/restore.md>), [storage](<https://devfeed.tech/tags/storage.md>), [supabase](<https://devfeed.tech/tags/supabase.md>), [supabase-backups](<https://devfeed.tech/tags/supabase-backups.md>), [supabase-database](<https://devfeed.tech/tags/supabase-database.md>), [test](<https://devfeed.tech/tags/test.md>)

### AI overview

The article describes five ways Supabase backups can fail despite appearing complete: database dumps may omit rows, database backups exclude uploaded Storage files, some platform backups cannot be downloaded, restores to plain Postgres can skip tables with Supabase-specific dependencies, and scheduled backups can become stale without alerts. It recommends regularly restoring the latest backup in a disposable Postgres environment and checking table and row counts, recency, and Storage file checksums.

### Source excerpt

Five Supabase backup setups that look fine until you restore them, from dumps with no rows to lost Storage files, and a 15-minute check that catches them.

## Load terabytes of data in minutes into Lakebase Postgres

DevFeed: [Load terabytes of data in minutes into Lakebase Postgres](<https://devfeed.tech/articles/load-terabytes-of-data-in-minutes-into-lakebase-postgres-77640.md>)

Original publisher: [Read original article](<https://www.databricks.com/blog/load-terabytes-data-minutes-lakebase-postgres>)

Author: Yecheng Yang; Nolan Biscaro; Szu-Po Wang; Pranav Aurora

Published: 2026-10-08T18:49:31Z

Content type: article

Language: en

Sources: [Databricks](<https://devfeed.tech/sources/databricks.md>)

Topics: [Supabase](<https://devfeed.tech/topics/supabase.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [table-partitioning](<https://devfeed.tech/topics/table-partitioning.md>)

Tags: [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [b-tree](<https://devfeed.tech/tags/b-tree.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [database](<https://devfeed.tech/tags/database.md>), [databases](<https://devfeed.tech/tags/databases.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [lakebase](<https://devfeed.tech/tags/lakebase.md>), [postgres](<https://devfeed.tech/tags/postgres.md>)

### AI overview

The article describes Databricks Lakebase Postgres's LTAP architecture for moving large bulk loads from the primary database to distributed Spark processing. It details how Spark-generated heap and index data are validated and staged in object storage before the destination database publishes it, and reports an internal benchmark of loading 1 TB in under five minutes, with index builds not yet parallelized.

### Source excerpt

Operational databases like Postgres are built to reliably execute highly concurrent...

[Next page](<https://devfeed.tech/topics/supabase.md?cursor=WyIyMDI2LTEwLTA4VDE4OjQ5OjMxKzAwOjAwIiwgImQxNGMyNmNiLTUxYjEtNDc3My1hMzViLWIxN2U3N2FhYzIzMCJd>)