Secure VMA sandbox per task, inside your perimeter
Run agents inside your perimeter
Every agent task runs in its own sandbox on your cluster, under the permissions of the person who asked. Commands and outside connections wait for a decision, and every action is recorded.
Build the Q3 review deck from the updates doc and the valuation bridge. Same structure as Q2, the three flagged companies up front.
Reading the Q3 updates and the bridge workbook, then drafting from the Q2 template.
- Read q3-portfolio-updates.docx, 14 companies
- Read q3-valuation-bridge.xlsx, 3 scenarios
- Draft slides from the Q2 template, 18 slides
- Place the flagged companies first, Northwind, Fenwick, Alder
- Render q3-portfolio-review.pptx, 4.1 MB
- Wrote q3-portfolio-review.pptx, 4.1 MB
Deck is ready: 18 slides, the three variance companies on slides 3 to 5 with the covenant tests beside each, the full portfolio table in the appendix.
q3-portfolio-review.pptx4.1 MB · 18 slidesBuild the Q3 review deck from the updates doc and the valuation bridge. Same structure as Q2, the three flagged companies up front.
Reading the Q3 updates and the bridge workbook, then drafting from the Q2 template.
- Read q3-portfolio-updates.docx, 14 companies
- Read q3-valuation-bridge.xlsx, 3 scenarios
- Draft slides from the Q2 template, 18 slides
- Place the flagged companies first, Northwind, Fenwick, Alder
- Render q3-portfolio-review.pptx, 4.1 MB
- Wrote q3-portfolio-review.pptx, 4.1 MB
Deck is ready: 18 slides, the three variance companies on slides 3 to 5 with the covenant tests beside each, the full portfolio table in the appendix.
q3-portfolio-review.pptx4.1 MB · 18 slidesGive each task its own computer
Each task run starts a fresh sandbox on your cluster and destroys it when the run goes idle, so nothing carries over between tasks.
Decide what the network reaches
Sandboxes reach the internet only through a domain allowlist you set. A connection outside it is blocked before anything leaves, and both outcomes are logged.
Audit log
Who granted, shared and revoked access across the organization, and every agent permission decision, with who answered.
| Time (UTC) | Outcome | Event |
|---|---|---|
| Today | ||
| 09:24:48.117 | Blocked | Atlas connected to api.factset.com:443 · not in the allowlist, nothing left |
| 09:22:31.774 | Allowed | Atlas connected to pypi.org:443 · in the allowlist |
Showing 1 to 2 of 2 events
Keep a record of every action
Every command, file and connection a sandbox makes is a row in an append-only log, with who asked and who decided.
Audit log
Who granted, shared and revoked access across the organization, and every agent permission decision, with who answered.
| Time (UTC) | Outcome | Event |
|---|---|---|
| Today | ||
| 09:24:51.402 | Recorded | Atlas wrote q3-portfolio-review.pptx · under Q3 portfolio review deck, for Maya Okafor |
| 09:24:48.117 | Blocked | Atlas connected to api.factset.com:443 · not in the allowlist, nothing left |
| 09:24:20.633 | Allowed | Atlas ran python3 build_deck.py --render · approved by Maya Okafor |
| 09:23:58.090 | Asked | Atlas asked to run python3 build_deck.py --render · sent to a person to decide |
| 09:22:31.774 | Allowed | Atlas connected to pypi.org:443 · in the allowlist |
| 09:21:09.255 | Recorded | Atlas read q3-valuation-bridge.xlsx · for Maya Okafor |
| 09:20:44.812 | Recorded | Atlas read q3-portfolio-updates.docx · for Maya Okafor |
| 09:20:02.038 | Recorded | Atlas started a sandbox for Q3 portfolio review deck · for Maya Okafor · record a3f9c2e1 |
Showing 1 to 8 of 8 events
Run agents inside your perimeter
Sandboxes run as pods on your own Kubernetes cluster, in your cloud account, one per task run.
Build the Q3 review deck from the updates doc and the valuation bridge. Same structure as Q2, the three flagged companies up front.
Reading the Q3 updates and the bridge workbook, then drafting from the Q2 template.
- Read q3-portfolio-updates.docx, 14 companies
- Read q3-valuation-bridge.xlsx, 3 scenarios
- Draft slides from the Q2 template, 18 slides
Build the Q3 review deck from the updates doc and the valuation bridge. Same structure as Q2, the three flagged companies up front.
Reading the Q3 updates and the bridge workbook, then drafting from the Q2 template.
- Read q3-portfolio-updates.docx, 14 companies
- Read q3-valuation-bridge.xlsx, 3 scenarios
- Draft slides from the Q2 template, 18 slides
Ask before a command or connection
Actions that leave the sandbox are decided outside it, so a refusal holds no matter what runs inside.
Build the Q3 review deck from the updates doc and the valuation bridge. Same structure as Q2, the three flagged companies up front.
Reading the Q3 updates and the bridge workbook, then drafting from the Q2 template.
- Read q3-portfolio-updates.docx, 14 companies
- Read q3-valuation-bridge.xlsx, 3 scenarios
The agent wants to run this command on its own computer.
DetailsBuild the Q3 review deck from the updates doc and the valuation bridge. Same structure as Q2, the three flagged companies up front.
Reading the Q3 updates and the bridge workbook, then drafting from the Q2 template.
- Read q3-portfolio-updates.docx, 14 companies
- Read q3-valuation-bridge.xlsx, 3 scenarios
The agent wants to run this command on its own computer.
DetailsNothing leaves without a record
Files, connections and credentials each cross one checkpoint outside the sandbox, and each crossing is a row in the log.
Build the Q3 review deck from the updates doc and the valuation bridge. Same structure as Q2, the three flagged companies up front.
Reading the Q3 updates and the bridge workbook, then drafting from the Q2 template.
Deck is ready: 18 slides, the three variance companies on slides 3 to 5 with the covenant tests beside each, the full portfolio table in the appendix.
q3-portfolio-review.pptx4.1 MB · 18 slidesBuild the Q3 review deck from the updates doc and the valuation bridge. Same structure as Q2, the three flagged companies up front.
Reading the Q3 updates and the bridge workbook, then drafting from the Q2 template.
Deck is ready: 18 slides, the three variance companies on slides 3 to 5 with the covenant tests beside each, the full portfolio table in the appendix.
q3-portfolio-review.pptx4.1 MB · 18 slidesSecure by default
Boundary decisions are made outside the pod, the audit log is append-only, and the deployment runs in your own account.
Audit log
Who granted, shared and revoked access across the organization, and every agent permission decision, with who answered.
| Time (UTC) | Outcome | Event |
|---|---|---|
| Today | ||
| 09:24:51.402 | Recorded | Atlas wrote q3-portfolio-review.pptx · under Q3 portfolio review deck, for Maya Okafor |
| 09:24:48.117 | Blocked | Atlas connected to api.factset.com:443 · not in the allowlist, nothing left |
| 09:24:20.633 | Allowed | Atlas ran python3 build_deck.py --render · approved by Maya Okafor |
| 09:23:58.090 | Asked | Atlas asked to run python3 build_deck.py --render · sent to a person to decide |
| 09:22:31.774 | Allowed | Atlas connected to pypi.org:443 · in the allowlist |
| 09:21:09.255 | Recorded | Atlas read q3-valuation-bridge.xlsx · for Maya Okafor |
| 09:20:44.812 | Recorded | Atlas read q3-portfolio-updates.docx · for Maya Okafor |
| 09:20:02.038 | Recorded | Atlas started a sandbox for Q3 portfolio review deck · for Maya Okafor · record a3f9c2e1 |
Showing 1 to 8 of 8 events
Audit log
Who granted, shared and revoked access across the organization, and every agent permission decision, with who answered.
| Time (UTC) | Outcome | Event |
|---|---|---|
| Today | ||
| 09:24 | Recorded | Atlas wrote q3-portfolio-review.pptx · under Q3 portfolio review deck, for Maya Okafor |
| 09:24 | Blocked | Atlas connected to api.factset.com:443 · not in the allowlist, nothing left |
| 09:24 | Allowed | Atlas ran python3 build_deck.py --render · approved by Maya Okafor |
| 09:23 | Asked | Atlas asked to run python3 build_deck.py --render · sent to a person to decide |
| 09:22 | Allowed | Atlas connected to pypi.org:443 · in the allowlist |
| 09:21 | Recorded | Atlas read q3-valuation-bridge.xlsx · for Maya Okafor |
| 09:20 | Recorded | Atlas read q3-portfolio-updates.docx · for Maya Okafor |
| 09:20 | Recorded | Atlas started a sandbox for Q3 portfolio review deck · for Maya Okafor · record a3f9c2e1 |
Showing 1 to 8 of 8 events
Run on our sandbox or your machines
A task runs in the managed sandbox by default, or on a machine you pair from the terminal, with the same lifecycle and approvals. A paired machine is where work runs, never who runs it.
- Web
- iPhone and Android
- Desktop
- CLI
Build the Q3 review deck from the updates doc and the valuation bridge. Same structure as Q2, the three flagged companies up front.
Reading the Q3 updates and the bridge workbook, then drafting from the Q2 template.
- Read q3-portfolio-updates.docx, 14 companies
- Read q3-valuation-bridge.xlsx, 3 scenarios
- Draft slides from the Q2 template, 18 slides
Build the Q3 review deck from the updates doc and the valuation bridge. Same structure as Q2, the three flagged companies up front.
Reading the Q3 updates and the bridge workbook, then drafting from the Q2 template.
- Read q3-portfolio-updates.docx, 14 companies
- Read q3-valuation-bridge.xlsx, 3 scenarios
- Draft slides from the Q2 template, 18 slides
Work across Context from one sandbox model
Agent work in every Context product runs in a sandbox like this one, so your files, chat, apps, skills and scores share one permission system and one log.
- DriveFiles your agent writes reach Drive through an explicit push and are stored under the task with the requester's permissions.
- TogetherTasks you start from a channel run in their own sandboxes, with approval cards appearing in the thread.
- AppsApp backends run in an isolated runner without ambient access to the network or filesystem.
- SkillsThe steps a run follows inside its sandbox are stored as a skill your team can read and edit.
- EvalsAn agent judge opens each run's files and trace in its own sandbox, then scores them against your criteria.
Home
- q3-portfolio-review.pptx1h ago
- q3-valuation-bridge.xlsx2h ago
- q3-portfolio-updates.docx3h ago
- lp-letter.pptx5h ago
Home
- q3-portfolio-review.pptx1h ago
- q3-valuation-bridge.xlsx2h ago
- q3-portfolio-updates.docx3h ago
- lp-letter.pptx5h ago
Deploy in your environment
Install on your EKS or AKS cluster through KOTS, with an air-gapped bundle that carries every image, SAML and OIDC sign-in, SCIM provisioning and zero data retention enforced at the model gateway.
Context runs in production at Qualcomm. Read the case study.
Sandboxes are included in every Context workspace, including the Free plan. Plus costs 20 dollars a month per person, and enterprise deployments run in your own cloud. Talk to us about a plan.
Questions
Is a sandbox a virtual machine or a container?
A sandbox is an isolated container pod on your Kubernetes cluster, created for one task run by the agent-sandbox controller or Daytona. It runs as a non-root user with every capability dropped, a seccomp profile and no cluster service-account token. You can optionally use a per-pod runtime class.
What happens to a sandbox when the task ends?
When a run stays idle for the configured window, 30 minutes by default, the pod is destroyed and the task sleeps. The task's working files are snapshotted to your object storage and restored into the next sandbox. Credentials, dependencies and caches are never persisted.
Can a sandbox access the internet?
You choose the network posture: open, domain allowlist or workspace only. Under the allowlist, traffic passes through an egress proxy that refuses destinations outside the list and logs every decision. An empty allowlist denies all outbound traffic.
Does the sandbox have access to all my files?
No. Drive is not mounted. The agent fetches each file explicitly through a gateway that re-checks permissions on every file, and outputs reach Drive only through an explicit push.
Are credentials placed in the sandbox?
Not on the identity plane. No standing secret is placed in the sandbox environment, filesystem or process. Credentials are injected at the edge after an authorization check, and a stored secret is used through a brokered call that returns only the response.
Can a task run on our own hardware?
Yes. Pair a machine from the terminal and choose it as the task's runtime. It runs the same lifecycle and approvals as the managed sandbox, and it is where work runs, never who runs it.