exe.dev
exe.dev is persistent VMs you SSH into, with root, apt and systemd, on a flat monthly plan. We compare it in Sandbox providers. The trade-off is being 15th of 19 on Meter (subscription).
What is exe.dev?
exe.dev — Persistent VMs you SSH into, with root, apt and systemd, on a flat monthly plan. exe.dev sells long-lived Linux VMs driven over SSH, with root, a public hostname and a flat monthly plan rather than a per-second meter. It is on this page because a competitor's comparison table lists it: BYO repos with a setup script, SSH, Docker inside the guest, no session cap and flat pricing, and — per that same chart — no snapshot or fork story and no dedicated IPv4. toolweight has verified none of those rows, and the absences in particular are a rival's characterisation rather than a checked fact.
We track it in 1 comparison — Sandbox providers — so every claim below is a cell in a table you can open and check rather than an impression. Across those rosters it sits against 19 other tools, and what follows is where it visibly separates from them.
Where it gives ground.
- Meter — subscription, 15th of 19. Cloudflare Sandbox records per-10ms.
None of these disqualify it on their own. They are the fields to check against your own requirements before you commit, because they are the ones where a competitor genuinely does better.
A caveat on the data. Only 5 of the 26 fields we track for exe.dev carry a value, so treat this profile as partial — an absent red flag is not evidence that there isn't one. Last verified 2026-07-23. Every figure keeps its own provenance — measured by us, claimed by the vendor, inferred, or community-reported — and we would rather print a dash than a guess.
Its nearest neighbour in our data is ascii, and on the fields we score the two are close to indistinguishable — nothing we record separates them by enough to call. If you are choosing between them, the deciding factor is not in this table. Compare them properly.
- Fields we track
- 5 of 26
- Last verified
- 2026-07-23
exe.dev in Sandbox providers
Ranked against 20 tools across 26 sourced fields. Open the full Sandbox providers table.Present on this page only because a competitor put it there, and every capability cell reflects that: box's table credits exe.dev with BYO repos and a setup script, SSH, Docker in the guest, 24/7 VMs and flat pricing, and omits it from the rows for snapshots, forking, a dedicated IPv4 and BYO domains. The positive claims are believable precisely because they come from a rival, and they are recorded. The omissions are not: a competitor declining to tick a box is not evidence that the box is empty, so exe.dev's snapshot-and-fork cell is unknown here rather than a zero, and the 24/7 row buys it no runtime ceiling. Nothing on this row is measured, and no price, boot time or isolation detail is established at all — treat it as a placeholder until it can be sourced from exe.dev directly.
When to use exe.dev
exe.dev is the right call in these situations, each one drawn from a field we actually record:
- Long-lived SSH VMs on a predictable monthly bill.
- You want root, apt and systemd rather than a constrained runtime.
- You are prepared to verify the gaps a competitor's chart reports.
When not to use exe.dev
Reach for something else when any of the following is a requirement rather than a nice-to-have:
- Meter. exe.dev records subscription, 15th of 19 in the Sandbox providers roster. Cloudflare Sandbox records per-10ms on the same field. If that is a hard requirement rather than a preference, start elsewhere.
We publish this block because a comparison that only lists what a tool is good at is marketing. Every figure above sits on the same page as its source, and the field definitions are on the category tables if you want to check how we measured them.
Tools compared alongside exe.dev
Everything below shares at least one comparison category with exe.dev, ordered by how much overlap there is. For the reasoning on each — which fields it wins, which it loses — see exe.dev alternatives.Recent exe.dev changes
We have not logged a dated change for exe.dev yet. The timeline fills in as pricing moves, features ship and things get deprecated.Sources and gaps
What we don't know. 21 of the 26 fields we track for exe.dev are still blank: Cold start, Cold start (claimed), Isolation, Egress control, Max runtime, Persistent FS, Snapshot & fork and GPU, and 13 more. Those render as dashes rather than as zeroes or assumptions, because an empty cell and a bad cell are not the same thing and only one of them is honest. If you know any of these figures and can point at a document, tell us.
- box.ascii.dev/compareRoot in guest, Custom images, File up/download, Meter · Inferred · verified 2026-07-23
- exe.devPositioning · Vendor-claimed · verified 2026-07-23