Practical tools for refurb, repair, and IT workflows.
Source Potato builds software for the work that happens after the device lands on the bench: intake, diagnostics, drivers, updates, restore files, labels, records, and the repeated jobs that quietly eat technician time.
Bench software with a job to do.
Available
PCCheck V5.1
Refurb intake, practical diagnostics, label output, records, and technician-facing device processing.
Available
Paste As File
Turn supported clipboard text, images, formatted content, tables, WAVE audio, and links into real files from Explorer.
Free download →
Available
SP Clipboard Mechanic
Automatically clears the current Windows clipboard and unpinned clipboard history after a timer you control.
Free download →SP Windows Update Blocker
Service-backed Windows 11 update blocking with tray status, automatic cleanup, perimeter checks, and permanent incident records.
View project →
In development
Project Verta
Driver resolution from a maintained archive so research done once can help future machines.
In development
Project Horizon
Windows update reuse for refurb benches, repair jobs, and repeated IT refresh work.
In development
iPotato Restore Tool
Four-lane fruit-phone restore station with shared restore files, local caching, and per-lane progress.
In development
SP Network Killswitch
Service-backed VPN safety workflow for holding traffic until the intended VPN path is available.
In development
SP VPN Persistence
Windows VPN profile monitoring and reconnect visibility for machines where VPN state should be obvious.
Source Potato is shaped around real operations.
Source Potato is not a software plant guessing at shop problems from the outside. We are active in electronics repair, refurbishment, reuse, recycling, and device processing work, and these applications are shaped by the jobs we deal with every day.
The tools come from real benches, real technicians, real device piles, and real repeated delays. Source Potato products are designed around practical shop needs: reusable files, clear technician screens, consistent records, and workflows that can survive a busy operation.
Useful beats flashy.
Reusable knowledge
Drivers, updates, restore files, and findings should become shop assets instead of one-time technician effort.
Clear bench status
Long jobs need visible progress, plain-language states, and logs that help when something needs review.
Operator-first design
The interface should support the person doing the work, not bury them in debug output or guesswork.