Pulseframe showcase

Control-room UI with calm urgency

html demo split css system nominal

Pulseframe now leans hard into the Dokku status app lineage: darker zinc surfaces, smaller radii, tighter density, sharper operational typography, and less startup gloss.

surfaces
03
flat layered panels with hard edges
signals
05
semantic tones for runtime posture
density
tight
compact, scan-first information layout
tone
ops
brisk, clinical, not product-marketing soft

Font preview area

Type pairings that actually fit this harsher Dokku-status style. These are operator-facing, compact, and technical.

recommended pairings
IBM Plex Sans + IBM Plex Mono
best overall fit
top pick
Node health 99.982%
Excellent for dashboards, deployment surfaces, incident consoles, and data-heavy admin views. Feels precise without looking sterile.
deploy sha e7a58df · uptime 99.99% · p95 184ms · queue 12.4k
Manrope + JetBrains Mono
slightly friendlier, still sharp
secondary
Webhook fanout degraded
Works if you want the status-app structure but with a little more softness in headings and KPI cards.
worker[03] timeout=20s retry=5 latency=487ms load=72%
Space Grotesk + IBM Plex Mono
more stylized, still credible
accent option
Incident timeline / active
Use this when you want a little more character in section titles, but not enough to drift into startup-land.
api-gateway 148ms · router stable · retries 38 · region iad1

View variants

Same system, three presentation modes: compact cards, operator list, and denser table.

card / list / table
Card view
API Gateway
Healthy
148ms
99.99% uptime · runtime health / 5m rolling
Webhook Fanout
Action needed
1.4s
96.40% uptime · retries accumulating
List view
API Gateway
148ms
99.99%
Model Router
212ms
99.73%
Event Queue
487ms
98.92%
Webhook Fanout
1.4s
96.40%
Table view
Service Latency Uptime Status
API Gateway 148ms 99.99% Healthy
Model Router 212ms 99.73% Stable
Event Queue 487ms 98.92% Degraded
Webhook Fanout 1.4s 96.40% Action needed
Availability
99.982%
Nominal
+0.021% vs last 30d
P95 latency
184ms
Within budget
window: last 60 minutes
Queue depth
12.4k
Elevated
threshold breach for 11m
Failed jobs
38
Needs action
retries still in flight
Primary region
iad1
3 edge pools, 2 failover lanes
Deploy SHA
e7a58d
latest pulseframe style refactor
Traffic shift
22%
to backup workers
Operator
1
active incident commander

Service posture

Dense service rows built for scan speed, not decoration.

1 degraded / 1 failed
API Gateway
runtime health / 5m rolling
148ms
99.99%
Healthy
Model Router
runtime health / 5m rolling
212ms
99.73%
Stable
Event Queue
runtime health / 5m rolling
487ms
98.92%
Degraded
Webhook Fanout
runtime health / 5m rolling
1.4s
96.40%
Action needed

Command surface

For runbooks, approvals, and operator prompts.

$ deploy rollback --app webhook-fanout --to e7a58df

Current alerts

Semantic alert treatments with low-noise emphasis.

danger
Webhook retries crossing alert threshold
Downstream provider latency increased after the last release window. Retry traffic is accumulating in the fanout worker.
ETA 18m
warn
Worker queue saturation detected
Backpressure is manageable, but async fanout should be rebalanced before the next traffic spike.
Watch closely
info
Planned schema deploy staged
The next migration batch is already validated against staging snapshots and ready for operator approval.
Pending release

Runtime facts

Key-value readouts for IDs, versions, and environment state.

Environment
production
Incident ID
INC-2026-04-04-017
Queue topic
fanout.webhooks
Current model
gpt-5.4

Incident timeline

Linear operator storytelling with a crisp visual rail.

07:41 UTC
Synthetic checks began timing out in us-east edge pool.
07:43 UTC
Queue depth alert triggered at 1.8x baseline.
07:46 UTC
Failover policy shifted 22% of traffic to backup workers.
07:49 UTC
Operator acknowledged incident and opened mitigation runbook.

Operator log

Monospaced event feeds for runtime debugging and approvals.

07:44:02 probe edge/iad1 latency budget exceeded
07:45:11 queue fanout backlog crossed warning threshold
07:46:29 router worker-shift rebalanced 22% load to secondary pool
07:48:50 hooks webhook-fanout retry storm still active after mitigation