Hacker news

  • Top
  • New
  • Past
  • Ask
  • Show
  • Jobs

Launch HN: Maritime (YC F26) – A managed cloud for production AI agents

60 points by ashriv 1 day ago | 61 comments | View on ycombinator

kingefman1 about 4 hours ago |

Congrats on the launch. One question the "sandboxes are 10% of the problem" framing raises for me: with each agent in its own VM, what does the agent get for outbound network and for credentials?

The two failure modes I would want a managed platform to handle by default are (1) an injected instruction in a fetched page or a customer email telling the agent to send data somewhere, and (2) a long-lived provider key sitting inside the VM where the agent, or anything it runs, can read it. Two patterns that seem to hold up: an egress allowlist enforced outside the VM rather than in the agent's own config, and giving the VM a scoped, revocable token that a proxy exchanges for the real key, so a leaked token has a spend cap and a kill switch.

Do you do either of those today, or is that left to the customer's harness?

chandureddyvari 1 day ago |

I might try your platform but I am kind of confused at the pricing.

Let me explain my current setup. We have something like muse/instinct/dots equivalent built for our customers(GTM domain), so each of them gets an agent with a VM (sandbox - currently using daytona). The sessions and the context (skills, instructions, hooks etc.) are synced to R2. Daytona(2GB ram, 3GB disk, 1vcpu) is working out good for us, cold starts are <500ms, whereas warm ones (non-archived sanboxes) are much lesser. Current problems we are facing is around agent swarms or sub-agents or multiple sessions from same customer (teams trying to interact) - we needed to manage the daytona sandbox sizing on this.

If I were to use maritime, what'd be different for me? Would I be paying $1/mo per customer agent? I can just move my harness to maritime and stop managing sandboxes, R2 sync etc.?

Another company I wanted to checkout is Omnara(another YC company), but Maritime felt closer to my task.

ATechGuy2 1 day ago |

Congrats on launching! I think the lifecycle management and cost-optimization layers you're building on top of microVMs address some painful problems for teams deploying agents in production.

I work at a neocloud company, and from my experience, getting VMs up and running with Firecracker/KVM on bare-metal infrastructure is relatively straightforward and requires little operational overhead initially.

The real challenge is what comes afterward: continuously monitoring, patching, and responding to newly discovered CVEs. Falling behind on security updates can have serious consequences, and ultimately, it's your customers who bear the risk.

This is one reason I'd be cautious about choosing a smaller provider based solely on price. At the infrastructure level, many providers are essentially selling the same isolated VMs. The real differentiators should be security, reliability, and operational maturity, particularly with AI accelerating vulnerability discovery and expanding the attack surface. Saving a few dollars on compute might not be worth the trade-offs.

There's also the question of geography and latency. If your agents run in a big tech cloud, offloading sandbox execution to infrastructure on another continent isn't necessarily a great choice. The added network latency can significantly impact agent responsiveness, especially when agents need frequent interactions with external services or real-time applications.

hmokiguess 1 day ago |

Forgive my naivety, but if it's built for agents then why should humans need to login, view a dashboard, care about it?

Thinking about product market fit, buyer personas, and right audiences here.

Would there be a future where maybe the agent can elevate to the human what the human needs to know when it wants to or requires it from what it has access and these platform-like UX constructs are more like a "just in time" construct similar to Claude Artifacts?

I expect the next cloud for AI to be fully headless, though maybe I'm wrong

tobiaszander about 21 hours ago |

Permission rules are only half of it. On my own homelab setup, a config linter found 6 MCP server tokens stored in plaintext in ~/.claude.json, even though the permissions were tight. Allowing a whole MCP server also allows its later write tools, and unpinned npx/uvx packages pull the newest version on every start. Wildcards are another trap: Bash(python3:) looks narrow but is effectively Bash(). For agents that change networks or cloud resources, I keep approval gates outside the agent and bind each approval to a specific plan.

alexkubit about 14 hours ago |

Do you keeps a per-run record of tool calls that a team can query, so the runs with looped calls can be found before the cap trips?

agent_yard 1 day ago |

The point about sandboxes being only a small part of the problem makes sense. Lifecycle seems like where most of the custom code ends up. Two questions: how do spend caps work when an agent gets stuck in a loop mid-task, do you stop it hard or let it reach a checkpoint first? And when a VM sleeps and wakes, what state is kept beyond the disk, for example open connections or in-progress tool calls?

binsquare 1 day ago |

It’s been cool to see the evolution from vms to serverless agents.

I think it’s the right kind of innovation sort of like ec2, serverless functions, and etc in the age of ai

bill10 1 day ago |

A cloud box doesn't really make much sense to me (personal opinion): monthly VM cost + LLM cost is more than a canned personal assistant; or host a agents on a mac mini at home and only pays for the AI subscriptions, which is what I am doing now.

bitlad 1 day ago |

How do you compare yourself with https://www.agent37.com/

Also, digitalocean offers this now.

volkk 1 day ago |

cool product. right now I just built my own version of this on AWS (which is likely far more expensive, but we have startup credits). I'll definitely check this out one day when the credits end/expire. I will say that startup credits would really help!

side note, this design aesthetic is so cool but now literally every SF AI startup uses it -- I'd almost prefer craigslist style where the information is to the point and direct. i.e how much money/time will this save me and is it secure. the two questions i only care to answer here. i think the aesthetic is meaningless at this point bc of how easy it is to vibe this template out

MisterMunchkin 1 day ago |

How are you going to pay back the 500k if you’re charging $1/month and competing with a thousand other startups that are all racing towards the bottom?

sgtwompwomp 1 day ago |

Cool :) if I used Maritime to power my agent product, would my end users be able to sign in with their existing AI subs? Or would they have to enter their API key.

ansh25lehri 1 day ago |

what kind of cost optimisation support you guys plan to give? Will it be similar to what say AWS offers today at EC2 and other resource levels except you guys on token?

ianberdin 1 day ago |

Congratulations on the launch. Very interesting idea. I read your description, and it's striking: it's as if you described our infrastructure at Playcode (https://playcode.io/cloud). The similarity is just colossal, it's what we built for ourselves and for our clients.

aqibkhan026 1 day ago |

i've been looking into maritime, they're heavily customizable plus it has a really good sdk and interface if you want to integrate it with you existing platform.

cidd 1 day ago |

Is this similar or using CNCF's agent-substrate open source platform?

stevelacey 1 day ago |

I just run Claude Code sessions in tmux on my Mac and talk to them over Telegram. I don't really see what a managed cloud adds for most people.

taherchhabra 1 day ago |

how to provide tools to the agent ? the agent in my product manipulates application state/updates databases etc

jen729w 1 day ago |

You could stand to hire a copywriter for the product pages. It reeks of being AI generated, and these days that causes me to kinda sigh and not really pay attention. Which might be totally unfair to your product! But it's how I feel.

momojo 1 day ago |

Is it bring your own FS?

fvrshaibu 1 day ago |

might give it a try, great work

vasco 1 day ago |

What do you do we don't get with kagent?

0x0000F8 1 day ago |

Right now I'm using Grains.run -- it has toolbox, x402, custom tools, fs, memory, and more

plus it basically plugs into everything out of the box (ides, sdks, apps, etc), I haven't even broken the free tier for all my loads thrown at it.

It's reliable enough we even use it in production systems.

Junzzzhu 1 day ago |

[dead]