Coasty
Computer Using Agents on Secure Cloud VMs That Run Forever
205 followers
Computer Using Agents on Secure Cloud VMs That Run Forever
205 followers
Most agent infrastructure runs workloads in shared environments, one compromised agent affects everything else. Coasty gives every AI agent its own isolated VM. No shared processes, no noisy neighbors, no blast radius. Each agent spins up sandboxed and tears down cleanly. True isolation. Not a container in a shared pool, a dedicated VM. Undercuts AWS & GCP. Built for agents, not retrofitted compute. Running code execution, browser automation, or multi-agent pipelines? Visit coasty.ai
This is the 2nd launch from Coasty. View more
Coasty
Launching today
Coasty is a computer use agent that operates real desktop software end to end. Started with healthcare prior auth, automating payer portals and legacy EHRs, and data removal for data privacy but now we're expanding into insurance and tax & accounting. Coasty does that work autonomously, with human takeover and full audit trails. Independently verified at 82.81% on OSWorld Verified (359 tasks), near the top of the leaderboard. No APIs required. If software has a screen, Coasty can run it.
Free Options
Launch Team
Coasty
how does the per-VM teardown actually handle stateful workloads like browser automation where you need session persistence across multiple steps
Coasty
@sevgiuurelukag Our VMs last forever, irrelevant of the tasks or the number of steps. And we specialize in long-horizon tasks(30m+), so we deal with this all the time.
Congrats on the launch!
The runs forever part is what stood out most agent VMs die when the session ends. Does it keep state between tasks, or reset each time?
Coasty
@irahimiam It keeps the state of the VM(doesn’t reset) and a snapshot when the VM fails for some reason, so you can restore and continue.
Running legacy software like a human sounds like a practical use case for computer-use agents. I’m curious how much setup is typically needed before an agent can reliably interact with an existing application.
Coasty
@amjad_shaik Not much setup is required! Just download the local version of Coasty and run it.
@nitish_kovuru That’s simpler than I expected. Does Coasty rely mainly on observing the UI like a human user, or does it also learn workflows over time to become more reliable with repeated tasks?
Coasty
@steven_snider We were horizontal haha. We’re still exploring which vertical to focus on but prior auth and healthcare was one of the first.
Coasty
For the developers here! Coasty is also available as an API.
You send a task in plain language, the agent gets a fresh environment, does the work, and returns structured results plus a full action log. Every click and keystroke is recorded, so you can replay exactly what the agent did. Setup takes 2 to 5 minutes per environment, then the agent runs unattended until the task is done or it decides a human should take over. It's modular so you can use the predict part of the harness to write an instruction for your own screenshots or any other part of the system. The pricing is fully transparent for every type of call you could make(at the end of Docs).
Docs are at Coasty/Docs. The quickstart gets you to a first running task in a few minutes. If you build something with it, tell me. I read everything in this thread.
@prateek_j1 given you started with prior auth and EHRs, the "every click and keystroke recorded so you can replay exactly what the agent did" part raises a real question for that use case specifically: those replays and screenshots would routinely contain PHI on screen. where does that action log live, who can access it, and what's the retention/deletion policy on it, since the audit trail itself becomes a second copy of sensitive patient data that needs the same protection as the source system
Coasty
@prateek_j1 @galdayan So yeah, the enterprise platform is much different as you pay for compliance and HIPAA, our zero-data retention policies and security systems so none of the data is stored on our side, just acted upon.
@prateek_j1 makes sense for the source data, but the follow-up is really about the action log itself. if every click/keystroke gets recorded so customers can replay what the agent did, that recording is capturing the same screen contents, including PHI on screen at the time. is that replay log covered by the same zero-retention policy, or does it persist somewhere (customer's own environment vs yours) since replay-ability kind of requires it to exist for at least some window
Is there a list of all softwares it supports?
Coasty
@ankur_jeswani It supports any software you can run on your desktop or the Virtual Machines we have, since it just uses a screen, mouse and keyboard.