See where server capacity goes
Inspect CPU, RAM and disk I/O over time for hosts and containers in the Dashboard. Server-side history keeps collecting when your client is closed. Compare measured use over an hour, day, week or month, and set aggregate per-user budgets across workspaces.
How it works
Resource history without an open client
Server-side samples preserve CPU, RAM and disk I/O when your client is closed. Compare workspace totals and keep shared-container consumption separate from individual sessions.
Inspect measured disk activity
Open a workspace timeline, then switch from CPU to disk reads. Unknown intervals stay blank; read/write totals come from actual counter deltas.
Compare host capacity over time
Switch to a week and inspect the host. Host CPU uses total host capacity; workspace CPU uses one core per 100 percent. Server users see only their own workspaces.
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…
Release videos
- devctrl 0.4.0: The agents' disk I/O on the Hosts screen chapter at 0:00 on YouTube
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.