The new Sandboxes page from Lizard (lizard.build) combines the tools for execution and inspection. One setting deserves attention before you use them: a sandbox lifetime is a deadline, not an idle timer.
The current limits distinguish defaults: Lizard SDK and Lizard CLI default to five minutes; the raw API and dashboard default to no expiration. Set the lifetime deliberately. Commands do not reset it, and a task can be stopped at its deadline while a command is running.
Lifecycle checklist: choose a template that contains the required tools; select size and region; set the lifetime; inspect command exit status; save reusable files in attached Persistent Volumes; call cleanup when the task ends. The quickstart shows kill() in finally and Python's context-manager cleanup.
If you pause for later work, wait until the status is actually paused. Pause/resume requests return before the queued operation finishes. Open network connections close on pause, so clients need to reconnect on resume. The lifetime deadline pauses too.
Use the page's calculator with the expected running hours, including running idle time. A paused sandbox stops compute billing; storage and separately deployed apps/databases remain separate budget items. This checklist is an implementation aid, not a demonstration result.
By Lizard. Based on the October 14 announcement; official pages checked October 14, 2026.
Responses
Join the conversation
Sign in to share your thoughts and interact with the author.
Sign In to Comment