References and practical exercises.
Planning references explain decisions and checks. The budgeting exercise gives inputs, actions and expected results. Cloud deployment procedures have not been run end to end.
Where should your AI agent run?
Choose between an API-backed agent server and self-hosted inference by examining workload, data boundaries, hardware, and operational responsibility.
Planning referenceBudget an AI agent: a worked 30/90-day exercise
Follow a fictional API-agent budget from token usage to six calculator inputs, check normal and failure totals, and choose resources from evidence.
Worked budgeting exercisePlan your first Vultr agent server
A reference workflow for choosing a server, preparing SSH access, separating public and private ports, and verifying a deployment before it handles real work.
Planning referenceKeep a Hermes dashboard private with Docker and SSH
A concrete Hermes dashboard recipe: pin the image, bind only to host loopback, tunnel over SSH, and verify authentication, external reachability and host reboot recovery.
Planning referenceAccept a private n8n deployment with PostgreSQL and an external runner
A reference acceptance plan for private access, database readiness, synthetic workflow execution, persistent state, dependency recovery, and a separate host-reboot test.
Planning referencePut an agent behind a domain and HTTPS
Plan DNS, Caddy certificate automation, private upstream connections, authentication, and ongoing verification without mistaking a padlock for access control.
Planning referenceAn operations checklist for an agent with real tools
Define action boundaries, protect secrets, preserve useful logs, and prepare a recoverable deployment before granting an agent access to real systems.
Planning referenceRehearse a Hermes restore without replaying real actions
Actual Hermes API backup/import evidence with session, file and paused-task checks, plus a clearly separated untested CLI and duplicate-action recovery protocol.
Planning referenceMove an agent server without losing control
Plan a reversible cutover, avoid two active writers, reconcile in-flight actions, and retire old infrastructure with verified data and billing cleanup.
Planning referenceNo guides match. Try a different search.