Hermes Agent VPS setup vs Vercel, Supabase and Railway

The speaker explains how he hosts Agent Wikis and maintains its content with Hermes Agent on a small VPS. He compares this setup with Vercel, Supabase and Railway, while acknowledging the convenience and operational safeguards those services provide. His example uses 1 vCPU, 1 GB of memory and 25 GB of storage. Telegram provides access to the agent without keeping his laptop running.

Agent Wikis stores its pages as Markdown files in Git rather than a database. The app renders files from disk on each request and rebuilds its in-memory search index when content changes. A server pull makes updates live without a rebuild or restart. Caddy handles TLS and reverse proxies the site to a local service.

The self-hosted AI agent uses scheduled scout and research workflows to propose content updates. A separate demand loop turns repeated unsuccessful MCP searches into research tasks. In the demonstration, five gaps qualify because each topic appeared at least twice in seven days. The speaker says this system stores aggregate search results without prompts, IP addresses or identities.

Two human gates remain: approving proposals through Telegram, then reviewing diffs and merging changes. The speaker recommends managed services for sensitive authentication, regulated data, heavy traffic or team deployment needs. This installment covers the site without a database; deploying his database-backed game is reserved for a follow-up.