Korve vs exe.dev
An application control plane or a persistent computer?
exe.dev is built around persistent Linux VMs for developers and coding agents. Korve is built around an application and the managed runtime, data, and operations resources it explicitly declares. The useful choice is the abstraction—not a feature-count score.
Primary-source review updated July 25, 2026.
Different layers, different strengths
exe.dev exposes more of a computer. Korve models more of an application's managed lifecycle. Neither boundary is universally better.
| Dimension | exe.dev | Korve |
|---|---|---|
| Primary unit | Persistent Linux VM with SSH and HTTPS | Application runtime plus declared managed resources |
| State | Persistent VM disk and copy-on-write VM clones | Managed Postgres, object storage, caches, backup and database branch workflows |
| Sharing | Private-by-default VM HTTP proxy with named sharing | Application access policy, invitations, grants, sessions, and project audit operations |
| Agent credentials | Scoped expiring API tokens and integration proxying | Scoped OAuth authorization plus role-checked API and operator actions |
| Automation | SSH CLI and HTTPS command API | Operation spec shared by API, dashboard, Rust CLI, MCP, and manifest |
| Managed primitives | Software is installed and operated inside VMs | Queues, crons, recovery, logs, metrics, budgets, and domains as project resources |
What exe.dev discloses
Personal: $20/month for a shared pool listed at 2 vCPU, 8 GB RAM, 100 GB pooled disk, 200 GB transfer, and up to 50 VMs.
Team: $25/user/month, with shared capacity, admin and user management, and SSO.
Usage: disk at $0.08/GiB-month, CPU at $0.05/core-hour, and active memory at $0.016/GiB-hour on the published usage card.
These are exe.dev's current public figures, not equivalent-workload estimates for Korve.
Choose by the work you want to own
Choose exe.dev when the product you want is a durable, root-access Linux computer for a developer or coding agent, with SSH-first workflows and copy-on-write VM cloning.
Choose Korve when the product you want is a deployed app plus explicitly managed data and operations resources controlled through one typed project contract.
Korve does not claim VM sandbox, raw-compute, or clone-performance parity with exe.dev.
Primary sources