PostgreSQL
Shared Postgres driver: connection, introspection, and parameterized SELECT. Hosted products reuse this.
@db-sdk/postgres
A driver is the database. A hosted provider is the product that opens it — @db-sdk/supabase uses @db-sdk/postgres.
Shared database implementations. One package per query family. Hosted providers reuse these.
Shared Postgres driver: connection, introspection, and parameterized SELECT. Hosted products reuse this.
@db-sdk/postgres
Document driver. Catalog from collections and samples. Native filters, not SQL.
@db-sdk/firestore
SQL driver on the same contract as Postgres. Query language stays MySQL.
@db-sdk/mysql
Relational driver for MSSQL reads. Native T-SQL, not a Postgres dialect.
@db-sdk/sqlserver
Document driver with Mongo's read API. Not Firestore filters rewritten as BSON.
@db-sdk/mongodb
Implement the provider contract for a new database type. Hosted products that speak that type should reuse the driver, not fork it.
docs/architecture.md
Product OAuth and resolve on top of a driver. Supabase opens Postgres; many providers can share one driver.
Hosted provider: OAuth, project list, pooler resolve, then the Postgres driver for reads.
@db-sdk/supabase
Hosted Postgres provider on the same driver. Until it ships, a Neon URI works with @db-sdk/postgres.
@db-sdk/neon
Postgres on RDS or Aurora. Use the Postgres driver with the instance URI (no separate package).
via @db-sdk/postgres
Google OAuth, then the Firestore driver. The host does not collect a service account.
via @db-sdk/firestore
MySQL-compatible Vitess. Will use the MySQL driver when that package ships.
via @db-sdk/mysql
Managed MongoDB. Will use the MongoDB driver when that package ships.
via @db-sdk/mongodb