Maritime
Every computer your agent needs
497 followers
Every computer your agent needs
497 followers
Maritime gives AI agents their own cloud computers. Host any kind of agent, customize its environment, and let it run code, browse the web, and use tools without managing infrastructure.
This is the 3rd launch from Maritime. View more
Maritime
Launched this week
Maritime gives AI agents their own cloud computers: persistent workspaces, disposable sandboxes, Linux and Windows desktops, and Android phones. Agents can run code, use browsers, and work in apps without APIs, with a human able to take over when needed. Whether you’re building a personal assistant or running thousands of tasks in parallel, Maritime handles the computers so you can focus on what your agent does.
Free Options
Launch Team / Built With
AWS Activate CreditsCredits that fuel your startup’s next milestone
Promoted
Hi hackers! I'm Maria, cofounder of Maritime (YC F26). Before Maritime, I researched AI agents at MIT.
Agents need different computers for different jobs: a throwaway sandbox for generated code, a workspace that’s still there next week, hundreds of clean machines for an eval, or a desktop for an app with no API.
Sometimes they need Windows or a phone.
We built Maritime to put all of these behind one API, on one bill. You can host any kind of agent and customize its environment with the software and tools it needs.
Sandboxes start at $0.011/hour for 1 vCPU and 2 GB of memory. Linux desktops are $0.12/hour, Windows desktops are $0.18/hour with the licence included, and Android phones are $0.15/hour. All are billed per second while running.
There’s a 7-day free trial with up to $20 of usage.
What are you building, and what kind of computer does your agent need?
For the Android phones - can an agent install its own apps on them, or do they come as fixed images?
Human takeover sounds useful. When control returns to the agent, how does it learn what the person changed?
Per-second billing for sandboxes makes sense. What about the persistent workspaces though? If one sits idle for a week, is there a storage charge, or does it only bill while running? That's the number I'd want before leaving agents parked.
Disposable sandboxes and persistent workspaces solve different problems. Making that choice explicit when a job starts would help avoid discovering later that a file needed for the next run is gone.
@oleksii_sekundant true that's why we added them
Variable agent workloads make billing complex - pay-as-you-go is tempting but unpredictable costs kill budgeting. How do you handle reservation optimization vs overprovisioning risk? That's the infrastructure moat.