Sandbox Management
Sandbox management in Buddy provides you with a full suite of tools once the Sandbox is created.
Terminal
The Terminal tab provides direct access to the Sandbox command line.
Image loading...
Logs
The Logs tab provides a real-time access to Sandbox system logs: app output, service startup, and First Boot CMDs (package installation, system updates, service configuration).
Use the dropdown to switch between logs for each app (e.g., npm start) and First Boot execution logs. Search logs and Refresh help you find entries and update the output.
Image loading...
Filesystem
The Filesystem tab provides access to files within Sandbox.
Image loading...
Variables
The Variables tab lists environment variables, keys, and assets for the Sandbox. You can add new entries with New, filter by Group, and manage values. Each variable shows its name and value (or type indicator for files/keys).
Image loading...
Activity
The Activity tab displays the history of pipeline runs in the Sandbox, including information about their status, date, and branch.
Image loading...
Permissions
The Permissions tab allows you to manage user/group access to specific Sandboxes. It enables you to define what actions users assigned to a particular Sandbox are allowed to perform.
Image loading...
How do Sandbox permissions work?
Sandbox permissions override project-defined roles. For example, it is possible to grant access to a user with a Viewer role permission to use a Sandbox, or restrict access for a user with a Developer role by setting their permission to None (Deny).
Available access levels
The following access levels are available for Sandbox permissions:
Manage - Users with the Manage role have full control over the Sandbox. They can:
- Edit all Sandbox settings.
- Delete Sandboxes.
- Manage user permissions.
View-only - Users can only view the Sandbox Activity tab but cannot use or modify it.
Project role (default) - Permissions will be inherited based on the user's role in the project.
None (Deny) - No access to the Sandbox.
Managing groups and users
You can add both individual users and entire groups to Sandbox permissions. Each user or group can be assigned a different access level, allowing for fine-grained control over who can do what with the sandbox.
YAML
The YAML tab displays the current Sandbox configuration in YAML format.
Image loading...
Preparing Sandbox with YAML
The YAML configuration allows for easy management and versioning of environments. Example:
yaml- sandbox: my-app-sandbox name: My Application Environment os: ubuntu:24.04 first_boot_commands: |- apt-get update apt-get install -y nodejs apps: - node server.js endpoints: - name: www endpoint: 80
For detailed information about YAML parameters, see the Sandbox YAML documentation.
Settings
In Settings you edit the Sandbox configuration: name and resources, first boot commands and apps, endpoints, timeout, snapshots and tags.
Snapshots for this Sandbox are listed under SNAPSHOT NAME. Use the three dots next to a snapshot to open the menu:
- Run this snapshot in a new sandbox
- Revert to this snapshot
- Delete.
Sandbox timeout stops the Sandbox automatically after a set number of seconds since the last start.
Image loading...
Snapshots
Snapshots are saved states of the Sandbox at a specific point in time. Create one from the context menu (three dots) on a Sandbox card or from inside the Sandbox. Create snapshot opens a dialog where you set the name and confirm. To manage them (run in new sandbox, revert, delete), see Settings and SNAPSHOT NAME.
List all snapshots
On the Sandboxes view, open the menu (three dots) next to New sandbox and choose Snapshots to see all snapshots in one place.
Image loading...
Sandbox Folders
Sandbox folders work exactly the same as for projects and pipelines, allowing you to store Sandbox servers according to a selected pattern. To add or manage a folder, click the three dots at the top when on the Sandboxes view:
Image loading...
Sandboxes Actions
Sandboxes can be managed using dedicated actions:
Last modified on Mar 11, 2026