Sandboxes on Targon

Not every job needs a server you keep for months.

Sandboxes on Targon are short-lived, isolated Linux environments for development, testing, previews, and agent workloads. Think of a disposable computer: its own files, resources, and network access, built to be created, copied, paused, and deleted faster than standing up traditional infrastructure.

You pick a template, set optional idle and delete timers, and Targon opens the sandbox in your dashboard when it is ready. Connect in the browser, over SSH if you attached a key, or both.

For long-lived infrastructure, confidential GPU VMs, or reserved capacity, use Targon Virtual Machines or Bare Metal. Sandboxes are for work that should start quickly and stay easy to reset.

Full walkthrough is in the Sandboxes guide.

Preview: Sandboxes are currently in beta. Available controls may vary by template and organization.

---

When a Sandbox is the right fit

Reach for a Sandbox when you need:

• A clean slate: try code or dependencies without touching your laptop
• Agent or automation workspace: isolated environment with predictable lifecycle
• Browser-first access: terminal or graphical Linux desktop, no local setup
• Parallel copies: fork the same setup for experiments or separate tasks
• Cost and clutter control: idle pause and automatic deletion after a timeout

If you need attestation, fixed regional capacity, or full host control, other Targon products are a better match. Sandboxes optimize for speed and disposability.

---

How you get started

You need access to a Targon organization. SSH keys are optional unless you plan to connect from your own terminal; browser terminal and desktop do not require a personal key.

1. Open Sandboxes in your organization on targon.com.
2. Click Create sandbox.
3. Choose a name (lowercase letters, numbers, hyphens).
4. Pick a template: filter by size, compare CPU, memory, and hourly price, and select a ready template. Choose desktop support if you need a GUI.
5. Set lifecycle: optional Idle timeout (pause after inactivity) and Delete timeout (permanent removal after a fixed period). Values are in seconds.
6. Attach an SSH key if you want local terminal access.
7. Click Create Sandbox.

Targon opens the new sandbox automatically. Status usually moves from Provisioning to Running within seconds.

---

Connect your way

On a Running sandbox, pick how you work:

• Browser terminal: open the Terminal tab for an interactive shell. Start another session when you need a second shell; reconnect if the session drops.
• Browser desktop: open the Desktop tab for a graphical Linux environment. It may take a little longer than the shell to appear. Use reconnect or full screen as needed.
• SSH: copy the command from Overview and run it locally. SSH works when the sandbox has one of your organization keys attached.

---

Manage, fork, and reuse

From the sandbox list or detail page you can pause to stop billing active compute while keeping the environment, then resume when you need it again. Idle timeout can pause for you after inactivity.

Fork creates an independent child from the current environment: parallel experiments, separate agent tasks, or risky changes without touching the original. Parent and child appear as a family in the list; each has its own workload ID.

Need to share a web app? Under Manage → Exposed Ports, add the port (TCP or UDP). Addresses show under Service Ports on Overview. Port 22 stays reserved for SSH.

When a setup is worth repeating, publish a template from Manage → General. Check Templates → My templates for status, then create new sandboxes from that configuration. Platform templates live under Templates → Platform.

Deletion is permanent. Deleting a parent does not automatically delete child forks.

---

Billing and support

The sandbox Overview shows running and paused hourly prices. Organization Billing summarizes hours, costs, trends, and recent activity.

Use Get support from the Sandboxes page and select the affected sandbox so the request includes the right context.

---

Automate when you are ready

Create sandboxes, drive lifecycle actions, terminal sessions, files, and desktop connections through the Sandboxes API. The Sandboxes guide points to the API reference for endpoints, WebSocket access, and error responses.

---

Thanks for building with us,
The Targon Team