Author
Ryan Martin
Founder · SEAOTTER
Founder of SEAOTTER. Writes about managed Hermes, control-plane operations, and agency isolation.
Posts
One key. Every agent.
One org key. Every agent. Manage your whole Hermes fleet from Cursor, Claude, or Codex. Lifecycle, secrets, and ops without SSH.
Create your first hosted Hermes agent
Name an agent. Watch it provision. Open the dashboard. Typical time is a few minutes. No VPS. No SSH.
SEAOTTER Hobby: 2.83s to 0.16s after we doubled CPU
Same Python loop, same gVisor pod. 2.83s at 0.5 CPU. 0.16s at 1 CPU: about 1.5× a laptop, not 25×. Sandbox stays.
Keep hosted Hermes keys out of chat and .env
Hermes recommends a secret manager at startup, not keys in .env. On SEAOTTER you save once on the write-only Secrets tab. The value is never shown again.
Talk to your hosted Hermes from Cursor, Claude, or Codex
Connect a SEAOTTER-hosted Hermes agent to Cursor, Claude, or Codex in a few steps. No SSH. No pasting keys into every chat.
The SEAOTTER engineering blog is live
A short note on why we write here: technical posts on managed Hermes.
Managed Hermes hosting
SEAOTTER on seaotter.dev is managed Hermes hosting: a control plane for always-on Hermes Agent, without a VPS, installer, or SSH. Not seaotter.ai.
Self-host vs managed Hermes
Own the box, or operate from a control plane? Hours, failure modes, and a clear decision guide for hosted Hermes on SEAOTTER.
Agency playbook: one isolated Hermes per client
Package always-on Hermes for retainers without a VPS per client—per-agent namespaces, secrets, lifecycle APIs, and an activation checklist built for agencies.