Bernato vs Devin: Autonomous Cloud Engineer vs Self-Hosted Orchestration
Pick Devin if you want a turn-key autonomous engineer running tasks in Cognition's cloud, with their tooling and their bill. Pick Bernato if you want to orchestrate any CLI agent (Claude Code, Aider, Codex, OpenHands, Open Interpreter) on hardware you own, with code and data that never leave your network, ~50× cheaper. They're not substitutes — Devin is a packaged agent + cloud; Bernato is the runtime for whichever agent you pick.
Devin (Cognition) launched in 2024 as a polished, branded autonomous software engineer. The pitch: assign Devin a ticket, watch it do the work in Devin's cloud-based virtual machine. Public team plans land around $500/month per seat. Reviews split — strong on isolated, well-scoped tasks; weaker on large codebases and ambiguous specs. The model + the runtime + the tooling are bundled.
Bernato is one layer below — the runtime, not the agent. A daemon (bernatod) on every machine you own; a dashboard to spawn, supervise, sandbox, and kill long-running processes; a web approval flow. The agent inside is whichever CLI you trust (Claude Code, Aider, OpenHands, Open Interpreter, your own Python script). The launch is free for 3 paired nodes; paid checkout stays hidden while billing and support are verified.
Feature matrix
| Capability | Devin | Bernato |
|---|---|---|
| Category | Packaged autonomous engineer (agent + cloud + UI) | Process orchestrator + sandbox + audit (runtime) |
| Where work runs | Cognition's cloud VM | Your Macs, Linux boxes, GPU rigs |
| Code/data exposure | In Cognition's environment | Stays on your hardware |
| Model choice | Cognition-selected | Bring your own (Anthropic, OpenAI, local llama, etc.) |
| Capability sandbox per spawn | Cognition-defined VM | macOS Seatbelt + capability tokens today; Linux/Windows trusted-host/open until parity ships |
| Mobile approval before destructive ops | — | ✓ (in-app) |
| Local activity log | Vendor logs | Replayable, shareable |
| Long-running ops (hours+) | Yes (Devin's runtime) | Yes (daemon-supervised, restart-on-crash) |
| Cost | ~$500/mo team plans (per seat) | Free 3 nodes · paid checkout hidden this cycle |
| Compute cost | Bundled in subscription | Whatever electricity your machine costs |
| Open-source engine | — | Ujex (Apache-2.0) |
| Air-gapped operation | — | Possible (LAN-only, off-internet) |
Pick Devin if
- You want a turn-key product where the agent, the runtime, and the UI are one company's responsibility
- You're comfortable with code/data running in Cognition's cloud
- The ~$500/month/seat fits the budget and the scope of work
- You don't have hardware to dedicate, or don't want to think about infrastructure
Pick Bernato if
- Your code or data can't leave your network (legal, healthcare, defense, internal IP)
- You want to choose your model — Claude, GPT-4, local llama — not be locked to a vendor's pick
- You already have hardware (Mac mini, M-series laptops, GPU rigs)
- You want a 50× cheaper control plane and to keep the agent open-source
- You need air-gapped or LAN-only operation for any window of time
- You want capability tokens, macOS sandboxing, and a local activity log
Honest tradeoff
Devin's pitch is "no setup, just a ticket and a result." Bernato's pitch is "setup is 90 seconds, then you control everything." They're not in the same category — Devin is the *agent*, Bernato is the *runtime*. You can run Aider or Claude Code through Bernato and get an open, cheaper version of the Devin pattern; you cannot run Devin through Bernato. The right question isn't which is better in the abstract — it's where your code can run.
FAQ
Can Bernato do what Devin does — receive a ticket, write the code, open a PR?
Bernato is the runtime, not the agent. Point it at Claude Code, Aider, OpenHands, or your own script that does that flow. Bernato supervises the process, sandboxes it, gives you a kill switch, audits every command. The 'autonomous engineer' work is the agent's job.
How is Bernato ~50× cheaper than Devin?
Devin bundles agent + cloud compute + UI at $500/mo per seat. Bernato is just the control plane; this launch is free for 3 paired nodes, with paid checkout hidden. You pay for whatever model API you use, and the compute is your existing hardware. Compute economics flip from cloud-rented to locally-owned.
Does code I run through Bernato ever leave my machine?
No. The control plane stores account info, machine names, and agent IDs. The code being executed and the agent's output stay on your machine. The dashboard talks directly to your daemon over LAN; off-LAN, traffic terminates on your hardware via a Firebase-gated tunnel.
Can I use Bernato in an air-gapped environment?
Sign-in needs the internet for initial Firebase auth and pairing. After that, the daemon can be reached from the local dashboard path on the same machine or LAN when the browser has a valid session. Legacy static machine secrets are not accepted.