ASL GPU reservations that mean something
Each computer admits its own GPU workload against current safe capacity. Leases carry an owner, session and purpose, renew through heartbeats, and release when the work stops.
GPU coordination · Parallel work · Your infrastructure
Know what is running.
Know what it is for.
When several projects share powerful computers, resource counts are only half the story. rbroker connects memory reservations to the people, projects and work behind them—and brings your machines into one private view.
Developer preview · Standalone server 0.2 · Windows GPU broker and cross-platform coordinator
One view. Clear boundaries.
Coordinate the work without taking control away.
Parallel jobs, not anonymous counts
Projects declare what a job is for. See its registered handler, queued or running state, allocated workers and completed/failed items. Progress advances when chunks report results.
Several machines, one private view
Signed reports meet at your server. Each authorized group sees its own computers. Stale reports remain clearly last-known; a full GPU is not mislabeled offline.
Standalone Node.js server
Your server.
Your address.
Host the coordinator on Linux or Windows. It needs no GPU and no Electron shell. Configure your own HTTPS hostname, enrolled computers and storage paths. The ASL deployment uses rbroker.autosecurelogin.com; the product does not lock you to that address.
Source preview · Requires Node.js 24+ installed separately. Includes setup tool, Linux service template and Windows launcher. Not a one-click installer or certified Microsoft Store package.
Where Steward fits
rbroker remains an independent server and protocol. Steward is the planned native Windows management interface—not a dependency for Linux users or other applications.
What is not included
No remote command execution, model downloads or combined GPU memory pool. Linux server hosting does not imply Linux GPU collection. Automatic cross-machine job placement and the Steward fleet screen are not released.
Private by design, specific about limits
Share the work description.
Keep the work itself local.
Explicit reporting
The view contains declared project/session information, purposes, resources and progress. It excludes job inputs/results, prompts, command lines, environment variables and unrelated process inventory. Work descriptions must not contain secrets or customer records.
Reporting is not permission
A project activity report does not reserve threads or authorize GPU access. Each GPU operation still needs a valid local lease. Coordinator or network outages do not replace the local lease lifecycle.