---
id: w1/m13/t003
title: UI parity — dashboard/ vs Render's dashboard IA, page-by-page
worker: worker1
status: done
estimate: 30m
depends_on: []
---

## Objective

Compare bex's dashboard against Render's, page-by-page: services list, service detail tabs (overview/env/logs/metrics/plan/settings — bex has these; what does Render have that bex lacks: events, deploys, shell, disks, scaling?), databases pages (w5/m8 is queued — record as planned), account/settings, team/members. Record per-page: present / partial / missing / deliberate divergence.

## Context

- bex routes: `dashboard/src/routes/` (services.$serviceId.* tree, settings, auth); features in `dashboard/src/features/`.
- Render side: live dashboard (read-only browsing via Playwright) + `docs/render-artifacts/`.
- w5's open/done milestones already map some of this (m4 services list, m6 logs, m7 settings/instance picker, m8 databases planned) — cross-reference instead of re-deriving.

## Steps

1. Enumerate Render's dashboard nav + service-detail tabs (screenshot each into `.playwright-mcp/`, read-only).
2. Map to bex routes/features; record status per page/tab.
3. Emit the UI column for t004.

## Files

- working notes; screenshots in `.playwright-mcp/` (gitignored)

## Acceptance criteria

- [ ] Every Render dashboard nav item / service tab has a recorded bex status; cross-referenced to w5 milestones where already planned.

## Out of scope

- Building any missing page (file notes in t004; UI work belongs to w5).
