DADA BOX Available now
A cloud computer for your AI agent
Let Claude, Cursor or Codex write code, install dependencies and run builds in a Box. Keep those tools off your own laptop.
Bring your own agent and model subscription.
Your agent. A separate environment.
Tasks run here. Your laptop stays free.
From a task to a link you can share
For prototypes, builds and experiments that need room beyond your own machine.
Connect your agent
Add DADA Cloud to Claude Code or another MCP client. Sign in to your account through the browser.
Give it a Box
Your agent creates a separate environment for the task. Code, dependencies and builds run in the cloud.
Share the result
Expose an app port over HTTPS to share your prototype. Check the box status in the console.
Pay for active time
Free includes 300 active box-minutes each month. Additional resources are accounted for separately.
Box
per active minuteIdle isn't billed. A forgotten box goes to sleep instead of burning your budget.
Database and S3
standard Dada Cloud ratesManaged Postgres and object storage with backups — the same ones as in the console.
Minutes count against your plan’s allowance. Check the limits and terms before starting. All plans →
Automatic migration to a permanent VM remains experimental. A brief pause is required; zero downtime is not guaranteed. The VM uses monthly billing.
Before you start
Capabilities, limits and answers without the fine print.
Do I need my own AI model subscription?
Yes. Bring your own agent and model subscription or API key. DADA Cloud provides the computing environment and does not resell access to Claude, Cursor or Codex.
Where do my code and data live?
Inside a Box on DADA Cloud infrastructure in Russia. It is a remote environment: uploaded files are stored in the cloud, not only on your laptop.
How is this different from a regular VPS?
A Box is designed for individual agent tasks: create an environment, do the work, then delete it. A VPS is intended to run continuously. Automatic migration from Box to a permanent VM remains experimental.
What if the agent breaks its environment?
You can delete the Box and create a new one. Save the files you need before deleting it: replacing an environment is not a backup.
Can I run several boxes?
Yes. Separate tasks can run in separate environments. Their combined usage counts against your plan’s limits.
Do I need to wait for access approval?
No request is needed for self-service access over MCP. Connect your client and sign in to DADA Cloud. The form on this page is for help with your use case.
Capabilities and limits
Create a Box and publish an app through your agent. Migration to a permanent VM has separate limitations.
Available
- Create an environment through your agent over MCP
- Run commands, builds and apps with root access
- Publish an application port at an HTTPS address
- Active Box time counts against your plan’s allowance
Limitations
- Automatic Box migration to a permanent VM remains experimental
- Migration requires a brief pause; zero downtime is not guaranteed
- Startup time depends on warm environment availability; no fixed startup time is guaranteed
Move a Box to a permanent VM
An experimental capability for moving an app and its environment to a permanent server. The end-to-end migration is not yet offered as a guaranteed working flow.
Automatic migration to a permanent VM remains experimental. A brief pause is required; zero downtime is not guaranteed. The VM uses monthly billing.
What the migration is designed to carry
- application files and attached volumes
- environment variables and secrets
- the startup command and published ports
- connected resources and a custom domain
See an example Box workflow
An example Box workflow
An illustration of commands and responses. This is a prepared scenario, not a running environment.
# play demo →
Start with one task
Bring your own agent and model subscription.