Share servers. Keep users separate.
Put the team’s compute to work without mixing private environments. Each developer gets their own containers, credentials and storage; you choose shared resources and per-user budgets.
How it works
Server Users
Review user placement, private workspace paths, retained roots and aggregate server budgets.
User placement and resource budgets
See each user’s host, workspace path, retained data, CPU set and aggregate limits.
Inspect verified host limits
Open the Limits tab to inspect aggregate CPU, RAM, disk and host enforcement for the selected user.
New-workspace storage and CPU affinity
Inspect the default path and CPU pinning. Retained workspaces stay in place; CPU pins are not exclusive cores.
Try the interface
Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.
Watch the workflow
Loading the recorded terminal…
Put your server to work.
Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.