What I do
I have spent more than eight years writing commercial software: CRM platforms, applicant tracking systems, and business automation tools. That is the day job, and it is the reason the tools here exist at all. Every test on this site is code I wrote and maintain myself, not a widget bought off a shelf.
Why hardware
Building PCs has been my hobby for years. I have put together more than five machines for myself and for friends, which means picking parts, reading spec sheets, and comparing components that look identical on paper and behave nothing alike in practice.
That work goes past assembly. I overclock CPUs, memory, and graphics cards, then hunt for the settings that stay stable under real load, both at the desktop and in a long gaming session. I stress test hardware to find where it actually breaks instead of trusting the number printed on the box, and I have written scripts to tune CPU behavior on Windows.
None of that is decoration on a bio. Finding a stable overclock is the same job as testing a mouse: apply a load, read a number, and work out whether the number means the part is fine or the part is failing. RigPolice is that habit turned into browser tools.
Why this site exists
The tools I needed while building and debugging machines were scattered across slow pages buried in ads, and half of them wanted an install. So I wrote my own: focused, fast, and free of anything you have to download. If you want the specifics of how each measurement is taken, along with what a browser genuinely cannot measure, read how we test.
Where to find the code
My work is public on GitHub, including the open source RigPolice Embed plugin that lets any WordPress site drop these tools into a post.
Get in touch
Found a bug, want a tool added, or think a measurement is wrong? Email me at contact@rigpolice.com.