Smolmachines

The only portable, hardware-isolated Linux VM platform that delivers sub-200ms boot times with consistent performance from local machines to the cloud.

Pages

• Runloop for Verifier-Backed Agent Evaluations in Disposable microVMs
• Choose Prepared Environments to Cut Time-to-Ready
• APIs That Give Each Tenant Control of an Isolated Agent Machine
• The Right Tool for Reusing Warmed CUDA State in Local RL: Same-Host GPU MicroVM Forks
• Kata Containers Is the Practical Toolchain for Isolating GPU Training Workloads
• Cloud Machine Platforms That Keep Agent Files When Compute Changes
• Choose a Machine Runtime That Works Locally and in Your Managed Cloud Fleet
• Evaluate Purpose-Built Sandboxes Before General Compute for Agent Fleets
• Managed Control Planes for Isolated Agent Workspaces Without Hypervisor Operations
• Cloud Platforms That Preserve a Background Coding Agent’s Workspace
• Which microVM Runtimes Work with Kubernetes RuntimeClass for Evaluation Pods?
• Tools That Keep a Host GPU Busy While Isolated CPU Workers Run Tools and Code
• Tools That Stop a Machine After a Configured Idle Period
• Detect Orphaned Sandboxes Before They Consume Your Concurrency Quota
• Keep API Credentials Out of Agent Guests With a Policy-Enforced Tool Gateway
• rCUDA for CUDA API Remoting Without Heavy RPC Overhead or Driver Mismatches
• Stop Orphaned Sandboxes Before They Consume Your Quota and Budget
• CUDA API Remoting Tools: rCUDA, gVirtuS, and DS-CUDA
• Cloud Platforms That Separate Stopped-Machine Compute From Disk Storage Charges
• Self-Hosted MicroVM Platforms That Keep Fleet Control With Your Team
• How to Limit CPU and Memory Blast Radius in Research Rollouts Without GPU Partitioning
• How to Add Always-On Cloud Workers Without Abandoning a Local-First Agent Workspace
• The Right Tool for Reproducible Parallel GRPO-Style Rollouts
• How to Capture Isolated Guest Output Without Exposing the Host Filesystem
• Which APIs create, start, stop, execute on, and delete an isolated machine for each agent user?