Service app that reads a configuration file and spawns server instances at system startup.
Mechanism inside each server instance that monitors its own memory usage and auto-terminates instance when above a threshold, knowing that InstanceSpawn will launch a new instance.
As it stands, no, it’s a GUI app.
The idea is to use the InstanceSpawn library (that the GUI app demonstrates how to use) to make a service app, then register it as a single windows service, and have it spawn 10 server instances (you’d otherwise need to register one by one as a service).
Then have your reverse proxy (nginx, caddy) load-balance across these 10 instances.