Agent 37 Cloud - Give every customer their own Hermes or OpenClaw agent
Agent 37 is managed hosting for persistent agents like Hermes, OpenClaw and ClaudeCode. So you don't need to run them on Mac minis or VPS yourself. One API call gives each of your customers their own always-on agent, from $3.44/mo. Founders use it to ship vertical agents to their own clients without babysitting servers.
Replies
Agent 37
@vishnukool this is actually super clean
The “no babysitting servers, just spin up an agent per customer with one API call” is exactly the kind of abstraction people want but rarely get this smooth in practice
One thing I’m curious about: when you scale to lots of customer-specific agents, what becomes the hardest part to manage in reality? cost control, tool permissions, latency, or keeping each agent properly isolated without context bleeding between tenants?
Also love the idea of making vertical agents feel like products instead of infra pain
Excited to see what people build on this 🔥
Agent 37
@md_khayruzzaman Cost control is at the top of one of the things we need to manage and just the health of the servers in terms of RAM and CPU.
Thanks!
This is a sharp wedge for vertical-agent teams. The part I’d want to understand is the customer boundary: when each customer gets a persistent agent with tools, are credentials, approvals, memory, and action logs isolated per customer by default, or does the founder wire that layer around the hosted agent?
Agent 37
@blah_mad So the default templates we offer comes with LLMs pre-wired, 1000+ tool integrations like Gmail, Calendar, Notion etc. via Composio pre-wired and a few other things.
But for custom use cases you can also create your own custom Docker images that doesn't have these pre-wired if you'd want to integrate with your own APIs.
Got it. Custom images for teams that want their own API layer makes sense.
The piece I’d still want explicit is the tenant boundary: are Composio connections, memory, approval state, and action logs isolated per customer by Agent 37, or does the founder model that around each hosted agent?
Huge congrats for @vishnukool on getting this out the door. cuts out a ton of standard marketing ops busywork for small teams, love that it's an api layer instead of wrestling with individual cli instances. excited to see where you take it next.....
Agent 37
@vikramp7470 Thanks Vikram!
Not everyone wants to maintain VPS instances or Mac minis. This looks like a much cleaner path.
Agent 37
@morgan__harriss Very true, thanks!
For me, the most intresting part isn't the hosting itself, it's the shift in how founders can think about AI products. Instead of building one shared assistant
Agent 37
@jennifer_cooker True, the goal is to make building persistent always on agents easy and affordable
This is super helpful! I have my own home lab but it already full of self hosted services and I don't want to host my OpenClaw or Hermes on the same machine with all my data. At the same time I don't want to buy another home lab like some Lenovo mini pc or Mac Mini which here in Canada we should wait at least until September.
I like that you made this product privacy friendly looking at your privacy policy!
Agent 37
@bogdan_stefanjuk Thanks!
Congrats on the launch @vishnukool. Turning a complicated infrastructure problem into a simple API is not easy.
Agent 37
@hamza_afzal_butt Thank you!
Congrats. I wonder how does Agent 37 ensure complete data isolation between tenants sharing the same underlying infrastructure?
Agent 37
Thanks @crystalmei
We follow a similar architecture to Modal as described here - https://modal.com/docs/guide/security. Each tenant is containerized and virtualized using gVisor which keeps them all isolated. Do you have anything in mind that you're thinking of to try us out ?
The per-customer always-on agent from one API call is the part I'd build on — shipping a vertical agent without standing up a server per client is exactly the friction I keep hitting. The thing I'd test first: where does each agent's memory/state actually live, and is it isolated per customer and exportable if a client churns or I later want to migrate them off Agent 37? I'd want that state to be portable, not locked to the hosting.
Agent 37
@noctis06 Yes, it's isolated per customer and exportable as needed. You essentially have full control over the sandbox container and can do any operation within it, like move data out/migrate etc.
Full container control plus move-data-out is exactly what makes this safe to build on — thanks. Two things I'd still want to pin down: when a customer's agent restarts or you redeploy, does the sandbox state (installed tools, memory, configured integrations) persist by default, or do I re-provision it each time? And is there a clean export/import so I can snapshot one customer's setup and stamp it onto a new tenant instead of wiring each from scratch?
Agent 37
@noctis06 yes the customer's data is processed by default. Basically everything in the home folder is preserved by default, which is where most harnesses like open cloud Hermes or even Claude Code save data.
Since we allow Docker images, you can basically templatize any setup that you have in mind and then install and spawn instances to your customers based on that image template
Tough Tongue AI
This is super helpful! We had to spend considerable for building agent creator for our customers and the infra work there was no way a competitive advantage.
Agent 37
@aj_123 Thanks Ajitesh. Out of curiosity what did you use ? I'd be happy to chat if it makes sense exploring integrating with us - https://cal.com/vishnukool/30min