Qelv

A prototype we built for a Toronto IT-services firm. August 2025 to February 2026.

A remote-desktop relay a Toronto IT firm saw run, then funded

A Toronto IT-services firm needed a remote-desktop component beyond the open-source relay it had, and something it could test within days. We built the portal, the Windows agent and the relay, deployed them in Docker on 28 August 2025, and the firm funded a continuation the following week.

IT services. Build.

Remote-desktop relay in figures

  • 3 daysfrom the firm sharing its code to the requirements session
  • 1 weekfrom the deployed prototype to a funded continuation
  • 3phases in the build plan the firm could sign against
The system, drawn from the story.

Screens from this system are being added.

The situation

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 we built

  • A React and Vite portal for listing machines and opening sessions
  • A .NET Windows agent driving remote-desktop sessions through PowerShell
  • An ASP.NET Core relay between portal and agent, with MongoDB and Redis behind it and the relay approaches researched side by side
  • Docker packaging, so the prototype deployed as one unit on 28 August 2025
  • A phased build plan with handover and ownership milestones, and the design phase completed in November 2025
  • 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

What changed

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

Along the way

  1. 25 August 2025

    Requirements session, three days after the firm shared its existing code and relay

  2. 28 August 2025

    Prototype deployed; the firm's written reaction to the interface came back the same day

  3. September 2025

    Continuation funded to complete the remote-desktop connection; phase one and two planning agreed

  4. October to November 2025

    Working build with the .NET agent and React portal, a three-phase plan, and the design phase complete on 24 November

  5. January to February 2026

    Deployment pipeline design for the firm's monitoring tool, with the database migration scoped

In their words

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

A Toronto IT-services firm, on the remote-desktop prototype, August 2025

Read next

  • Dubai World Trade Centre, a venues and events operator in Dubai

    An employee-management system for Dubai World Trade Centre, in two months

    A dedicated four-person team, two full-stack engineers and two mobile developers, built and deployed an internal employee-management system for Dubai World Trade Centre. 2 months from the team's first day to deployment.

Where to next

Have a problem in this shape?

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

We reply within two business days. If it is a fit, you get a one-page note on what to do first, before any sales call.