Separate projects and accounts
Keep client work and personal work in different cloud Environments. Each has its own workspace, browser profile, website logins, and agent credentials, so the projects keep separate working state.
Use cases
A place for every project. Continuity for every task.
Give each project its own cloud Environment, with its own workspace, browser, and accounts. Keep related tasks in Sessions that share that Environment, just as different conversations can use the same computer.
Research and browser work
Sign in to a website yourself and let your agent work in the same browser. Gather sources, inspect a dashboard, or prepare a report with the files and browser state kept in one Environment.
Different tasks in the same project
Keep implementation, research, and maintenance in different Sessions with their own conversation histories. They share the project's files, tools, browser logins, and Sandbox, saving the cost of another Environment for each conversation.
Repository onboarding
Give an agent a persistent checkout and ask it to map architecture, dependencies, conventions, and operational risks.
Feature implementation
Keep planning, edits, tests, terminals, and reviewable Git state attached to the same durable environment.
Debugging and repair
Let the agent reproduce a failure, inspect runtime evidence, make a change, and verify the fix without losing its workspace.
Background maintenance
Schedule test suites, dependency checks, or recurring research in a cloud Environment. Return to its native history and workspace when you want to inspect the result.
Continue away from your desk
Start a task on your laptop, check progress from your phone, and continue from another device. The cloud Environment holds the working state without requiring your local computer to stay online.
Use your existing machine
Connect your computer to work with its installed agent and local project. This uses your own OS account permissions and depends on that machine staying available; cloud Sandbox isolation applies to hosted Environments.
Choose your workflow
Sandpi for you. Platform for your software.
Both use persistent Sandbox0 Environments. Each product has its own Environments, Sessions, and billing.
| Your workflow | Sandpi · sandpi.ai | Sandpi Platform |
|---|---|---|
| How you work | Control a native agent terminal, files, and browser yourself. | Your service creates Sessions, submits Runs, and streams events through an API. |
| Agent access | Sign in to your agent or supply its credentials. | Bring your model API key and an endpoint compatible with the native harness. |
| What you pay for | A hosted Environment plan. Your provider bills model usage separately. | Shared Sandbox runtime, billed by the second. Your model provider or gateway bills model usage directly. |
| Where it runs | A cloud Environment, or your own connected machine. | A persistent cloud Environment for headless work. |
Start a workspace