Hermes forgets you. Every. Single. Time.
Open any Hermes Agent thread on Reddit or GitHub and the same frustration comes up: it isn't the install — it's the amnesia. We fixed it at the infra layer with persistent memory wired into every instance.
Hermes alone
- What was that project we discussed last week?
- Could you re-explain what you're working on?
- Sorry, I don't remember our last conversation.
Hermes + Recall
- Welcome back. Ready to continue where we left off?
- Yes, the API migration we started Monday — I have all the context.
- You mentioned this 3 weeks ago — should we follow up?
Same question. Two answers. One reason.
Same user. Same question. One day apart. On the left, vanilla Hermes. On the right, Hermes + Recall. Watch them side by side.
This is the difference. Persistent memory — never resets, never shared, never accessible to our staff.
Most people install Hermes once. Most people don't finish.
Hermes Agent is brilliant. Installing it is not.
The raw install path
- Find a server that won't crash
- Write 3 config files by hand
- Create a Telegram bot with BotFather
- And after all that — nothing remembers anything
Most people never make it past the install.
Your agent is already running
Open the site, pick a plan. We wire up your AI. Live in 60 seconds.
- Zero CLI, zero config, zero YAML
- Auto-onboarding — we configure the AI, you just use it
- Every native Hermes skill pre-installed, persistent memory wired in
- Telegram bot ready, no BotFather ritual
- Memory live from message one — never start from zero
- Your data never leaves your private instance
The agent you wanted from the start, without the install hell. 💚
How we compare.
Not all hosting is equal. Compare what's actually included.
Based on publicly available information as of April 2026.
Integrates with
Encrypted at rest
Per-tenant AES-256 keys. Your data is encrypted on disk and in transit — always.
Your own server
Every plan runs on a dedicated, isolated instance. No shared resources, no noisy neighbors.
Zero staff access
Our team cannot read your messages or memory. Ever. You control what you share.
Your Hermes is waiting.
Stop starting from zero. Your Hermes, live on Telegram in 60 seconds — with memory that persists across every conversation.
Cancel anytime · Month-to-month · Export your memory anytime · No surprise charges
Frequently asked questions
No — not during support, not for debugging, not ever. Your Honcho memory entries and chat logs are encrypted at rest with per-tenant keys that live only inside your private instance. Our operators can restart your container, scale compute, and ship updates, but they cannot decrypt or read a single message. When you open a support ticket, you choose what to share — we never pull data from your instance without explicit consent in that ticket. We run this the way we'd want our own therapist's notes run: encrypted, siloed, and fundamentally off-limits to the infra team.
Yes — no lock-in, no penalty, no "call us to cancel" trick. Cancellation is one click in your dashboard. After cancellation, your agent and memory keep running until the end of the billing period you've already paid for, so you don't lose anything mid-month. At the end of that period, we cleanly tear down your private instance, wipe the Honcho memory layer, and delete all your conversation data within 24 hours. You can also export everything beforehand from the dashboard — conversations, memory entries, settings — as a portable JSON archive that stays yours.
Yes — every HermesRecall plan runs on a dedicated instance, not a shared cluster. Your agent, your memory, your data, your server. Nothing is shared with other users. This means consistent performance (no noisy-neighbor slowdowns), full isolation for privacy, and the ability to restart or scale independently. Your server runs 24/7 with encrypted storage and automated backups.