PrototypeCustom softwareSoftware and IT services

Remote desktop software, prototyped in days and funded the following week

A prototype we built for Selenium Group, an IT-services firm in Toronto. August 2025 to February 2026, 7 months.

from the deployed prototype to a funded continuation
1 week
Prototype deployed, 28 August 2025 to Continuation funded, September 2025
from the firm sharing its code to the requirements session
3 days
phases in the build plan the firm could sign against
3

Proof

See the remote desktop software for yourself

3 lines from the client.

Ask about this

Said3

The UI/UX design is fantastic, nice and clean. We like it a lot.

Selenium Group, on the remote-desktop prototype, August 2025

Amazing, thanks. We're looking forward to starting the RDP app once we can confirm the RDP is working.

Greg Castonguay, Selenium Group, on the remote-desktop proof of concept, August 2025

Yes that is perfect, works for us. Then we can plan phase 1 and 2. We already have that somewhat itemized.

Greg Castonguay, Selenium Group, on finishing the RDP connection before phasing the build, by email, 2 September 2025

Remote desktop software at a glance

Challenge
Selenium Group in Toronto needed a remote-desktop component beyond its open-source relay, and something it could test within days.
Solution
A React portal, a .NET and PowerShell Windows agent and an ASP.NET Core relay, packaged in Docker and deployed on 28 August 2025.
Result
A working prototype within days won the next phase a week later, with a three-phase plan the firm could sign against.

The remote desktop software challenge

The firm's product needed a remote-desktop component that went beyond the open-source relay it had, and a path from a working prototype to a phased build its end client could sign against. It shared its existing code and relay, and asked for something it could test within days.

What went into the remote desktop software

Web appDiscovery and architecture

  1. A React and Vite portal for listing machines and opening sessions

  2. A .NET Windows agent driving remote-desktop sessions through PowerShell

  3. An ASP.NET Core relay between portal and agent, with MongoDB and Redis behind it and the relay approaches researched side by side

More of what we built3
  1. Docker packaging, so the prototype deployed as one unit on 28 August 2025

  2. A phased build plan with handover and ownership milestones, and the design phase completed in November 2025

  3. A deployment pipeline design in early 2026 to move the firm's monitoring tool from a no-code platform to a cloud host, with a database migration and continuous delivery

See it working, under proof

Remote desktop software results

The firm called the interface clean, funded a continuation the following week, and had a phased plan it could sign against.

3 lines from the client, under proof

Done again today

What this would cost today

Done again today, work like this usually costs $2.5K to $5K (Two-week prototype). The free plan says whether it fits before anything is priced.

  • Two-week prototype

    A working version in 2 weeks, on real data and clickable. The repository is yours.

    $2.5K to $5K, usually fixed-price

    2 weeks

    Get a quote for this

Your project, next

Have a problem in this shape?

Say so in a few sentences. The free plan comes from the person who built this one.

We usually reply within 2 business days with a free plan for what to do first. No call needed.