All work
Full-Stack

AlgoEdge Cloud: On-Demand Windows VM Hosting with a Client Portal

A zero-dependency Node portal that provisions Hyper-V Windows VMs for MT4/MT5 hosting and delivers credentials to a client dashboard.

VMFactory console with differencing disks off a golden image and unattend-injected identities; portal with signup, order, manual payment and admin build; a WireGuard dial-out relay designed around carrier-grade NAT; and honest pricing caveats raised to me.

AlgoEdge Cloud: On-Demand Windows VM Hosting with a Client Portal — illustration
What makes it serious
  • Zero-npm-dependency portal and console
  • Golden image + differencing disks + unattend injection
  • CGNAT diagnosed; outbound WireGuard relay designed
  • Pricing and SLA concerns raised, not buried

The idea was to resell spare capacity on a workstation as MT4/MT5 hosting for Indian algo traders. Two pieces were built. VMFactory is a local web console that provisions Windows VMs on Hyper-V on demand: a golden image, differencing disks per VM, identity and credentials injected as an unattend file before first boot, and a PowerShell module layer behind a Node server with no npm dependencies. The portal (also dependency-free, on Node's built-in SQLite and crypto) handles signup, orders, manual payment confirmation, an admin "mark paid and build" action, and shows credentials in the client's dashboard.

The infrastructure finding shaped everything: the connection sits behind carrier-grade NAT, so inbound traffic can never reach the host and router port-forwarding is useless. The chosen design is a small VPS relay with a static IP, WireGuard dialled outbound with keepalives, and one forwarded port per VM, so clients always receive a hostname and the ISP rotating addresses no longer matters.

Three Windows provisioning traps were documented for reuse, and the honest conclusion was recorded too: list-plus-margin pricing came out several times above the market, and a residential line cannot honour data-centre uptime promises, so the product stays a working prototype rather than a launched service.

How it works

  1. Client signs up and places an order
  2. I confirm the manual payment and click build
  3. VMFactory clones the golden disk and injects identity
  4. Relay maps a port to the VM over the outbound tunnel
  5. Credentials and hostname appear in the client dashboard
Stack
Node.jsPowerShellHyper-VSQLiteWireGuard
#hyper-v#vm-hosting#nodejs#powershell#wireguard#mt5