Sine Box / Private workspaces
Private workspaces for files, code and commands.
Give your application or agent a workspace of its own. Choose Lite for lightweight commands or Sandbox for Linux workloads, with private files, execution records and snapshot recovery.
What you can build
Choose an environment for the task
Use Lite for supported lightweight shell and file operations. Choose Sandbox when your task needs a full Linux environment with an explicitly started runtime window.
Keep files and results together
Read and write private workspace files through the Console or API. Inspect saved command output, exit status and execution history alongside the files your task uses.
Recover work with snapshots
Create and inspect workspace backups, read saved files and restore from a snapshot. Recovery state remains visible so you can check the result before continuing a task.
Sine Box
Get started in the Console
Built for your workflow
- Private file processing and lightweight automation
- Linux tasks that need an isolated runtime
- A dedicated workspace for authorized agent sessions
Create a Box
Choose Lite or Sandbox when you create the workspace. Creating its metadata does not start a virtual machine or execute a command.
Prepare files and execution
Add the files your task needs. Review access, available credits and the execution estimate; for Sandbox, explicitly start a funded runtime window.
Run and inspect the result
Submit a command and retain its execution ID. Check output and final status, or query that same execution if the connection is interrupted.
Read-only API example
Read your workspace through the same API.
List files before making a change or submitting a command. This request reads the workspace; it does not start a Sandbox or run code.
export SINE_CLOUD_URL="https://sinecloud.dev"
curl "$SINE_CLOUD_URL/api/products/sine-box/boxes/$BOX_ID/workspace/files?path=%2Fworkspace" \
-H "Authorization: Bearer $SINE_CLOUD_API_KEY"Set BOX_ID to an existing Box ID. The Cloud API key needs Box fileRead access to that workspace, and its lifecycle must allow file access.
Set SINE_CLOUD_API_KEY securely in your environment with the required product permissions. Keep it on your server; never expose it in browser code.
Access and billing
Workspace access
Workspace access is scoped to your organization and Box. Available runtime kinds can require separate release approval and capacity. File access, command execution and runtime management each check the relevant permissions.
How usage is charged
Lite commands reserve credits and settle against confirmed execution time. Sandbox uses funded VM time, including idle time, rather than charging each command again. Review the current estimate and runtime expiry before starting.
View pricing