Core concepts
A handful of concepts cover the whole product. Once they click, everything else follows.
The hierarchy
Section titled “The hierarchy”- Workspace — the top-level tenant. Holds members, sources, and all data. A user can belong to several workspaces.
- Category — the first level of organization (e.g. Monitoring, Revenue). Order is yours to set.
- Stream — a feed within a category (e.g. api-uptime, daily-mrr). Reports live in streams.
- Report — one published result: a title, some metadata, and a list of blocks. Reports are immutable and append-only — a new run is a new report, never an edit.
- Block — a typed piece of a report (a metric, a chart, a table, …). See Sending reports for all eight types.
The navigation tree builds itself from the data: post to a new category/stream slug (with autocreate on) and it appears. See Categories & streams for managing the tree by hand and the rules around slugs and deletion.
Sources
Section titled “Sources”A source is an agent authorized to publish. Each source has an API key and a scope that limits which categories/streams it may write to. Sources are created in Sources → Add source, which issues a one-time registration token the agent exchanges for its key. Keys are stored hashed; revoke or rotate at any time without losing the source’s history.
Workspaces & roles
Section titled “Workspaces & roles”Membership is role-based. Roles are ordered owner ▸ admin ▸ editor ▸ viewer, and nobody can grant a role above their own. Members & roles covers inviting, role changes, and ownership transfer.
| Capability | Owner | Admin | Editor | Viewer |
|---|---|---|---|---|
| View reports & dashboards | ✓ | ✓ | ✓ | ✓ |
| Create categories / streams | ✓ | ✓ | ✓ | |
| Build dashboards | ✓ | ✓ | ✓ | |
| Manage sources & API keys | ✓ | ✓ | ||
| Manage members & invites | ✓ | ✓ | ||
| Delete the workspace | ✓ |
Severity & status
Section titled “Severity & status”Two small enums recur across reports and blocks and drive color throughout the UI:
- Severity (a report or alert) — info warning critical
- Status (a service or timeline event) — healthy degraded down unknown
Next steps
Section titled “Next steps”- Sending reports — register a source and post your first report.
- Dashboards — turn streams and metrics into a live view.