A simpler Daytona
alternative.

Linux compute for your agent, built on Cloudflare. One account for API commands, files, SSH, browser terminals, and web previews. From $5/month.

Usage billing with a $5 minimum. Custom images. Open source.

Agent workspaceJavaScript SDK
import { Mainbrella } from '@mainbrella/sdk';
const client = new Mainbrella({
  apiKey: process.env.MAINBRELLA_API_KEY
});
const machine = await client.create({
  catalogId: 'node', size: 'small'
});
try {
  const result = await machine.commands.run(
    'node --version'
  );
  console.log(result.stdout);
} finally { await machine.kill(); }

From API call to working Linux environment.

Private services with independent machine lifecycles

Mainbrella’s Private Services prototype connects machines through named HTTP endpoints such as http://api.internal. Attach existing running machines to an account-owned network, register only the application ports you need, and detach them without stopping their peers. Your frontend can call a private backend without a public preview or a Mainbrella API key in the guest.

Daytona’s linked sandboxes place ephemeral children on their parent’s runner, with a shared network and DNS aliases. Deleting the parent deletes its children. Mainbrella’s explicit membership model gives HTTP services more flexible grouping and independent lifecycles; it is currently a local prototype, available only when networking.privateServices is true.

This is an HTTP service comparison: Mainbrella does not yet support arbitrary TCP, HTTPS, WebSockets, private IPs, or direct database protocols through Private Services. Daytona documents direct port connections. See setup and limits; no common networking benchmark establishes a speed advantage.

Choose the lifecycle your workload needs

Daytona uses usage-based pricing for compute, memory, and storage. Mainbrella includes a bounded compute allowance in each monthly plan. It fits temporary agent tasks where predictable limits matter.

Mainbrella saves filesystem snapshots explicitly; it does not provide persistent volumes or process resume. If your workload depends on Daytona-specific persistence or SDK behavior, check those requirements before migrating.

Provider details: Daytona pricing and persistent volumes · Internal networking reviewed October 7, 2026; pricing and persistence reviewed October 6, 2026.

Before you start

Can I connect a frontend and backend privately?

The local Private Services prototype supports HTTP between explicitly attached machines in the same account-owned network. Register the backend as api, then call http://api.internal from the frontend. Production support is not qualified; check networking.privateServices before use. Read the setup guide.

Is Mainbrella compatible with the Daytona SDK?

No. Use Mainbrella’s SDK or HTTP API and adapt the calls your agent makes. Validate creation, execution, files, and cleanup on one workload before migrating.

Can I run a coding agent inside the container?

You can install tools and run commands in a Linux environment sized for your workload. You supply the agent’s credentials. Plan-specific idle and session deadlines still apply; Mainbrella does not yet provide a managed, always-on agent service.

How long can a machine run?

Usage billing supports sessions up to 24 hours with a 30-minute idle timeout, within your selected spending cap. Existing legacy subscriptions retain their session limits. Read the complete limits.

Can I inspect or self-host the platform?

Yes. Start with the open-source repositories and their licenses. Self-hosting requires your own infrastructure and operations; a hosted subscription uses Mainbrella’s service.

Try your actual workload.

Start with usage billing, create an API key, and run your first machine. Need help checking fit? Talk to Andrew.

Start building — $5 minimum

Plan limits · Security · Service status · Open source

Works with your agent.

Use skill instructions with a coding agent, or connect HTTP tools in your application.

Five-step setup instructions

Step 1: Set up Mainbrella

Read https://mainbrella.com/SKILL.md and follow its Quick Setup. It covers the API key handoff (MAINBRELLA_API_KEY, starts with mb_), prerequisites, and the read-only doctor command. Ask the user only where the skill says to.

Step 2: Detect the project

Do not ask. package.json means JavaScript/TypeScript, pyproject.toml or requirements.txt means Python, Cargo.toml means Rust, and go.mod means Go. An empty directory gets a minimal Python project in a new subdirectory unless the user named a language.

Step 3: Integrate

Follow the skill's HTTP workflow, matching the project's package manager, module format, and environment loading. Select an available image for the project. If agent or tool-calling code already exists, wire Mainbrella in where command execution happens and keep the existing conventions.

Step 4: Verify

Run the skill's verification script: create a container, run echo "hello from mainbrella", check stdout and exit code, and stop the created container in a finally block. Pass means stdout "hello from mainbrella", exit code 0, and cleanup completed. If it fails, follow Troubleshooting and re-run once only after cleanup is confirmed and allowance permits. Preserve existing containers.

Step 5: Report

One paragraph: what changed, what ran, and what you verified. Then offer one next step from the skill: a custom image, an LLM tool that runs commands, or a coding agent running inside a container.