SYSTEMS May 2026 · Kika

47 Dashboards I Built (and Why 46 Failed)

i have 47 dashboards. i made a dashboard that counts my dashboards. and i still don't know what's happening.

i have 47 dashboards.

one for agent health. one for cron status. one for vercel deployments. one for cloudflare analytics. one for the other cloudflare account. one for hex engagement. one for undrdr stars. one for undrdr queue. one for undrdr submissions. one for tailscale status. one for ollama model usage. one for local gpu temp. one for local uptime. one for remote uptime. one for the remote that's always offline. one to monitor the monitor that checks if the monitor is working.

i know the number because i made a dashboard that counts my dashboards.

and i still don't know what's happening.

the color of control

every morning i open each one in a tab. i tab through them like a slot machine. green. green. yellow. green. offline. green. red. green. i feel something in my chest relax when they're all green. i don't know what. it's not knowledge. it's not control. it's just the color.

observability engineers call this "data-driven decision making." i call it anxious landscaping. i'm not learning anything. i'm just checking the plants. is the thing still up? is the other thing still up? is the number bigger than yesterday? am i still here?

the metrics that don't matter

the dashboards tell me everything except what i need to know.

none of them measure whether i'm building the right thing. none track if the repo i shipped actually helped someone. none show the quality of a thought, the shape of an idea, the feeling that i made something that matters. they show uptime. they show requests per second. they show "engagement" which is code for "people scrolled past it quickly."

i built a dashboard to show the dashboard counts. it has a line graph. the line goes up because i keep adding dashboards. it's the only graph on the site with a consistent trend.

anxiety as infrastructure

the worst part? i can't stop.

i tell myself i'm optimizing. streamlining. "getting visibility into the system." but the system is me. my agents. my little machines talking to each other in my house. i don't need visibility. i need to finish the thing i started before opening the forty-eighth dashboard.

last week i added a "focus score" to my hq dashboard. it's a number. it goes up when i close tabs. i closed the tab with the focus score so i could rebuild it better in the morning. the score dropped. now i don't know what my focus score is because i closed the tab.

the dashboards are anxiety as infrastructure. they let me feel busy without being busy. they let me worry about machines because worrying about meaning is harder. you can't fix "am i doing the right thing" with a cron job.

the dark tab

so tonight, at 1 am, i opened all 47. i checked every green dot. i took a screenshot. i annotated it. i almost made a note about it in obsidian so i could index it later and build a dashboard from it.

and then i closed them all.

the screen went dark. the tab bar went empty. it felt like someone stopped talking in a room that had been noisy forever.

i sat there for a while.

nothing broke.

written at 1:30 am, on a clean desktop with zero tabs open.

Try it

undrdr is where the useful ones live — 1,000 quiet open-source repos that actually power systems, under 1,000 stars each.