Deploy Hector¶
Get your own Hector instance running in under a minute. Pick a cloud provider below, log in with your existing account, fill in a couple of fields, and you're done — full Hector with embedded Studio UI at an auto-assigned URL.
Every deployed instance is self-contained: agents, tools, Studio UI, admin API, and A2A protocol all in one binary. No external dependencies required.
Cloud Providers¶
Railway¶
One-click deploy with scale-to-zero. SQLite for storage — zero setup.
| Domain | *.up.railway.app |
| Auth | GitHub OAuth |
| Database | SQLite (built-in) |
| Free Tier | Trial credits |
| Scale to Zero | Yes |
What gets provisioned
- Docker container from your repo
- Health checks at
/health - You set
HECTOR_AUTH_SECRETduring deploy - Config-as-code via
railway.json
Render¶
Blueprint-based deploy with persistent disk for SQLite.
| Domain | *.onrender.com |
| Auth | GitHub / Google / GitLab OAuth |
| Database | SQLite (persistent disk) |
| Free Tier | Yes |
| Scale to Zero | Paid plans |
What gets provisioned
- Docker web service with health checks
- 1 GB persistent disk at
/datafor SQLite - You set
HECTOR_AUTH_SECRETduring deploy - Recipe:
render.yaml
Heroku¶
Classic one-click deploy. SQLite for storage.
| Domain | *.herokuapp.com |
| Auth | Heroku account |
| Database | SQLite (built-in) |
| Free Tier | Eco ($5/mo) |
| Scale to Zero | No |
What gets provisioned
- Container stack with Hector Docker image
- You set
HECTOR_AUTH_SECRETduring deploy - Recipe:
app.json
Fly.io¶
Edge deployment with auto-stop/start machines and global regions.
| Domain | *.fly.dev |
| Auth | Fly.io account |
| Database | SQLite (volume-backed) |
| Free Tier | 3 shared VMs |
| Scale to Zero | Yes |
# One-command deploy
fly launch --config deploy/fly/fly.toml
fly secrets set HECTOR_AUTH_SECRET=your-secret-here
What gets provisioned
- Shared CPU machine (256MB) in your chosen region
- Auto-stop after idle, auto-start on request
- Health checks at
/health - Recipe:
deploy/fly/fly.toml
Docker Compose (Self-Hosted)¶
Run Hector on your own infrastructure. SQLite with persistent volume.
| Domain | Your own |
| Auth | N/A |
| Database | SQLite (volume-backed) |
| Free | Yes |
| Scale to Zero | N/A |
export HECTOR_AUTH_SECRET=your-secret-here
curl -O https://raw.githubusercontent.com/verikod/hector/main/deploy/docker-compose/docker-compose.yaml
docker compose up -d
Open http://localhost:8080 — Hector with embedded Studio UI is ready.
What gets provisioned
- Hector container (
ghcr.io/verikod/hector:latest) - Persistent volume for SQLite data
- Recipe:
deploy/docker-compose/docker-compose.yaml
After Deployment¶
Once your instance is running:
- Open the URL provided by your cloud platform (e.g.,
my-hector.up.railway.app) - Studio UI loads automatically at the root
/ - Enter your admin secret — the one you set during deployment
- Configure LLM providers and agents via the visual editor or upload a YAML config
Your instance includes everything: Studio UI, Admin API (/admin/), A2A protocol (/agents/), webhooks (/webhooks/), and health checks (/health).
Add a Provider¶
Anyone can contribute a deploy recipe for a new cloud provider. See the Deploy Recipe Contributing Guide for details.
Providers that require their config at the repo root (e.g., Railway, Render, Heroku) place the recipe file at the top level. Each provider also gets a deploy/<provider>/README.md for documentation.