Uncategorised decision
MouseFree.click
A single competent developer can build and maintain a privacy-first Windows keyboard-to-mouse utility using existing input-simulation libraries; the product contains no evident durable moats and core functionality is implemented by prior-art libraries.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off54 h to build
$0/mo1 h/mo upkeep
No published price to break even against.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All MouseFree.click alternatives, with the arithmetic →
What a replacement has to do
- Map three keyboard keystrokes to a screen coordinate and emit the chosen mouse action (click/hover/drag) at that coordinate.
What it still won’t have
- Signed, widely-distributed installer and reputation/brand trust
- Polished UX refinements and accessibility testing across many edge cases
- Official support or warranty
- Cross-device distribution channels (store listing, auto-update infrastructure)
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
MouseFree.click does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a Windows desktop app in Rust (egui for UI) that provides keyboard-driven precise mouse control. In-scope: global keyboard hooks, an overlay grid renderer that shows and lets the user select region/row/point, mapping keys to actions (left click, right click, double click, hover, click-and-drag), simulate mouse events via enigo, local settings saved as human-readable JSON, an installer (WiX or cargo-bundle) and basic auto-update stub. Out of scope: cloud telemetry, account system, analytics, cross-platform macOS/Linux support. Include error handling for missing permissions, unit tests for coordinate translation, integration test automation using enigo/pyautogui where possible, and a short README with build and install steps.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 3 cited sources+3
- Evidence score60
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productmousefree.click — Your screen. Your coordinates. Your move.
- open sourceAntiMicroX/antimicrox
- open sourceSnoothy/UCR
Integrity checks
What held up, and what did not.
