Why Eliza Cloud?
You built an agent. Now you need it running 24/7, accessible from anywhere, with proper monitoring. The traditional path: write a Dockerfile, configure cloud infrastructure, set up load balancing, create CI/CD pipelines, manage SSL certificates, configure health checks… With Eliza Cloud: two commands.5 minutes
From code to production URL
Zero config
No infrastructure setup needed
Built for elizaOS
Optimized for agent workloads
Quick Start
1
Sign up
Create your account at elizacloud.ai
2
Login from CLI
3
Deploy
What You Get
Every deployment includes:Dedicated EC2 Instance
Your own t4g.small ARM server, not shared resources
HTTPS by Default
SSL certificates handled automatically
Health Monitoring
24/7 checks with automatic alerting
Zero-Downtime Updates
Push updates without interruption
Persistent URL
Same URL across all deployments
Real-time Logs
elizaos containers logs --followCustomize Your Deployment
The defaults work for most agents. When you need more control:Add Environment Variables
Scale Resources
Update Your Agent
Same command, zero downtime:Managing Deployments
View Your Agents
Check Logs
Remove a Deployment
Troubleshooting
Login Issues
“Browser didn’t open”- Ensure you ran
elizaos loginfrom your project directory - Check
.envforELIZAOS_CLOUD_API_KEY - Verify the key starts with
eliza_
Deployment Issues
“Docker not running” Start Docker Desktop, then verify withdocker info.
“API key invalid”
- Check you copied the full key (starts with
eliza_) - Verify:
echo $ELIZAOS_CLOUD_API_KEY
- Ensure your project has a
Dockerfile - Check Docker has enough resources (Settings → Resources)
- Try:
docker build .
- Check logs:
elizaos containers logs --project-name my-agent - Verify you have credits in your account
CLI Reference
Authentication
Deployment
Container Management
Environment Variables
The CLI looks for API keys in this order:--api-keyflag (if provided)ELIZAOS_API_KEYenvironment variableELIZAOS_CLOUD_API_KEYenvironment variableELIZAOS_CLOUD_API_KEYin project.envfile
elizaos login command writes to ELIZAOS_CLOUD_API_KEY in your project’s .env file.
Next Steps
TEE Integration
Deploy with Trusted Execution Environment for enhanced security
Self-Hosted Options
Full control with your own infrastructure

