---
id: w8/m5/t006
title: "Render parity: Postgres/Key Value compute in usage view"
worker: worker8
status: todo
estimate: 30m
depends_on: [w8/m5/t005]
---

## Objective

Compare this milestone's behavior against Render's billing usage view for Postgres/Key Value compute and flag any drift as documented follow-up rather than silent divergence, per the standing Render-parity closing task.

## Context

- `w8/m2`'s docs already record that Render's billing surface is dashboard-only (no REST/GraphQL/MCP usage endpoints) — this task is about the usage-view *content* (does Render show Postgres/Key Value compute alongside services, in what units/grouping), not the API-surface question.
- `docs/ADR018-render-parity.md` § Usage metering is the place to record the outcome.

## Steps

1. Verify (live capture or documented research) how Render's billing/usage view presents managed Postgres/Key Value compute.
2. Compare field/semantics/grouping against this milestone's implementation.
3. Update `docs/ADR018-render-parity.md`'s usage-metering entry with the comparison; file any drift as a follow-up note, not silently.

## Files

- `docs/ADR018-render-parity.md`

## Acceptance criteria

- [ ] `docs/ADR018-render-parity.md` reflects the comparison with an explicit verdict (parity or documented drift).

## Out of scope

- Building any drift-closing feature itself (goes to a follow-up note/task).
