01
Start with nothing.
Every orb begins as an empty ring. A hairline outline that lives in the same space your work does, waiting for a signal.
CLOSED BETA · COMING SOON
Hairline performance overlays.
See right through them.
Seven floating wireframe orbs for Windows. Thin themed outlines. Nothing in your way.
Illustrative. A real product screenshot lands here as soon as the closed beta opens.
THE CPU ORB
Six parts. One orb. Any processor.
Scroll right → to watch every piece appear, then watch the same orb scale from a laptop CPU to the biggest workstation chip currently shipping.
02
Add your machine’s load.
The workload arc fills clockwise with overall processor utilization. The headline in the middle is the same number, in big.
03
Know what’s underneath.
The caption identifies your CPU and the current clock. It’s your live boost clock, refreshed every second — not the number on the box.
04
Every core, every thread.
One tick around the perimeter for every logical processor, each scaling with its own load. On a quad-core i3-13100 — 4 cores, 8 threads — the ring is sparse and easy to read: now you can clearly see one tick per thread, each moving on its own.
05
It knows your fast cores from your efficient ones.
On a hybrid chip the orb tells performance cores from efficiency cores and draws them differently — tall ticks for the P-cores, short ticks for the E-cores — so you see exactly where the work is landing. Package temperature and live wattage sit in the chip beneath the headline.
06
From a 4-core laptop chip to 192 threads. Same orb.
We started on a quad-core i3 with eight legible ticks. Here is a 96-core Threadripper PRO 9995WX — 192 threads with SMT, a packed perimeter of ticks, each still moving on its own. Same orb the whole way up; nothing about the logic changes.
THE GPU ORB
Four engines. One ring. Any card.
Scroll right → to watch every piece appear, and watch the same orb climb from integrated graphics all the way to a 32 GB RTX 5090.
01
Start with nothing.
Every orb begins as an empty ring. A hairline outline that lives in the same space your work does, waiting for a signal.
02
Add the busiest engine.
Start small: integrated graphics ticking over with light work. The workload arc fills with the max utilization across every GPU engine, and the big number in the middle is that percentage.
03
Know what you have.
Start at the integrated floor and the caption still names it — your exact GPU and its live clock, in real time, refreshed every second. Even shared-memory graphics get identified, not lumped in as “unknown.”
04
Every engine, every workload.
Step up to a discrete card and four sectors light up around the ring: 3D, Copy, VideoEncode, VideoDecode. Each fills with that engine’s utilization, so you see at a glance which subsystem your workload is hitting.
05
Heat, power, and VRAM.
Move up to a bigger card and the inner ring shows VRAM occupied. The chip beneath the headline reports junction temperature and current VRAM percent. All live — the kind of detail most overlays skip.
06
From integrated graphics to a 32 GB RTX 5090. Same orb.
We started on Intel UHD Graphics 770 ticking over quietly. Here is an RTX 5090 under full load — four bright sectors, 32 GB of GDDR7 nearly full, junction at the thermal limit. Same orb the whole way up; nothing about the logic changes.
THE RAM ORB
One ring. Two canisters. Any kit.
Scroll right → to watch every piece appear. From an 8 GB DDR3 kit to bleeding-edge 64 GB DDR5.
01
Start with nothing.
Every orb begins as an empty ring. A hairline outline that lives in the same space your work does, waiting for a signal.
02
Add what you’re using.
The workload arc fills with committed memory as a percentage of installed. The big number is the same value — at a glance, how full your RAM is right now.
03
Know what’s installed.
The caption identifies your memory configuration and effective transfer rate, and a tick appears for every populated module — two sticks here, one tick each. Start at the bottom: an 8 GB DDR3 kit, identified automatically.
04
Used and available, side by side.
Step up a generation to a 16 GB DDR4 kit. Twin canisters along the orb show Used GB on one side and Available GB on the other. They breathe with the workload — Used fills as you load tabs and apps, Available drains.
05
Timings and compression.
Move up to a 32 GB DDR5 kit. The chip beneath the headline shows your primary timings and current compression ratio — detail most monitors never surface.
06
From DDR3 to bleeding-edge DDR5. Same orb.
The renderer is hardware-agnostic. An 8 GB DDR3 kit fills its canisters fast under a single Chrome window. A 64 GB DDR5-8000 kit spreads across four sticks — four ticks now — with room for a couple Adobe sessions and a virtual machine without breaking a sweat. Same orb the whole way up.
THE DISK ORB
One arc per drive. Any array.
Scroll right → to watch every piece appear. The ring divides into one segment per physical drive — twelve drives, twelve arcs, each filling on its own.
01
Start with nothing.
Every orb begins as an empty ring. A hairline outline that lives in the same space your work does, waiting for a signal.
02
One drive, one arc.
Start at the bottom: a single M.2 NVMe. With one physical drive, the ring is that drive’s active time and the headline is the same value. One arc = one drive — that rule never breaks.
03
Every drive gets its own arc.
Add a few drives — an NVMe boot disk plus a small SSD-RAID — and the ring divides into one segment per physical drive. Each fills independently with that drive’s active time, NOT a single accumulated workload. The headline tracks the busiest segment so you spot the noisy disk at a glance.
04
Independent, not accumulated.
Each segment is its own gauge. If C is hammered and D is idle, you see one bright arc and three faint ones — not one big half-full ring. The drive letter label outside each segment tells you which disk is which.
05
Per-drive R/W and queue.
Add spinning disks to the mix — an HDD-RAID alongside the NVMe and SSDs. The chip stack beneath the headline shows each drive’s current reads / writes and queue depth in compressed form. C is the system drive; the rest get one line each.
06
From one M.2 to a 12-drive array. Same orb.
The renderer is hardware-agnostic. A single-M.2 ultrabook shows one arc filling the entire ring. A twelve-drive workstation — NVMe, an SSD-RAID, and an HDD-RAID — shows twelve separately-filling arcs. Nothing about the orb logic changes.
THE NET ORB
Sent and received. Live.
Scroll right → to watch every piece appear. Same orb on 56k dial-up, Wi-Fi 6, or 10 Gbps fiber.
01
Start with nothing.
Every orb begins as an empty ring. A hairline outline that lives in the same space your work does, waiting for a signal.
02
Add the busier direction.
The workload arc fills with whichever direction is currently saturating more of your link. The big number is that percentage.
03
Know what you’re on.
The caption identifies your active connection and its negotiated link speed — detected automatically, whatever you’re connected through. Start at the bottom: a 56k dial-up line, nearly maxed by a single page load.
04
Send and receive.
Step up to DSL. Twin canisters flank the headline — Sent on the left, Received on the right. Each fills with that direction’s current rate relative to the cap. You read upload-versus-download at a glance.
05
Rates and latency.
Move up to Wi-Fi 6. The chip beneath the headline reports current send and receive rates plus the gateway ping in milliseconds. Live, every second.
06
From 56k dial-up to 10-gig fiber. Same orb.
The renderer is hardware-agnostic. A 56k dial-up line crawls, both canisters barely lifting. A workstation on 10 Gbps fiber under full load shows both canisters near the top. Same orb the whole way up; nothing about the logic changes.
THE FPS ORB
Every frame. Supported games.
Scroll right → to watch every piece appear. The FPS orb works in most modern games, and we’re expanding compatibility every release.
01
Start with nothing.
Every orb begins as an empty ring. A hairline outline that lives in the same space your work does, waiting for a signal.
02
Add the current frame rate.
The workload arc fills with FPS as a fraction of your display’s refresh rate. The big number is the FPS itself.
03
Know what you’re playing.
The caption identifies the focused game and your display’s refresh rate. Detected automatically the moment you tab into a game.
04
Every frame, the last 60 seconds.
Ticks around the perimeter show frame time for each recent frame. Taller ticks mean longer frames. Spot a stutter at a glance.
05
1% lows and GPU bound.
Chip beneath the headline shows your 1% lows over the last sixty seconds plus current GPU utilization. If GPU is hitting 99% you’re GPU bound; otherwise you’re CPU bound somewhere upstream.
06
From 30 Hz cinema to 360 Hz competitive.
The renderer is hardware-agnostic. A 30 Hz console title at 28 FPS reads as a nearly full ring (28/30). A 360 Hz CS2 session at 312 FPS reads bright and busy (312/360). Nothing about the orb logic changes — we’re widening game support every release.
THE BATT ORB
Charge, state, watts. Read it from across the room.
Scroll right → to watch every piece appear. The captionTop word IS the charging indicator — no bolt graphic to squint at.
01
Start with nothing.
Every orb begins as an empty ring. A hairline outline that lives in the same space your work does, waiting for a signal.
02
Add the charge.
The workload arc fills with the current charge percentage. The big number in the middle is the same value. Read it from across the room.
03
Plugged in or not.
The top caption tells you whether AC is connected — "AC Power" when plugged in and topped up, "Charging" when actively charging, "On Battery" when running off the cell, "Discharging" when actively pulling down. No bolt graphic to interpret; the word is the signal.
04
Time left, or time to full.
The bottom caption reports estimated time remaining on battery, or time to full charge when charging. Straight from your battery, updated live.
05
Watts in or out.
Chip beneath the headline shows signed instantaneous wattage. Positive means current flowing IN (charging), negative means current flowing OUT (discharging). Zero is the top-off state Windows enters at 100%, which is normal.
06
Plug in. Same orb.
Connect AC and the top caption flips to "Charging", the bottom to time-to-full, the chip to a positive wattage. Same orb, different state — at a glance you know which cable is actually delivering current.
Designed to disappear.
Most overlays add ink to your desktop. Crystal Clear subtracts it. Hairline outlines, outline-only numerals, transparent everywhere else. You read your work through the orb, not around it.
Click-through is on by default — the orb ignores your mouse and lets you click the window underneath. Drag mode is a single toggle in the tray. Each orb carries its own theme colour so the seven metrics read at a glance, without legends.
What's inside an orb.
Per-metric theming
Seven colours, one for each orb. The palette is the navigation — you learn it once and never read a legend again.
Click-through by default
Orbs ignore the mouse. Hit a tray toggle to enter drag mode when you want to move them. Hit it again to lock them down.
Workload arc and sparkline
A hairline arc fills with the live metric. A thin sparkline under the headline shows the last sixty seconds.
Per-core CPU ticks
Optional ring of small ticks around the CPU orb — one per logical core. Tiny, deliberate, off by default for the rest.
Closed beta is opening.
Signup opens shortly — we're finishing the email plumbing this week. Come back soon.
No newsletter. No marketing. One email when you're in.