About desktest.net

Front-desk computers break in boring, repeating ways: a check scanner stops talking to the browser, a signature pad service is not running, a printer driver gets replaced by Windows Update. We built desktest.net because the fastest way to answer "is this thing actually working?" should be a single web page, not a 40-minute support call. Every page here exists to answer one question with a clear pass or fail.

What this is

desktest.net is a free collection of single-purpose diagnostic pages for front-desk peripheral and software problems. The focus is the software stack that runs property management, self-storage, dental, medical, legal, and hospitality front desks: check scanners, signature pads, receipt printers, PDF viewers, vertical-specific web apps.

Each tool answers exactly one question: does this work right now? The pages run entirely in the browser against your local drivers and services. There is no backend to send data to. You can hit "View source" in your browser and read every line that runs.

The three rules

Every page on this site follows the same three rules. They are written down so the project does not drift later.

One page, one question. A diagnostic that asks the user to think is a diagnostic that fails. Every tool is built to give a clear pass or fail in under a minute, with one obvious button to press. No menus, no settings panels, no choices to make before you can run the test.

Nothing leaves your computer. Every check runs locally in the browser tab against the drivers and services on your workstation. Signatures, scanned checks, printer output, customer data: none of it is uploaded anywhere, because there is nowhere for it to go. The pages do not even load Google Fonts or analytics scripts. Open the network tab and watch.

No accounts, no tracking, no monetization-via-data. There is no sign-up, no email gate, no cookie banner, because there are no cookies to consent to. The site does not exist to harvest leads or build a profile of who is having scanner trouble at 9 AM on a Tuesday. If a "sign up to continue" button ever appears on this site, something has gone wrong.

Who runs it

desktest.net is built and maintained by Kristian (Tech1k), and shared freely to help the people who keep front-desk systems running.

It is open source so anyone who does this work can read it, trust it, and extend it.

Why open source

The trust posture of this site is structural, not a marketing line. A diagnostic page that promises "your data stays on your machine" is only worth the source code behind it. So the source is on GitHub at tech1k/desktest. Anyone can read it, fork it, audit it, run it offline, or submit a patch.

This is also a deliberate competitive position. Commercial diagnostic tools in this space tend to be built on top of a backend with telemetry, account systems, and an analytics pipeline. Those companies cannot honestly say "no data leaves your computer" without rewriting their entire business model. We can, because the architecture was the point from day one.

License

The project is licensed under AGPL-3.0-or-later. The full license text lives in the LICENSE file in the repository. AGPL means you can use, modify, and redistribute the code freely, including for commercial purposes, as long as derivative works (including network-hosted ones) are also released under AGPL. For organizations that want to embed parts of these tools inside a proprietary product without the AGPL share-alike obligations, commercial dual-licensing is available. Contact the copyright holder through the GitHub repository to discuss terms.

Contributing and reporting bugs

Bug reports, peripheral models that need support, and pull requests are all encouraged. Open an issue at github.com/tech1k/desktest/issues. For non-trivial code contributions a short Contributor License Agreement is required so the commercial dual-licensing track stays clean. Typo fixes and small documentation changes do not need a CLA.

Tools

The full list of live tools is on the homepage. As of v1.0 there are fifteen:

Help

If you are reading this and want practical entry points: