Bernato vs Replit Agent: Cloud Build vs Local Orchestration
Pick Replit Agent if you want zero-setup web app prototyping in a browser tab on Replit's hosting. Pick Bernato if your work runs on your hardware, your code never leaves your network, and you want a kill switch and audit log for long-running processes (AI agents, training, browser automations). They solve different problems.
Replit Agent is built around a "type a prompt, get an app" loop. The agent runs inside Replit's containers, writes code, runs it, deploys it on Replit Hosting. Bundled into Replit Core ($20/month). For a brand-new prototype where you don't already have a stack, it's the fastest path to "click this URL".
Bernato is the layer below that. A small Go daemon (bernatod) on every Mac, Linux box, or homelab Pi you own. One dashboard to spawn, watch, supervise, and kill long-running processes — Claude Code, Codex, Aider, training jobs, browser agents — on hardware you trust. Local-first on LAN. Mobile approval flows for destructive operations. Local activity log.
Feature matrix
| Capability | Replit Agent | Bernato |
|---|---|---|
| Where it runs | Replit cloud containers | Your Macs, Linux boxes, GPU rigs |
| Does code/data leave your network? | Yes — Replit hosts it | No — local-first; tunnel only when off-LAN |
| Mobile approval before destructive ops | — | ✓ (in-app) |
| Capability sandbox per spawn | Container isolation (vendor-defined) | macOS Seatbelt + capability tokens today; Linux/Windows trusted-host/open until parity ships |
| Audit log | Vendor logs | Local activity and capability log |
| Long-running ops (hours+) | Limited by Replit timeouts/quotas | Daemon-supervised, restart-on-crash |
| Runs Claude Code / Codex / Aider | — | ✓ (any CLI agent) |
| Cost | $20/mo Replit Core (bundled) | Free 3 nodes · paid checkout hidden this cycle |
| Time to first agent | ~3 min (account + prompt) | ~90s (download daemon, pair, spawn) |
| Kill from anywhere | Replit dashboard only | Web dashboard, bernatod ctl |
| Works offline (LAN-only) | — | ✓ (control plane needs internet for sign-in only) |
Pick Replit Agent if
- You're prototyping a brand-new web app from a prompt
- You want bundled hosting + agent in one product
- You're not sensitive to where code/data lives
- Your team is already on Replit Core
Pick Bernato if
- Your code or data can't leave your network (compliance, IP, sovereignty)
- You already have hardware sitting idle (Mac mini, GPU rig, homelab)
- You run long agentic workflows (overnight Claude Code, training, browser automations)
- You want macOS capability sandboxing — read this path, exec this binary, no network unless asked
- You need a local activity log for legal / compliance / sign-off
- You want web approval review for destructive ops
Use both
Replit Agent for one-shot prototypes you don't mind being in someone else's cloud. Bernato for the work that needs to live on your hardware — long-running, sensitive, repeatable. Different jobs, different tools.
FAQ
Can Bernato run a Replit-style 'build an app from a prompt' workflow?
Bernato runs the orchestrator layer — you'd point it at any CLI agent (Claude Code, Aider, OpenHands) that does the prompt-to-app work. Bernato supervises the process, sandboxes it, lets you approve from your phone, and keeps an audit log. The 'build from prompt' is the agent's job; Bernato makes it survivable.
Does my code or repo go to Bernato's servers?
No. The dashboard talks directly to your daemon over your LAN when it can. Off-LAN, traffic rides the daemon's outbound WebSocket connection to the Bernato broker and terminates on your machine; the control plane sees machine names and agent IDs, not your code or output.
How does pricing compare?
Replit Core is $20/month and bundles the agent with hosting + IDE. Bernato is free for 3 paired nodes; paid checkout is hidden while billing and support are verified. Different shape — Replit charges for compute + bundled agent; Bernato is the control plane, and you supply the compute.
Can I run Replit Agent jobs from Bernato?
If a Replit CLI exposes a process you can spawn locally, yes — Bernato spawns any command. The point of Bernato is that the long-running process runs on your hardware with your sandbox and audit, regardless of which model or agent does the thinking.