2026 — present
Remote command execution on Windows machines
Founder and sole author — CtisEvolution
Impact
Running a command on a remote machine went from needing open RDP access to being an action from the browser, without exposing the machine to the public network.
The problem
Administering remote Windows machines without relying on open RDP or VPN, from a centralized web interface.
The approach
An agent runs as a Windows service on each machine, with its own installer and tray icon, and connects as an outbound client to a central server over WebSocket. Commands are fired from a React interface — the remote machine never needs an open inbound port.
There are two client generations: one in Python and a rewrite in .NET as a real Windows service, with its own installation flow.
A CtisEvolution product, my company, built almost solo — external help was limited to specific details, not the overall design.
Result
Running a command on a remote machine went from needing open RDP access to being an action from the browser, without exposing the machine to the public network.