# Databases page (managed Postgres) — Render-consistent — candidate milestone

Wire a managed-Postgres page to bex-api's Render-shaped database GraphQL: `databases` / `database(id)` / `databaseConnectionInfo(id)` queries + `createDatabase` / `deleteDatabase` mutations (`docs/ADR006-bex-api.md`). Match Render's **dashboard** noun (`database`, not the REST `postgres`) and its database-detail IA (status, connection info, credentials).

Milestone-sized (list + detail + create/delete + connection-info reveal, plus states) → **promote to a milestone when scoped**, don't build as a loose note. Deferred behind the services/logs arc (m4–m6): Render exposes suspend/resume/failover/PITR/credentials/pooler that bex-api marks deferred (unbuilt features), so scope the page to what bex-api actually serves today and flag the rest as gaps.

Source: `/pm-brainstorm for w5` (2026-07-06) + "consistent with render.com". Goal: dashboard pillar, pillar-1 API-first (already-exposed ops).

> **Promoted 2026-07-08** → milestone `w5/m8` (Databases page) via `/pm promote w5/001`.
