Supavisor

Cloud-native multi-tenant Postgres connection pooler that runs as a distributed cluster.

Provider
default
Category
Data
Properties · 2 set by this component
propertytypevaluesrequiredkind defaultthis component
clustered · component propertyboolean—notrueinherited
hedging · advancedboolean—nofalseinherited
loadShedding · advancedboolean—nofalseinherited
managedboolean—nofalseinherited
multiTenant · component propertyboolean—notrueinherited
poolMode · component propertyenumtransaction | sessionnotransactioninherited
poolSharded · advancedboolean—nofalseinherited
poolingboolean—notrue▸ true
requestCoalescing · advancedboolean—nofalseinherited
routingenumnone | shard-key | lookupnonone▸ none
scatterGather · advancedboolean—nofalseinherited
Rules that apply · 0

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

No rule reads this kind yet. That is a gap, not a guarantee.
Use it in a design
nodes:
  - { id: "supavisor", component: "supavisor" }
Other Database proxy products · 13
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# Supavisor: scalable cloud-native Postgres connection pooler from Supabase, run as a
# distributed multi-node cluster. README: transaction pooling is what ships today,
# session pooling is on the roadmap; tenants are held in a highly available Postgres.
schemaVersion: "1"
type: "component"
id: "supavisor"
kind: "database-proxy"
provider: "default"
docs: "https://github.com/supabase/supavisor"
defaults:
  pooling: true
  routing: "none"
properties:
  poolMode:
    type: "enum"
    values: ["transaction", "session"]
    default: "transaction"
  multiTenant:
    type: "boolean"
    default: true
  clustered:
    type: "boolean"
    default: true

The same page as markdown, for an agent: /catalogue/components/supavisor.md