Hey HN, I'm Nitish, co-founder of Coasty (coasty.ai). My co-founder Prateek and I built this after running into the same wall most agent developers hit: you need a real, isolated computer for your agent to actually do things, browse, run code, fill forms, submit jobs — and the existing options are either expensive, capped at 24-hour sessions, or both. What we built Coasty gives AI agents secure, isolated cloud VMs that spin up in 2–5 minutes. Each sandbox is fully isolated, agents get a real desktop environment with a browser, terminal, and filesystem. No shared state between runs, no session limits. The benchmark We ran our agent stack on OSWorld, the standard benchmark for computer-use agents. We hit 82% task success rate. For reference, most published results from well-resourced labs are in the 50–72% range. We're not cherry-picking tasks, it's the full eval. Why cheaper E2B charges per sandbox-hour with a hard 24-hour session cap. Most real agent workflows — job applications, research pipelines, async browser tasks, need longer sessions and burst capacity. We charge for actual compute consumed, no caps. On equivalent workloads, customers are running at 70% lower cost. The dogfooding story We run our own marketing agent on Coasty infrastructure. It handles Twitter posts and cold outbound email autonomously. If the VM infrastructure can't handle our own agent, it doesn't ship. That's the bar we hold ourselves to. Where we're at

800+ signups 14,000+ agent sessions logged and analyzed Early design partners across sales automation and QA testing

What we're looking for from HN Honest feedback. We want to know:

What breaks for you with current sandboxed agent infra? Is session length actually the pain point, or is it something else we're missing? If you've tried E2B or Modal for agent workloads, what made you stay or leave?

The waitlist is open at coasty.ai. Happy to answer technical questions about the VM architecture, the OSWorld setup, or anything else.