CaseDash is a compact dashboard for dedicated PC telemetry screens. Its natural home is a small USB/HDMI or case-mounted panel, and its edge auto-hide mode keeps it practical on a single monitor too. It turns system telemetry into an always-on native sensor panel.

It is not a generic hardware-monitoring suite. CaseDash is a polished sensor panel you place, configure, and mostly leave alone. There are no keyboard shortcuts or extra controls beyond what is needed to make the panel look right and stay put.

It's me, Roman Elizarov — ex-project Lead for Kotlin, software development expert, sports programming, ICPC. Why a native C++ app? Because I needed a small, fast, clean software that works for me. But is also an experiment in what is possible to build. I'd be glad if it is useful for you, too.

• Constraint-based layouts and a live editor.
• Theme system that derives a full palette from a small set of key colors.
• Animated metric fills and throughput plots interpolate smoothly between telemetry snapshots.
• Small native executable: an .exe under 1 MB, with vsync-paced animation that spends less than 1 ms per frame.
• A hover titlebar keeps first-time configuration controls reachable without cluttering the panel.
• Ready-made layouts fit common compact landscape, portrait, and wide panel shapes.
• Built-in display setup handles the fiddly work of fitting the panel and remembering where it belongs.
• Machine-wide auto-start setup works for all users out of the box.

CaseDash supports provider-backed GPU telemetry, board temperature and fan telemetry, and presented-FPS capture for the active presenting application. See docs/hardware.md for the current supported-provider sections, runtime requirements, and troubleshooting notes.

1. Download and run CaseDash.exe.
2. Use the hover titlebar or right-click menu to open setup controls.
3. Pick a layout and theme, then select storage and network devices if needed.
4. Use Configure Display to choose the small screen, or an edge placement on the main monitor.
5. Enable Start with Windows when the panel is ready for daily use.

Configuration is saved beside the executable as config.ini.

Contributions are welcome in code, issues, sketches, and plain ideas.

Good areas to explore:

• New themes and visual ideas. Do you have cool animations or styling in mind?
• New layouts for different screen sizes and mounting styles.
• Localization: does it need translation? Which languages, and which parts of the UI?

Open an issue and write what you want to achieve.

• GPU telemetry and board sensor modules. Do you have unsupported hardware? Open Codex or Claude, give it full access, tell it which provider software exposes fan and temperature information on your machine, let it explore and write the corresponding telemetry provider similar to the existing ones. Keep the vendor-selection mapping and known-machine test fixture updated, grill the agent to keep integration light and elevation-free, then send a detailed PR.

• Linux users: are you interested? What hardware do you have? A Linux port would be a cool project to undertake; write up your use cases.

There is code here that I am not proud of, but it works. I do not clean code just for the sake of it; I clean it gradually when adding features or fixing bugs.

Build and development setup lives in docs/build.md. Release steps live in docs/release.md. Product behavior is specified in docs/specifications.md, and the layout/config language in docs/layout.md.

This project is licensed under the Apache License 2.0. See LICENSE.