undefined

**Pros:**
- Familiar ops tooling (Terraform, Ansible, etc.)
- Easy to scale horizontally — just add more VMs
- Pay-as-you-go pricing on most providers
- Full control over networking and security

**Cons:**
- You own the uptime — no managed restarts or healing
- GPU instances get expensive fast
- Cold start if you're spinning up on demand

**Best for:** Teams that already have cloud infrastructure and want full control.

---

undefined

**Pros:**
- Zero server management — just push code
- Built-in health checks, auto-restarts, and scaling
- Easy preview environments for testing agent changes
- Usually includes logging and metrics out of the box

**Cons:**
- Less control over the underlying machine
- Can get costly at scale compared to raw VMs
- Cold starts on free/hobby tiers
- GPU support is limited or nonexistent on most platforms

**Best for:** Small teams that want to move fast without an ops burden.

---

undefined

**Pros:**
- Best price-to-performance ratio, especially for GPU workloads
- No noisy neighbors — predictable latency
- Full control over hardware, kernel, drivers
- No egress fees

**Cons:**
- You manage everything: OS, networking, failover, monitoring
- Scaling means ordering and provisioning new hardware
- No managed load balancing — you build it yourself

**Best for:** Cost-sensitive workloads, GPU-heavy inference, or teams with strong ops skills.

---

undefined

**Pros:**
- Zero idle cost — pay only for invocations
- Global distribution with low latency
- No servers to patch or maintain
- Scales to zero and back automatically

**Cons:**
- Execution time limits (often 30s–300s)
- No persistent state between invocations
- Not suitable for long-running agent sessions
- Limited runtime environments (no arbitrary binaries)

**Best for:** Stateless agent endpoints, webhooks, or lightweight tool-calling proxies.

---

User → API (Railway/Vercel) → Agent Runtime (bare metal GPU)

undefined

**Pros:**
- Fast for operators — one command, done
- Easy to script and compose with other CLI tools
- Works great in CI/CD pipelines
- Low overhead, no server-side UI to maintain

**Cons:**
- Requires terminal access and auth setup
- Hard to share with non-technical team members
- No real-time dashboard or visual overview
- Each tool has its own CLI conventions to learn

**Best for:** Day-to-day operations by the team that built the system.

---

undefined

**Pros:**
- Language-agnostic — any HTTP client can use it
- Easy to integrate with dashboards, Slack bots, or other systems
- Can enforce auth, rate limiting, and audit logging at the API layer
- Enables building custom UIs on top

**Cons:**
- More infrastructure to build and maintain (the API itself)
- Versioning and backwards compatibility become your problem
- Latency overhead compared to direct CLI-to-server
- Auth token management adds complexity

**Best for:** Teams building internal platforms or integrating deploys into larger systems.

---

{
  "tool": "deploy",
  "input": {
    "service": "agent",
    "version": "latest",
    "strategy": "rolling"
  }
}