Cloud Deployment Integration
An operator-controlled cloud deployment can place Steward governed routes between its agent containers and configured provider or wallet operations. This guide describes a reference topology for a node fleet with on-chain transactions on Base mainnet.Architecture
Each node runs self-hosted Steward in front of supported agent actions:- Steward API on port 3200 — agent CRUD, policy management, vault operations
- Steward Proxy on port 8080 — API credential injection (when enabled)
- Agent containers — ElizaOS-based agents connecting to Steward
How Provisioning Works
When a new agent is created:- The cloud provisioner calls
POST /agentsto create the agent in Steward - Wallet generated — encrypted EVM + Solana keypairs
- Policies applied — default policy template for the agent tier
- Agent token issued —
POST /agents/:id/tokengenerates a scoped JWT - Container created with only
STEWARD_PROXY_URLandSTEWARD_AGENT_TOKEN - Container starts — agent boots, connects to its LLM via the proxy
Production Reference
Container Configuration
Agents use the@stwd/eliza-plugin for Steward integration. The plugin is baked into the container image:
172.18.0.1 address is the Docker bridge gateway, allowing containers to reach Steward running on the host.
Network Setup
Steward binds to0.0.0.0:3200 so Docker containers can reach it via the bridge network:
The
STEWARD_BIND_HOST=0.0.0.0 setting is required in a containerized deployment. Without it, containers cannot reach Steward because it only listens on localhost.Deploying Your Own
To replicate this setup:- Deploy Steward (Self-Hosting Guide)
- Create a tenant for your platform
- Set up the provisioning flow (agent creation → policy → token → container)
- Use the ElizaOS plugin or SDK in your agent containers
Related
- Architecture — System design overview
- Self-Hosting — Deploy your own instance
- ElizaOS Plugin — Agent integration
- Docker Guide — Container deployment