For anyone who debugs hardware
Any sufficiently good tool looks like magic from the outside.
Scryglass puts every log line, bus transaction, GPIO edge and microamp from your device under test on one timeline — instead of five windows and a wall clock.
MCPBuilt-in MCP server. Point any MCP client at it — running a cloud or local model — and it can drive the bench, read the traces and write up what it found.
- FTDI multi-protocol adapters
- USB-serial adapters
- Nordic PPK2 power profiler
- I²C · SPI bus tools
- probe-rs debug probes
- Any target with a UART or SWD/JTAG port
Send anyone a session. They can open it.
A colleague, a contract manufacturer, the vendor whose chip you think is at fault — they download Scryglass, open your file, and see the same timeline you saw. No licence, no payment, no expiry.
Compare tiers →Flash it, halt it, step it
Plug in a probe and debug from VS Code with nothing else installed — firmware logs landing on the same timeline as the power trace.
Debug probes →Get the build
macOS, Windows, Linux — signed and notarized. Current build v0.8.1-beta.1 · prerelease.
Downloads →When it breaks
Docs, release notes, and answers from the people who build it.
Support →Who's behind it
A small team that spent years building this quietly before saying anything.
About →The beta is open, in phases.
A phase is running now. Answer five questions and we'll invite you when yours opens.