Factory Environments

https://factory.com/product/cloud-agents

Factory Environments are saved development baselines containing repositories, setup commands, cloned code, and installed tools. Software teams use them to launch separate cloud instances for Droids performing tasks such as bug fixes, code review, or browser testing; changes in an instance do not alter the saved baseline.

Pricing model Factory subscription plans with rolling usage limits; Environment compute-billing terms are not stated.
Pricing The headline compute price as the provider states it. Sorting ranks prices stated per vCPU over time, converted to hourly. Other pricing models sort after, unranked. No per-compute rate for Environment instances is stated in the official pricing material.
Free while idle Whether a stopped, paused, or sleeping sandbox costs nothing. –
Elastic Resources flex with what the sandbox actually uses, and the bill follows: yes when the provider bills on active or observed use, no when capacity is reserved or allocated and billed while it runs. –
Memory snapshots Whether RAM state survives a pause and resume, not just disk. –
Wake on request Whether a stopped sandbox wakes automatically on inbound traffic. –
Start / resume Typical time from create or resume to running. Sorting ranks stated times, converted to seconds; claims with no figure sort after, unranked. –
Max runtime The longest a sandbox may run. –
Isolation The isolation technology between sandboxes. –
GPUs Whether GPU instances are available for sandboxes. –
Docker Whether Docker containers can run inside the sandbox. –
SDKs Python, TypeScript

✓ yes · ✕ no · – no cited public fact.

Each Environment-backed launch starts a separate instance from the saved baseline; its changes are not written back, and its lifetime depends on the workflow that created it.

Sources

Last verified 2026-10-13. Corrections land through the update log.