Log inSign up free

The infrastructure your agents need.

Isolated computers with a browser, desktop and persistent files, for any agent framework or coding harness.

Start deploying
$ curl -fsSL https://radian.sh/install | sh

Boxes, sandboxes, swarms, desktops.

For the work agents do.

Bring the agent you have.

32 frameworks and harnesses, plus any image you can run. No new agent loop and no SDK to adopt: Radian runs your own entrypoint and keeps its native sessions, approvals and state.

Agent frameworks

  • New project · detected settingsVerified on Radian
    Framework
    Vercel eve · eve 0.75
    Language
    TypeScript
    Workload
    service
    Radian runs
    eve build, eve start, HTTP sessions with NDJSON events
    Start command
    eve start --host 0.0.0.0
    Keeps
    Workflow world, sandbox state

    Continued the same native session after a real stop and start, with its workflow world intact.

Coding harnesses

Declarative and custom

Europe means Europe.

Europe at night from orbit, dithered: city lights from London to Milan, the Alps and the Mediterranean coast.

Europe

Builds, registries, computers, workspaces, native state, secrets, logs and backups run on European-owned, European-operated sovereign infrastructure.

  • Choose per project. One account and one team can run both.
  • Sign-in and payments use disclosed providers. They never receive your code, prompts, files, secrets or logs.
  • Moving a project between locations is an explicit transfer, never a silent failover.
  • Your models stay your choice. Agents call any provider from either location.

Leave whenever you want.

Export a project and run it on your own machines. Code, configuration, files, native sessions, pending approvals and checkpoints come with it. You bring fresh credentials.

Runner
Runs an exported project on any Linux machine. No Radian account, licence check or hosted API.
Formats
The deployment declaration and export manifest are public specifications.
Adapters
Native session and state transfer for each supported framework.
Clients
TypeScript and Python SDKs and the CLI, under the same licence.

The exit kit is open source under Apache-2.0. The hosted fleet, scheduler and operations are what you pay us for.

Export · support-agent · europemanifest v1
$ radian export support-agent  included  image sha256:9b1e4c…, radian.json, lockfiles  included  workspace /workspace 2.1 GiB, browser profile  included  eve Workflow world · 214 sessions  included  3 pending approvals, 2 committed checkpoints  included  run history, native events, audit log  rebind    4 secret bindings · values are never exported  blocked   none  wrote support-agent.radian-export (2.4 GiB, sha256 verified)$ radian-runner up support-agent.radian-export  running on this machine at http://localhost:3000  214 sessions restored · 3 approvals waiting for you  no Radian account or API used

Every portability claim is tested: stop the hosted project, export it, cut it off from Radian, restore it on a clean machine and run new work. Anything that cannot move is listed with its reason before you export.

Your agents can run Radian too.

Everything in the dashboard is an API call, with TypeScript and Python SDKs, a CLI and an MCP server. Agents get the same permissions and audit trail as people, and only the actions you grant.

Hand this to Claude Code, Codex or any agent with a shell. It reads our instructions and asks you only what it must.

Set up Radian for this project. Read https://radian.sh/agents.md and follow it step by step. It explains what Radian is, how to request beta access for me, and which questions to ask me first.
agents.mdllms.txt
claude mcp add --transport http radian https://mcp.radian.sh

# Tools your agent gets, scoped by your token:
#   deploy, promote, rollback
#   submit_run, follow_run, cancel_run
#   list_approvals, decide_approval
#   open_shell, export_project, get_usage

Everything around the agent.

Protected previewsEvery commit gets its own URL behind your team's sign-in. Previews use test credentials and their own state.
ApprovalsApprove, edit or reject the exact tool call, from the dashboard, the CLI, the API or your phone.
Take controlWatch the agent's desktop. Take the input when you need it; the agent waits.
Scoped secretsPer environment. Previews never get production keys.
Spend limitsSet a monthly budget. New work stops before you go over.
Promote and roll backNew work moves to the new version. Open sessions finish on the one they started with.
Teams and rolesOwner to observer. SSO and SCIM when you need them.
Events that survive reconnectsNative events stream live and replay from where you left.

Questions, answered.

No. Radian builds your repository or image and runs its own start command. A native adapter adds sessions, approvals and resume where your framework supports them. Without one you still get builds, previews, isolation, logs and exports.

Building an agent startup?

Let's talk about working together.

Get in touch

Give your agent the infrastructure it needs.

Start deploying