ALWAYS-ON AGENT COMPUTERFounder-led beta · 5–10 builders

Give your agents
a computer of their own.

A private computer where your agents live and work—even when your laptop is closed. They keep persistent files, projects, terminal sessions, memory, and routines, and stay reachable from anywhere.

The first beta is for builders already using Claude Code, Codex, terminal agents, and VPSs. You bring the box; I set up the first workflow with you.
$49 founding setupFirst month includedThen $20/mo if useful
cloudbox — ubuntu@vps — /projects/acme
ready
From Telegram
now

Run the tests on the current branch and tell me what failed.

opening /projects/acme
resuming Claude Code
running npm test
! 2 failing tests found
summary saved to logs
result sent to Telegram
Latest result
test-failure-summary.md
delivered
Visible inTelegramdashboardlogspause available
Demo walkthrough

One request. One VPS.
The full run.

This is the experience being tested: a Telegram request becomes a real terminal-agent run, with status and results you can inspect. No fake play button and no platform magic hidden in the story.

cloudbox — workflow walkthrough
live flow
STEP 01

Message it

Send one concrete task from Telegram while you are away from your desk.

Run the tests and report what failed.
STEP 02

The box runs it

Your Linux VPS opens the project, resumes the terminal agent, and keeps a visible log.

$project → agent → command → logs
STEP 03

Get the result

Receive the summary, blockers, and artifact back in Telegram. Pause the run when needed.

status sent · result delivered

Want to see it on a real box? I will walk through the current build with you.

Ask for a live demo →
Who this is for

Built for people who already
live in the terminal.

The first users should understand the value quickly. This beta is narrow on purpose so we can learn whether one always-on workflow is useful enough to keep paying for.

Good fit
  • You already use Claude Code, Codex, Cursor, or terminal agents.
  • A real workflow stops when your laptop closes or you leave your desk.
  • You can bring a Linux VPS, or you are willing to create one.
  • You will share honest feedback about the setup and the result.
Not this beta
  • A ready-made hosted computer
  • GUI browser or email automation
  • Approval queues for every action
  • Mac Mini setup as the primary box
  • A security or uptime SLA
How it works

One workflow,
set up together.

01

Choose one workflow

We talk about what stops today and agree on one result worth testing—not a list of hypothetical features.

02

Set it up together

I configure your Linux VPS, Telegram channel, project workspace, and existing Claude Code or Codex subscription.

03

Use it for a month

We review real runs, logs, blockers, and outcomes. Then you decide whether the result deserves a monthly fee.

What exists today

A small, working system.
Not a platform roadmap.

Enough infrastructure to test whether a persistent agent workspace changes how builders work away from their laptop.

Requestreceived
Agentrunning
Logsvisible
Resultdelivered
Workspace
A Linux box that stays available.
Your project files and terminal-agent session live on a VPS you control, ready to resume without reopening your laptop.
Command channel
Send work from Telegram.
Start with a concrete request. Receive status, blockers, and a completion summary in the same conversation.
Existing tools
Bring your own agent plan.
Use your current Claude Code or Codex subscription. Cloud Box orchestrates the workspace; it does not resell model tokens.
Projects
Persistent workspaces.
Keep project files, sessions, logs, and produced artifacts in one place.
Control
Visible and pausable.
Inspect status and honest logs, then pause a run when you need to intervene.
Concierge
Founder help included.
Setup, debugging, and workflow tuning are part of the first-month test.
Founding beta · 5 spots

Is one useful workflow
worth paying to keep?

The beta is a real test, not a waitlist. I set up one workflow, we use it for a month, and you decide from the result.

$49
founder-led setup
first month included

Then $20/month if it earns a place in your workflow.

Apply for the founding beta
Included in the test
  • Founder-led setup on your Linux VPS
  • Telegram command and status channel
  • One real workflow configured with you
  • Setup debugging and tuning for the first month
Your VPS and Claude Code or Codex subscription are separate and remain under your control. This is a limited founding-beta offer, not a finished service plan or SLA.
FAQ

An honest beta,
with honest boundaries.

What do I need to bring?+

A Linux VPS, Telegram, and your own Claude Code or Codex subscription. We will confirm the exact setup and choose one workflow before touching the box.

What can it do today?+

The beta is focused on terminal-based agent workflows: coding, scripts, project maintenance, watches, routines, and other work that can run on a Linux VPS. GUI browser and email workflows are not part of this v0.

Can I see or stop what it is doing?+

Yes. The current system exposes status and honest logs, and includes a way to pause a run when you need to intervene. That is visibility and a brake—not an approval queue for every action.

Is it secure?+

The box is single-tenant and runs on infrastructure you control, but no system is absolutely secure. We review access and credential trade-offs during setup. This early beta does not include a security or uptime SLA.

Why is setup founder-led?+

Because the point of this beta is to learn which workflows are genuinely useful, where setup breaks, and what builders will pay to keep using. Manual setup is part of the research, not something hidden from you.

What happens after the first month?+

We review the runs and outcomes together. If the workflow is useful, the proposed beta price is $20/month. If it is not, we stop. You still control the VPS, project files, and agent subscription.

Start with the work

Bring one workflow that should keep moving after your laptop closes.

Tell me what you use today, what keeps stopping, and what result would make the setup worth paying for. I will reply personally.

Start a builder conversation