Self-hosting agents means separating four things: model, agent loop, history DB, and tool workers
krishnan · x · 2026-11-16
Post 2/8 of krishnan's thread: self-hosting an agent requires separating four components—the model, the agent loop, the history database, and the machines that run tools. In this setup the company runs the server, its PostgreSQL database, and the workers, while the model runs at Anthropic or a provider the company picks.
Related event: Anthropic Opens Private Beta for Self-Hosted Claude Managed Agents(4 posts)→
More from coding & agent
- Gemini 4 Hydrogen launched: 2.5x faster than 3.8 Flash, but how much is batching? — krishnan · 2026-11-16
- Running 13 agents in parallel: handhold the critical bits, let the rest rip all day — willcb · 2026-11-16
- Agent sessions stall silently when no worker polls—ops must watch for it — krishnan · 2026-11-16
- Self-hosted Managed Agents migrates nothing—not even session history—and drops webhooks and cron — krishnan · 2026-11-16
- Self-hosting agents buys control but you own the server, database, sandboxes and every release — krishnan · 2026-11-16
- Researchers formally specify ops interfaces for CockroachDB, Kafka and RabbitMQ to make AI operators verifiable — tianyin_xu · 2026-11-16