Providers
Managed cloud SQL and Redis providers behind oke's postgres and redis drivers — dashboard click-paths, pooling, and gotchas.
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.
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.
SQL providers
Managed Postgres-wire databases — set DATABASE_URL, driver stays postgres.
Neon
Connect widget · pooled vs direct · cold start.
Supabase
Connect modes · :6543 vs :5432 · free pause.
CockroachDB
Connect dialog · verify-full · CA cert.
YugabyteDB
YSQL on :5433 · Connect → Application.
Redis providers
Managed Redis-wire caches — set REDIS_URL, driver stays redis.
{ durable: true } KV lives in your SQL database, not a second Redis.
Redis Cloud
Configuration tab · Connect wizard · rediss://
Amazon ElastiCache
Primary Endpoint · Redis OSS ≤7.1.
Google Memorystore
Primary Endpoint IP · TLS on 6378.
Azure Cache for Redis
Access keys · TLS port 6380.
Upstash
TCP rediss:// — not REST tokens.
Dragonfly Cloud
Data store drawer · Connection URI.
DigitalOcean Managed Caching
Connection Details · trusted sources.
Learn more
- Recipes — self-hosted recipes for the same protocols
- Store —
sql/kvfacets - Environment variables — URL precedence