Agent 37 Cloud

Give every customer their own Hermes or OpenClaw agent

Developer Tools

Artificial Intelligence

SDK

Visit WebsiteSee on Product HuntTwitter ⧉

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.

I have been running Hermes in a self-hosted setup with Ollama, and one of the biggest challenges isn't the agent itself, it's maintaining the infrastructure, monitoring uptime, handling updates, and ensuring reliability over time. Agent 37's approach of providing persistent agents through a managed platform is an interesting alternative for builders who want to focus on the product rather than server operations. Curious how much customization and control developers retain compared to a fully self-hosted deployment.

what happens when one customer's agent goes rogue, infinite loops, runaway API calls to other services, anything that spikes cost or behaves unexpectedly? since each customer gets their own always-on instance, curious whether there's any per-agent resource capping or kill-switch a founder can configure, or if that's left entirely up to whatever the founder builds on top of Agent 37

The per-customer always-on agent angle is the useful part here. I’ve seen the same “agent infra becomes a babysitting job” problem once tools and permissions differ by client. Curious how you separate tenant secrets/tool scopes when an agent is idle most of the time but still persistent?

I can see this being useful for SaaS companies that want to give every customer their own AI assistant without building the backend themselves.

Judging by the cost structure, this appears to be serverless. I’m curious about the latency on cold paths and whether usage-based billing will apply later on.

Congrats. I wonder how does Agent 37 ensure complete data isolation between tenants sharing the same underlying infrastructure?

The unit economics here look incredible for SaaS teams wanting to deploy dedicated AI features. At $3.44/mo per customer agent, how do you handle resource provisioning if a client's agent suddenly experiences a massive spike in background workflows or data processing?

The interesting constraint here is handoff quality: if each customer gets a persistent agent, the audit trail and failure state need to be as easy to inspect as the API call is to start.

This solves the exact tradeoff I keep running into. I looked at self-hosting part of my own AI agent stack to save on a per-minute provider fee, and the math always won on paper but lost in practice: the real cost wasn't the server, it was becoming the person who gets paged when an agent goes down for a paying client. $3.44/mo always-on, not-my-problem-to-babysit is the right price for that peace of mind. Curious how you handle noisy-neighbor isolation between customer instances at that price point.

Love this! But - are you compliant with EU laws?
Under what jurisdiction does your company run and do you have a DPA for EU/GDPR compliance?

Congrats on the launch @vishnukool. Turning a complicated infrastructure problem into a simple API is not easy.

The per-customer agent model makes a lot of sense for vertical SaaS. What I keep thinking about is observability: how does a founder show their client what the agent actually did?

Logs the end customer can understand, or at least something you can point to when they ask, "what did it do this week?" Is that on the roadmap or already there?

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!

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

Congrats on the launch 🚀 Agent 37–38 looks sharp, excited to see how it pushes AI agents into real workflows!

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.

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?

Not everyone wants to maintain VPS instances or Mac minis. This looks like a much cleaner path.