Keep the work.
Release the compute.

Give agent tasks a dedicated Linux workspace. Keep files, tools, and running state through review cycles, then release CPU and memory while the work waits. Your application decides when to continue.

Evaluate your workloadSee the session lifecycle
Workspace runningTools + processesFiles + stateProgress savedCPU + memory releasedWorkspace restoredTools + processesFiles + state

A separate workspace for tools, files, and the work in progress.

Product illustration

One workspace.
Several rounds of work.

Example workspace
Source filesInputs for the job
Tools and working stateThe work behind the answer
Draft and review notesReady for another pass
Kept together in the session.

An agent may inspect a file, run an analysis, wait for feedback, then revise its result. Keep that work in one session instead of rebuilding the environment at each step.

  1. Bring the task.

    Provide the source files and a guest image with the tools your workload needs. Each session runs in its own Linux microVM.

  2. Work through the steps.

    Run commands, inspect output, and keep intermediate files together. Your application supplies the model, instructions, and decisions.

  3. Return the result.

    Download the finished files to your application. End the session when its workspace is no longer useful.

How tools connect to a session

Use VMYard's client interfaces with your guest tools. Foreground commands stream bounded output; background tasks provide logs and cancellation.

A review can take hours.
The compute can wait.

Keeping an idle environment running ties up resources. Throwing it away loses the working state. Snapshot sleep saves the guest's memory and disk, stops its VM, and releases CPU and memory for other sessions.

When feedback arrives, restore the saved environment and continue with its files and guest state. Saved sessions use storage and need compatible hosts with available capacity to resume.

Keep the context around the result.

Keep the scripts, intermediate outputs, and running state behind a draft ready for its next revision.

What saving a session preserves

Snapshot sleep preserves guest memory, device state, and disk. Ordinary pause retains memory and its capacity reservation. A snapshot does not preserve the state of external services or guarantee that an open network connection will resume.

Make room for
the next job.

Use one host or place sessions across several. Host-level ownership, resource limits, and headroom for returning work help keep shared capacity usable.

Move eligible sleeping sessions to compatible hosts for maintenance or available capacity. Cross-host moves require guest networking to be disabled.

See how VMYard fits your infrastructure

Use your next
review cycle.

Choose work that pauses for feedback or approval. Follow it through a saved session to the finished result.

Build your evaluation briefFind a workload like yours
Set the boundaries

Define who can use a session and how much it can consume.

Keep a recovery copy

Preserve a saved session beyond its original host.