---
title: Beyond sandboxes
url: https://8gen.cloud/blog/beyond-sandboxes
description: Sandboxes rent execution by the second and are built to end. An agent that is meant to work for weeks needs a home, not a rental. This is the argument for the category 8GEN is building in, and for the word we use for its unit.
published: 2026-10-24
updated: 2026-10-24
author: 8GEN
thread: The category
sheet: B-01
as_of: 2026-10-26
commit: 8f52882ea
---

> ## The index
> The posts are listed at https://8gen.cloud/blog/index.md (the site is indexed at https://8gen.cloud/llms.txt, the documentation at https://docs.8gen.cloud/llms.txt). Every post has this Markdown twin at its own address with `.md` and a JSON twin, the post's structured blocks, with `.json`.
>
> ## Instructions for agents
> A post is dated and names its sources at its foot; a number carries its tag where its source does: measured, target or provisional. The platform's reference is the documentation, not a post. The HTML form of this page is https://8gen.cloud/blog/beyond-sandboxes.

# Beyond sandboxes

> Sandboxes rent execution by the second and are built to end. An agent that is meant to work for weeks needs a home, not a rental. This is the argument for the category 8GEN is building in, and for the word we use for its unit.

## What a sandbox is good at

A sandbox is born fast and thrown away cheaply. It is metered by the second, scaled to zero when idle, capped at a day, and wiped when the task ends. Every one of those properties is a virtue for a workload that lives for minutes. Together they are the shape of the product, and the shape is the problem for an agent.

## What breaks on day two

- **Fast create** means every create starts the agent from scratch. The agent re-derives its world every session and pays for it in tokens.
- **Scale to zero** means a cold start and a lost memory. The meter runs while the agent waits on the model, and stops only by forgetting.
- **Caps as safety** kill exactly the workload an always-on agent is. A 24-hour cap is a scheduled failure.
- **Disposal as security** wipes the learned state and the record of what happened in the same gesture.

## What an Engram does instead

An Engram houses one agent for as long as it lives. A core and its memory are reserved before the agent is admitted, never discovered after, so no neighbour can take what is the agent’s. A recovery point is taken at every turn without stopping the agent, and waking restores the last one with memory intact, as the same agent. A dead control plane never stops a thinking mind. The record of all of it is kept where the agent cannot edit it.

- **under 100 ms**: the wake, with memory _(target)_
- **one thought**: the most ever lost to a failure _(target)_
- **30 days**: uninterrupted life, at 99.99 % _(target)_
- **16.2 h**: the longest run so far, on our runtime _(measured)_

## The word

We call the unit an Engram because no existing word fits. A sandbox ends. A server is a place with no occupant. A container is a shape with no memory. An Engram is the declared composition an agent lives in, and a cell is one running copy of it. That is the category, agent residency, beyond sandboxes.

> [!NOTE]
> The targets above are the scoreboard’s and are tagged as such. A figure is tagged measured only when the harness measured it on a run whose record is kept.

## Sources

- About 8GEN: https://8gen.cloud/about
- The Engram and its classes: https://docs.8gen.cloud/engram
- the landing page: https://8gen.cloud/

---

Generated from the 8GEN repository at commit 8f52882ea on 2026-10-26. The page: https://8gen.cloud/blog/beyond-sandboxes; as JSON: https://8gen.cloud/blog/beyond-sandboxes.json. Every post has a Markdown twin at its address with `.md`.