The computer your AI agents live in.

Spin up a real environment for an agent, then own it, share it, move it across hosts, and prove exactly what it did. Everything a sandbox does, plus the one thing it cannot: you own it.

Start building See how proof works

No account needed to open and verify a shared environment.

app.reeg.xyz/env/nightly-evals

nightly-evals

Owned by you · 2 snapshots

Verified

History

Created environmentUbuntu · Python 3.12 · Node 221h ago
Ran the test suite142 passed24m ago
Saved snapshotSnapshot #1418m ago
Shared with DanaCan resume6m ago
Resumed on a new machineByte-identicaljust now

Verified independently. 4 checks passed.

no server needed

Built on the Sui stack

SuiOwnership & proof

WalrusStorage

SealEncryption

The problem

Agents do real work in a computer that was never yours.

Agents now write code, move money, and change records. The environment where all of that happens is rented from a vendor and vanishes the moment the session ends.

Rented, then gone

The agent's computer is a row in a vendor's database. When the session ends, the workspace is gone. You cannot keep it or reuse it.

Impossible to hand off

You can share a transcript of what happened, but not the actual workspace. A teammate or client cannot pick it up exactly as it was.

Nothing to stand behind

When a run is questioned, you have the vendor's word for what the agent did. No outside party can check it independently.

What makes it different

Own it, share it, move it, and prove it.

Reeg does everything a sandbox does: spin up, run commands, write files, snapshot, restore. The difference is what the environment is, and that unlocks four things a rented box cannot give you.

Own it

The environment is yours, held as data you control, not a tenant slot on someone else's server.

No vendor can change it, lock you out, or delete it
Gated by an object you hold on Sui

Share & fork it

Hand a whole live environment to a teammate, or fork a good snapshot to try two directions. The actual workspace, not a transcript.

Grant access by person, with optional time limits
Revoke any time, forward-looking

Move it

Kill it on one host and bring it back on another, byte-identical. Your work travels with you.

Resume on any machine
No lock-in to a single vendor or datacenter

Prove it

Anyone you choose can re-check the entire history against public records and confirm nothing changed after the fact.

Independent, offline verification
No trust in Reeg required

Proof, not promises

A record anyone can check, with Reeg switched off.

Anyone you choose can re-walk a run's entire history against public records and confirm nothing was changed after the fact. The check runs in their browser and needs no Reeg server. That is what makes “Verified” mean something.

Independent: no Reeg server in the trust path
Durable: the record outlives any one vendor
For free: proof rides along with ownership

VerifiedVerify independently

Checking the full history against public records...

okprovenance-head— replayed chain matches the on-chain head
okcheckpoint-count— 2 checkpoints vs on-chain count 2
oksequence-contiguous— checkpoint seqs are 0..n-1
okmanifest-hash— latest manifest matches the record

4 checks passedReeg servers: offline

Why Reeg

Everything a sandbox does. Plus the one thing it can't.

We took the latency trade on purpose. For a throwaway box for thirty seconds of work, a centralized sandbox is the right tool. For an environment worth owning, sharing, and standing behind, that is Reeg.

SandboxCentralized sandbox

Reeg

Spin up, run commands, write files

Snapshot and restore

Resume on a different host, byte-identical

You own the environment

Hand over the live workspace, not a transcript

Fork a run to try two directions

Anyone can verify it with the vendor offline

A competitor can copy any feature except letting you own the environment, and ownership is what makes the rest possible.

In good company

A flagship app for the AI OS on Walrus.

Reeg stores every environment on Walrus, gates ownership with a Sui object, and encrypts with Seal before anything leaves your machine. Built in the open, in the Sui ecosystem.

Built on

SuiWalrusSealMysten Labs stack

Programs & recognition

Sui Overflow 2025ApplyingNVIDIA Inception

Pricing

Pay for what you keep and prove.

Usage-based and honest. You pay for snapshots stored and anchored, which maps to our real Walrus and Sui costs plus a margin. We never hold your data hostage; the record is yours and verifiable without us.