Cloud Run adds singleton instances for long-lived, individually addressable workloads

Google made Cloud Run instances available in Preview on August 25 and published a detailed launch explanation on August 27. An instance is a top-level singleton Cloud Run resource: it runs exactly one container with no autoscaling, has an individually addressable HTTPS URL, and is managed through explicit create, stop, start, update and delete lifecycle operations. Google says instances can run continuously for up to seven days before an automatic restart and can then continue indefinitely through restart policy. Its launch example puts a continuously running 1 vCPU, 1 GiB instance at $5.70 for 30 days.

Cloud Run previously optimized around request-driven services, run-to-completion jobs and worker pools. The new resource fills a different shape: one long-lived process that needs a durable network identity but does not justify a traditional VM or horizontal autoscaling. That is especially relevant to personal AI agents, lightweight control planes and low-duty-cycle workers. The trade-off is that this is not persistent compute in the storage sense: the container filesystem and in-memory state are disposable, so durable state still belongs in external storage.

Cloud Run instances are distinct from ordinary service instances. They are top-level resources that are created and operated individually rather than produced by an autoscaler. Each has its own stable `run.app` URL and can be started, stopped, restarted, updated or deleted directly. Google describes the resource as a lightweight serverless VM for workloads that need one stable runtime rather than a horizontally scaled service.

Google’s launch material explicitly uses personal agents such as OpenClaw and Hermes as examples. These systems often need one process available for one user, with bursts of work separated by idle periods. A normal Cloud Run service wants to scale to zero or scale out with requests; a VM stays allocated and brings more operating-system management. Cloud Run instances instead keep one managed container alive and give it a stable endpoint.

Google says a 1 vCPU, 1 GiB instance running continuously for 30 days costs $5.70 in its launch example. The resource model uses shared CPU: workloads can burst to their allocation, while Google documents a 6.25% baseline outside the burst budget. That makes the shape attractive for agents that are mostly waiting and occasionally spike, but compute-heavy continuous workloads need their own benchmark rather than assuming the headline example applies.

An instance can run for days or weeks through automatic restarts, but updates restart the container and Cloud Run instances do not have persistent disk storage. Stopping an instance also destroys in-memory files and unpersisted state. Builders therefore need Cloud Storage, a database, NFS or another external persistence layer for anything that must survive lifecycle events.