myHermy
Your always-on AI agent, powered by the AI plan you pay for
Start new thread
Ali Hasnain

myHermy - Your always-on AI agent, powered by the AI plan you pay for

byā€¢
myHermy is a personal AI agent that lives on a private cloud server you own ā€” always on, reaching out on WhatsApp, Telegram, Discord & Slack. Connect the ChatGPT, Claude, Copilot, or Grok plan you already pay for. Zero setup, daily backups, your data stays yours.

Add a comment

Replies

Best
Ali Hasnain
Maker
šŸ“Œ
Hey Product Hunt šŸ‘‹ I'm Ali, the maker of myHermy. Every AI assistant I tried had the same three problems: it forgets me the second I close the tab, it only works inside its own app, and it bills me per message on top of the subscription I'm already paying for. So I built myHermy ā€” a personal AI agent that lives on a private cloud server that's yours, stays on 24/7, and reaches out to you on WhatsApp, Telegram, Discord, or Slack instead of waiting for you to open an app. Three things that make it different: šŸ”Œ Bring your own AI plan. Connect the ChatGPT Plus, Claude Max, Copilot, or SuperGrok subscription you already pay for ā€” no API bills stacked on top of hosting. Your agent runs on credits you've already bought. šŸ–„ļø A server you actually own. Every agent runs on its own private VPS ā€” no shared infrastructure, no data mining, root SSH if you want it. Daily snapshots with 7-day retention and one-click restore. šŸ’¬ Always on, on every channel. It reads and drafts your email, manages your calendar, runs research, sets reminders, and pings you first ā€” wherever you already chat. It's powered by Hermes (the open-source agent from Nous Research), fully managed, zero setup ā€” provisioned in minutes. I'd love your honest feedback ā€” especially: what's the one task you'd actually trust an always-on agent to run for you? I'm in the comments all day šŸ™
Naim Azoutar

How do you handle message history privacy across those channels, what gets stored on the server vs only forwarded to the model?

Ali Hasnain
Maker

@naimzĀ Hey Naim! Great question! privacy was a core design decision, so happy to walk through it.

The short version: nothing sensitive lives on our servers.

Every agent runs on its own dedicated VPS that you own ā€” fully single-tenant. All the channel bridges (Telegram, WhatsApp, Discord, Slack, Signal, email) run on your box, so messages flow channel ā†’ your agent ā†’ model. They never route through our control plane.

What's stored where:

  • Conversation history lives locally on your VPS, never in our database.

  • Our database only holds account + infra metadata: server config, billing, and encrypted-at-rest credentials (bot tokens, OAuth). Zero message content.

  • Model calls go directly from your VPS to the provider (Anthropic/OpenAI/etc.), we never see the prompts or responses.

Why history is stored at all: it's what makes the agent actually useful ā€” the memory the model reasons over for multi-turn context, follow-ups, and long-term personalization across sessions and channels. The important part is where it sits: on your own server, not ours. So you get a stateful agent and full ownership - inspect, export, or wipe it anytime.

One honest caveat: daily backups are full-disk snapshots, so they do include that local history (7-day rolling retention, same datacenter, deletable anytime from your dashboard).

So "forwarded to the model" = everything; "stored on our servers" = essentially nothing beyond your account.

Let me know if you want to give it a try, will be happy to provide you a promocode for 40% discount on first month.

Ali Hasnain
Maker

@naimzĀ Hey Naim! Great question! privacy was a core design decision, so happy to walk through it.

The short version: nothing sensitive lives on our servers.

Every agent runs on its own dedicated VPS that you own i.e fully single-tenant. All the channel bridges (Telegram, WhatsApp, Discord, Slack, Signal, email) run on your box, so messages flow channel ā†’ your agent ā†’ model. They never route through our control plane.

What's stored where:

  • Conversation history lives locally on your VPS, never in our database.

  • Our database only holds account + infra metadata: server config, billing, and encrypted-at-rest credentials (bot tokens, OAuth). Zero message content.

  • Model calls go directly from your VPS to the provider (Anthropic/OpenAI/etc.) ā€” we never see the prompts or responses.

Why history is stored at all: it's what makes the agent actually useful, the memory the model reasons over for multi-turn context, follow-ups, and long-term personalization across sessions and channels. The important part is where it sits: on your own server, not ours. So you get a stateful agent and full ownership - inspect, export, or wipe it anytime.

One honest caveat: daily backups are full-disk snapshots, so they do include that local history (7-day rolling retention, same datacenter, deletable anytime from your dashboard).

So "forwarded to the model" = everything; "stored on our servers" = essentially nothing beyond your account.