Every provider below speaks a protocol oke already drives — Postgres wire or Redis wire.
Hand the connection string to that driver; no new driver id, no Flow code changes.

These managed providers are real, working infrastructure choices behind the same two templates (`standard`, `advanced`) and the same eight elements — not alternative products or separate frameworks.

<Callout title="The one rule">
  Vendor choice lives in a connection URL (`DATABASE_URL` / `REDIS_URL`) — never in
  `drivers.store.sql` / `drivers.store.kv`, which only ever say `postgres` or `redis`.
</Callout>

## SQL providers

Managed Postgres-wire databases — set `DATABASE_URL`, driver stays `postgres`.

<Cards>
  <Card
    title="Neon"
    description="Connect widget · pooled vs direct · cold start."
    href="/docs/providers/neon"
  />
  <Card
    title="Supabase"
    description="Connect modes · :6543 vs :5432 · free pause."
    href="/docs/providers/supabase"
  />
  <Card
    title="CockroachDB"
    description="Connect dialog · verify-full · CA cert."
    href="/docs/providers/cockroachdb"
  />
  <Card
    title="YugabyteDB"
    description="YSQL on :5433 · Connect → Application."
    href="/docs/providers/yugabytedb"
  />
</Cards>

## Redis providers

Managed Redis-wire caches — set `REDIS_URL`, driver stays `redis`.
`{ durable: true }` KV lives in your SQL database, not a second Redis.

<Cards>
  <Card
    title="Redis Cloud"
    description="Configuration tab · Connect wizard · rediss://"
    href="/docs/providers/redis-cloud"
  />
  <Card
    title="Amazon ElastiCache"
    description="Primary Endpoint · Redis OSS ≤7.1."
    href="/docs/providers/elasticache"
  />
  <Card
    title="Google Memorystore"
    description="Primary Endpoint IP · TLS on 6378."
    href="/docs/providers/memorystore"
  />
  <Card
    title="Azure Cache for Redis"
    description="Access keys · TLS port 6380."
    href="/docs/providers/azure-redis"
  />
  <Card
    title="Upstash"
    description="TCP rediss:// — not REST tokens."
    href="/docs/providers/upstash"
  />
  <Card
    title="Dragonfly Cloud"
    description="Data store drawer · Connection URI."
    href="/docs/providers/dragonfly-cloud"
  />
  <Card
    title="DigitalOcean Managed Caching"
    description="Connection Details · trusted sources."
    href="/docs/providers/digitalocean-caching"
  />
</Cards>

## Learn more

- [Recipes](/docs/recipes) — self-hosted recipes for the same protocols
- [Store](/docs/elements/store) — `sql` / `kv` facets
- [Environment variables](/docs/reference/environment-variables) — URL precedence

## Next

<Cards>
  <Card
    title="Neon"
    description="Start with a serverless SQL option."
    href="/docs/providers/neon"
  />
  <Card title="Recipes" description="Run the same protocols yourself." href="/docs/recipes" />
  <Card title="Store" description="The facets these drivers back." href="/docs/elements/store" />
</Cards>