Skip to main content
Use the console to manage your organization’s sandboxes, snapshots, API keys, and usage.

​
Set up your account

Sign in to the console. If you are joining an existing organization, use its invitation link and complete email verification when prompted. If access is pending, contact the person who invited you with the email address you used. Select the organization you want to work in using the organization menu in the sidebar. Sandboxes, snapshots, and API keys belong to the selected organization.

​
Create an API key

  1. Select your organization and open API Keys.
  2. Create a key and copy its value. The console shows the full value only once.
  3. Run the installer and enter the key at its hidden prompt.
If you have already installed LithosBox, update your saved key with:
Check the connection with lithosbox check. A successful check creates a sandbox, runs a command, deletes the sandbox, and prints VERDICT: PASS. Keep API keys out of source code and shared logs. Revoke a key from API Keys when it is no longer needed or has been exposed. If a key cannot access a resource, check that both belong to the same organization.

​
Find your resources

  • Sandboxes lists your sandboxes and their current states. Open a sandbox to inspect its activity, logs, and resource use.
  • Snapshots lists saved checkpoints, including snapshots whose original sandbox has been deleted. Check durability before relying on a snapshot for recovery.
  • Usage shows resource use over a selected time range.
  • Audit shows who performed actions and whether those actions succeeded.
Your organization can have up to 20 active sandboxes, each with up to 4 vCPU and 8 GiB of memory. Creating, running, paused, and sleeping sandboxes count toward that limit. Archive or delete unused sandboxes to free a slot. See Limits for all resource and request limits.

​
Recovery

Choose the action that matches the sandbox’s state: Restoring a snapshot creates a new sandbox ID. Work performed after that snapshot is not included. Before deleting a sandbox or relying on a checkpoint for recovery, use sandbox.snapshot(wait_durable=True) and keep the returned snapshot ID. If a create request times out, check Sandboxes before starting another create; the original request may have succeeded. For slow image preparation, see Custom images.

​
Understand usage

Use Usage to review sandbox time, CPU, memory, and retained snapshot storage. Choose a time range to compare activity across runs. Usage is recorded in minute intervals, so short runs and rapid state changes may be grouped within one interval. Archiving releases an active sandbox slot but retains its saved state. Deleting a sandbox leaves its snapshots intact; delete snapshots separately when you no longer need them. The usage view reports resource consumption rather than invoice charges. Refer to your account’s pricing agreement for charges and credits.

​
Support

Contact your organization’s support contact or the person who set up your account. For a sandbox issue, include:
  • Organization name, sandbox or snapshot ID, and the time of the issue with its time zone.
  • The action you attempted, the full error message, and whether it still occurs.
  • SDK version, image reference, and a small example that reproduces the issue.
Run lithosbox --version to find your SDK version. Keep the affected sandbox available when practical, or record its ID before deleting it. Remove API keys, passwords, cookies, and private download links from anything you share.