Skip to main content

Overview

This guide shows you how to deploy Orpheus on your own infrastructure - whether that’s AWS, GCP, Azure, bare metal, or your laptop. Orpheus Hero Time to first agent: ~5 minutes on fresh Ubuntu What you’ll get:
  • Production-ready Orpheus daemon
  • Queue-depth autoscaling (not CPU-based like K8s)
  • Workspace persistence and crash recovery
  • Full control over your infrastructure

Prerequisites

System Requirements

Minimum (CPU-only):
  • Ubuntu 22.04+ or Debian 11+
  • 2GB RAM, 10GB disk
  • Root access (sudo)
Recommended (with GPU for vLLM):
  • Ubuntu 22.04 with NVIDIA GPU
  • 8GB+ RAM, 50GB disk
  • CUDA drivers (see GPU section below)
For Testing in this Guide: We’ll use AWS EC2 for demonstration, but these steps work on:
  • ✅ AWS EC2
  • ✅ GCP Compute Engine
  • ✅ Azure VMs
  • ✅ DigitalOcean Droplets
  • ✅ Bare metal servers
  • ✅ Your laptop (Linux)

Quick Start (Automated)

Step 1: Clone Repository

Step 2: Run Setup Script

What it does (automatically):
  1. Installs runc + podman (container runtime)
  2. Installs Go (if not present)
  3. Builds Orpheus daemon from source
  4. Installs daemon to /usr/local/bin/
  5. Creates systemd service
  6. Starts daemon automatically
  7. Installs Ollama (optional, for local models)
Time: ~3-5 minutes Output:

Step 3: Verify Installation

Expected response:

Connect from Your Machine

Install CLI (Locally)

On your development machine (not the server):

Connect to Your Server

You should see:

Deploy Your First Agent

Option 1: Use Example

Expected:

Option 2: Create Your Own

Create two files: agent.yaml:
agent.py:
Deploy:

Testing with OpenAI/Anthropic

For agents that call cloud APIs, add API keys to agent.yaml:
Deploy and test:

GPU Setup (Optional)

For GPU-accelerated inference with vLLM: AWS:
Then run setup script - CUDA already installed!

Option B: Install CUDA Manually

If using regular Ubuntu with GPU:
Then run setup script.

Install vLLM

Configure agent to use vLLM endpoint.

Production Configuration

Firewall

Open port 8080 for Orpheus API:
AWS Security Group:
  • Add inbound rule: TCP port 8080 from 0.0.0.0/0 (or your IP)

Monitoring

Daemon logs:
Prometheus metrics:
Integrate with Grafana, Datadog, or your monitoring stack.

Resource Limits

Edit /etc/systemd/system/orpheusd.service:
Then reload:

Troubleshooting

Daemon Won’t Start

Check logs:
Common issues:
  1. Port 8080 in use:
  2. Runtimes not found:
  3. Podman not found:

Agent Deploy Fails

Check daemon logs during deploy:
Verify runtimes:

Agent Execution Fails

Check execution logs:
Common issues:
  • OOM killed: Increase memory: in agent.yaml
  • Timeout: Increase timeout: in agent.yaml
  • Missing dependencies: Check requirements.txt or package.json

Tested Environments

This guide has been validated on: AWS EC2 (us-west-2)
  • Instance: g4dn.xlarge (Tesla T4 GPU)
  • OS: Ubuntu 22.04 (Deep Learning AMI)
  • Setup time: 5 minutes
  • Test date: February 4, 2026
Key Features Tested:
  • Python runtime (OpenAI calculator) - 7.86s execution
  • Node.js runtime (OpenAI calculator) - 3.29s execution
  • Queue-depth autoscaling (1 → 5 workers)
  • ExecLog tracking (45 executions logged)
  • Self-hosted + published CLI integration

What You Need

Required:
  • Ubuntu/Debian server (cloud or bare metal)
  • Root access
  • Internet connection
You provide:
  • Server infrastructure (AWS/GCP/your own)
  • Domain/IP for access (optional)
  • API keys for LLMs (if using cloud APIs)
Orpheus provides:
  • Queue-depth autoscaling runtime
  • Workspace persistence
  • Crash recovery (ExecLog)
  • Multi-runtime support (Python, Node.js)
  • Model server management (Ollama, vLLM)

Next Steps

After self-hosting:
  1. Deploy agents - Move beyond examples
  2. Set up monitoring - Connect Prometheus metrics to Grafana
  3. Add TLS - Use nginx reverse proxy for HTTPS
  4. Scale horizontally - Deploy multiple instances (advanced)
Or migrate to managed cloud when you’re ready:
  • Sign up at orpheus.run
  • Same agents, zero infrastructure management