- You
- One command
- Your cloud
- Railway
- AWS
- Docker
- Out of the boxProduction agent platform
- AgentOS runtime
- Postgres
- Auth
- Slack
- Your agents
- Any model
- Your data, your database
AgentOS templates are the starting point for running Agno in your own cloud: one repo that runs the same way on a laptop and in production - a deploy script for Railway, Agno’s infrastructure tooling for AWS (ECS, RDS, load balancer, optional EFS), and Docker Compose anywhere else.
Out of the box
- The AgentOS runtime: one FastAPI app with a REST API for agents, teams and workflows.
- PostgreSQL for sessions, memory, knowledge, eval results and traces.
- JWT auth in production, and a Slack interface that switches on when its tokens are set.
- Reference agents (Pal, Scout, context-provider agents), an eval runner, and workflow docs for building agents with coding agents.
What I built
- The AWS and Docker templates: ported the reference agents, structured the code and kept both in step with Railway.
- Persistent storage on AWS with EFS and access points, so an agent’s local data survives deploys - plus the infrastructure support for it in Agno.
- Scout and the context-provider agents in the Railway template, and the evals and docs synced across all three.