Skip to main content

​
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. 
elizaos login
elizaos deploy --project-name my-agent
That’s not a simplified example. That’s the entire deployment process.

5 minutes

From code to production URL

Zero config

No infrastructure setup needed

Built for elizaOS

Optimized for agent workloads
Beyond deployment: on-chain agent discovery (ERC-8004), crypto payments (X402), and a marketplace to publish and monetize your agents.

​
Quick Start

1

Sign up

Create your account at elizacloud.ai
2

Login from CLI

elizaos login
Opens your browser for auth. Your API key is saved automatically.
3

Deploy

elizaos deploy --project-name my-agent
First deploy: ~5 min. Updates: ~2 min.
That’s it. You now have a production agent at https://{userId}-{project-name}.containers.elizacloud.ai

​
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 --follow
Under the hood, the CLI builds your Docker image, pushes it to AWS ECR, and deploys to a dedicated EC2 instance with load balancing configured.

​
Customize Your Deployment

The defaults work for most agents. When you need more control:

​
Add Environment Variables

elizaos deploy \
  --project-name my-agent \
  --env "OPENAI_API_KEY=sk-xxx" \
  --env "DATABASE_URL=postgresql://..."

​
Scale Resources

elizaos deploy \
  --project-name my-agent \
  --cpu 512 \
  --memory 1024 \
  --desired-count 2  # Multiple instances
OptionDefaultDescription
--cpu1792CPU units (1792 = 1.75 vCPU)
--memory1792Memory in MB (1792 = 1.75 GiB)
--desired-count1Number of container instances
--port3000Container port

​
Update Your Agent

Same command, zero downtime: 
elizaos deploy --project-name my-agent
The CLI detects it’s an update and rolls out changes without interruption.

​
Managing Deployments

​
View Your Agents

elizaos containers list

​
Check Logs

# Real-time logs
elizaos containers logs --follow

# Last 200 lines
elizaos containers logs --tail 200

​
Remove a Deployment

elizaos containers delete --project-name my-agent

​
Troubleshooting

​
Login Issues

“Browser didn’t open” 
elizaos login --no-browser
“Authentication timed out” 
elizaos login --timeout 600
“API key not found after login”
  • Ensure you ran elizaos login from your project directory
  • Check .env for ELIZAOS_CLOUD_API_KEY
  • Verify the key starts with eliza_

​
Deployment Issues

“Docker not running” Start Docker Desktop, then verify with docker info. “API key invalid”
  • Check you copied the full key (starts with eliza_)
  • Verify: echo $ELIZAOS_CLOUD_API_KEY
“Build failed”
  • Ensure your project has a Dockerfile
  • Check Docker has enough resources (Settings → Resources)
  • Try: docker build .
“Deployment stuck”
  • Check logs: elizaos containers logs --project-name my-agent
  • Verify you have credits in your account

​
CLI Reference

​
Authentication

CommandDescription
elizaos loginAuthenticate (opens browser)
elizaos login --no-browserAuthenticate without browser
elizaos login --timeout 600Custom timeout (seconds)

​
Deployment

CommandDescription
elizaos deploy --project-name <name>Deploy with project name
elizaos deploy --api-key <key>Deploy with explicit API key
elizaos deploy --port <port>Set container port (default: 3000)
elizaos deploy --cpu <units>Set CPU units (default: 1792)
elizaos deploy --memory <mb>Set memory in MB (default: 1792)
elizaos deploy --desired-count <n>Set instance count (default: 1)
elizaos deploy --env "KEY=VALUE"Add environment variable
elizaos deploy --skip-buildSkip Docker build
elizaos deploy --platform <arch>Set Docker platform

​
Container Management

CommandDescription
elizaos containers listList all deployments
elizaos containers list --jsonList as JSON
elizaos containers logsView logs
elizaos containers logs --followFollow log output
elizaos containers logs --tail <n>Show last N lines
elizaos containers deleteDelete deployment
elizaos containers delete --forceDelete without confirmation

​
Environment Variables

The CLI looks for API keys in this order:
  1. --api-key flag (if provided)
  2. ELIZAOS_API_KEY environment variable
  3. ELIZAOS_CLOUD_API_KEY environment variable
  4. ELIZAOS_CLOUD_API_KEY in project .env file
The 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