FORGE

Building at a
hackathon? Ship.
We will handle deploys.

One config file. One push. Forge runs your CI on your machine, deploys the backend to Railway, and ships the frontend to Vercel — automatically, every time.

Get started free Read the docs
terminal
$pip install forge-cicd
Collecting forge-cicd...
✓ Successfully installed forge-cicd
How it works

Three layers. One command.

Y
Your Machine
Docker-powered CI runner
R
Railway
Backend deployment
V
Vercel
Frontend delivery
01
Push code
git push triggers the GitHub webhook to Forge
02
CI runs locally
Your Docker container runs install & test commands
03
Backend deploys
Railway picks up the commit and deploys your API
04
Frontend ships
Vercel builds and delivers your UI globally
Features

Everything you need.
Nothing you don't.

Spec-driven configuration

One forge.yaml describes your entire stack. No YAML sprawl, no hidden magic — just a clean spec that version-controls with your code.

Local Docker CI

Your machine runs CI inside isolated Docker containers. No credits, no queues — runs start instantly when you push.

Multi-platform deploys

Railway for long-running backends, Vercel for frontend statics. Best-in-class platforms, wired together automatically.

GitHub-native checks

Every push gets a GitHub check run. Pass or fail, you see it inline in your PR — no extra dashboards to check.

Zero cold-start friction

forge init → forge login → forge create. You're deployed before the hackathon judges open their laptops.

CLI-first workflow

Everything is a command. Logs, status, deployment, credentials — all in your terminal, all scriptable.

start now

Hackathon clock is ticking. Ship already.

Join teams who stopped fighting devops and started winning hackathons.

Start for free Read the docs