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.
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

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

Deploy

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

Scale Resources

Update Your Agent

Same command, zero downtime:
The CLI detects it’s an update and rolls out changes without interruption.

Managing Deployments

View Your Agents

Check Logs

Remove a Deployment

Troubleshooting

Login Issues

“Browser didn’t open”
“Authentication timed out”
“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

Deployment

Container Management

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