Isolated runtimes
One Hermes Agent workspace per customer or team, with package policy, secrets, memory, crons, and tools scoped to that runtime.
HostedHermes provisions isolated Hermes Agent runtimes, applies package policies, and gives founders and teams a managed control plane for automations, memory, crons, tools, updates, backups, and support.
Public launch shell is live now. Customer app, admin, API, docs, and status subdomains stay unattached until their targets are ready.
$ npm run cf:deploy ✓ built Next.js with OpenNext ✓ uploaded Worker: hostedhermes ✓ attached hostedhermes.com ✓ redirects live: www.hostedhermes.com → hostedhermes.com tryhermescloud.com → hostedhermes.com next: health route + app/admin surfaces
One Hermes Agent workspace per customer or team, with package policy, secrets, memory, crons, and tools scoped to that runtime.
Health checks, backups, support bundles, manual approvals, and safe updates are part of the control plane instead of ad-hoc scripts.
Start from supportable packages for personal assistants or DevOps operators, then expand capabilities under explicit policy.
Package catalog
Consumers and solo operators
A consumer-safe always-on Hermes lane for Telegram, briefings, reminders, and research — terminal disabled.
Technical founders and infrastructure teams
A sandboxed DevOps Hermes runtime with SSH allowlists, Docker CLI visibility, health checks, and update/backup workflows.
Live now
The canonical domain is attached to the production Worker. Redirect domains resolve to the apex. App, API, admin, docs, status, staging, and preview hostnames remain reserved until each target is deployed and protected.