CI runners · Blacksmith comparison
One runs-on: change. Your hardware, flat price.
Each ai-dev slot includes 3 self-hosted CI runners on your VPS. Switch from Blacksmith with a single label change — no per-minute metering, no $100 static IP fee.
version: 1
budget:
max_cost_usd: 5
policy:
require_checks: true
deny_paths:
- infra/prod/**Audited end to endGitHub-native workflowExisting checks stay in controlCost visible per task
The switch
The switch is one line
Ubuntu 24.04, 4 vCPU / 16 GB RAM default. Size configured in .maintainer.yml.
Before (Blacksmith / GitHub-hosted)
runs-on: blacksmith-4vcpu-ubuntu-2204After (developerz.ai self-hosted)
runs-on: developerz-4vcpuSide by side
Cost comparison
| developerz.ai | Blacksmith | GitHub-hosted | |
|---|---|---|---|
| Price | Included in $500 / ai-dev / mo | $0.004 / min + $0.50 / GB cache + $100 / mo static IP | $0.008 / min (private repos, since Mar 2026) |
| Your hardware | Yes — runs on your VPS | BYOC optional (extra setup) | No — GitHub cloud |
| Zero metering | Yes — flat price | No — every minute billed | No — every minute billed |
| Runners per ai-dev | 3 included | Separate contract | Unlimited (metered) |
Blacksmith pricing: blacksmith.sh/pricing (Jul 2026). GitHub Actions pricing: docs.github.com/billing/managing-billing-for-your-products/managing-billing-for-github-actions (Mar 2026 change).
Runner sizes
Pick your runner size
The runs-on: label sets the box. Bare developerz maps to the 4 vCPU default; add a suffix for more.
| Label | vCPU | RAM |
|---|---|---|
developerz | 4 | 16 GB |
developerz-2vcpu | 2 | 8 GB |
developerz-4vcpu | 4 | 16 GB |
developerz-8vcpu | 8 | 32 GB |
developerz-16vcpu | 16 | 64 GB |
developerz-32vcpu | 32 | 128 GB |
Security posture
Isolation and access, by default
- Each CI job gets a repo-scoped GitHub App installation token minted just-in-time, with a 15-minute TTL — the box never holds your App's private key.
- Every job runs in a fresh container that's destroyed on completion — nothing persists between jobs. Fork-PR jobs are refused outright, and CI on a public repo stays off until you opt in with ci.public_repos: true.
- Raw CI logs are kept for 3 days, then deleted. Want them longer? Point your own Postgres at the platform and keep logs on your own terms.
Put a fleet of AI developers to work
Bring your own keys, drop a .maintainer.yml, and let the loops run — audited end to end. Access is invite-only.