From commit to live.
Automatically.
DeployForge turns shipping an application to production into one command — analyzing your stack, deploying the frontend to Vercel and the backend to Render, wiring environment variables and CORS, then verifying everything is live.
$ deployforge ✓ GitHub repository detected aasz253/my-app ✓ Project detected Next.js + FastAPI ✓ Security scan completed 0 secrets ✓ Backend deployed → Render https://api.my-app.onrender.com ✓ Frontend env wired NEXT_PUBLIC_API_URL ✓ Frontend deployed → Vercel https://my-app.vercel.app ✓ Backend CORS configured https://my-app.vercel.app ✓ Deployments verified HTTP 200 🚀 Application is LIVE https://my-app.vercel.app
One command. Six stages.
Everything between "it's on GitHub" and "it's live on the internet" — automated and safe.
Analyze
DeployForge reads your project and recognizes the topology — Next.js, Vite, FastAPI, Express and more, even inside monorepos.
Plan
A deployment plan routes the frontend to Vercel and the backend to Render, choosing the plan you asked for.
Secure
A preflight secret scan sweeps your files and blocks the deployment before a credential could ever ship.
Deploy
Backend first, then frontend — deployed straight from your GitHub repository through the official provider APIs.
Wire
NEXT_PUBLIC_API_URL points at the live backend and FRONTEND_URL opens CORS on it — no copy-paste.
Verify
Deployments are polled to ready and every URL is health-checked before the live report is printed.
Built for the daily deploy
The wiring you'd otherwise do by hand, folded into one habit.
One command per release
In a GitHub-backed folder, deployforge is the whole pipeline. No dashboards, no click-dancing.
Reads your topology
Frontend-only, backend-only, full-stack or monorepo — it detects what you have and deploys exactly that.
Security-first by default
The preflight scanner blocks deployments carrying leaked credentials before they reach production.
Partial-failure safety
If one service fails, the services already deployed stay live — never a half-destroyed rollout.
Cross-platform
Linux, macOS and Windows. Same command, same output, anywhere.
Credentials protected
Provider tokens live in your OS keyring, never in your project. Logs store fingerprints, not values.
PushForge-native
DeployForge is the second stage of the PushForge workflow — pushforge ships code, deployforge ships it to production.
Credentials never reach production.
Before anything deploys, DeployForge scans for API keys, private keys, database credentials and high-entropy tokens. If something looks live, the deployment is blocked and the value is never displayed — only a fingerprint is recorded.
⚠ Potential secret detected ✗ GitHub token api/client.py:88 ✗ AWS key config.py:12 Deployment blocked to protect your credentials. Remove the secrets and run 'deployforge' again.
Blocked deployments exit with a clear code — safe for CI
Tokens live in your OS keyring, never committed
Values never shown — at most a SHA-256 fingerprint
Official Vercel & Render APIs only — nothing else is contacted
Available on every OS
Python 3.11+, git and a GitHub-backed project are all you need.
# Debian / Ubuntu
sudo apt install pipx
pipx install deployforge
# Fedora / Arch or any distribution
pipx install deployforge
# one-time path setup (adds ~/.local/bin)
pipx ensurepathcd ~/projects/my-app
deployforge --version # ✓ works from any folder
deployforge --dry-run # preview the whole rollout
deployforge status # what is live right nowbrew install pipx
pipx install deployforge
# or without Homebrew, using pip
pip3 install --user deployforge# PyPI ships a universal wheel — no compilation.
# Works identically on Intel and Apple Silicon.
pipx install deployforge
deployforge version# install with pip (remember to enable "Add python.exe to PATH")
py -m pip install --user deployforge
# or with pipx
pipx install deployforgecd C:\Users\you\my-app
deployforge --help
deployforge --dry-run# Store tokens in your OS keyring (never in the project)
deployforge config --set vercel_token
deployforge config --set render_api_key
# or export them and DeployForge picks them up:
export VERCEL_TOKEN=...
export RENDER_API_KEY=...
# Verify readiness any time
deployforge doctorFrom local to live in two commands
PushForge ships your code to GitHub. DeployForge ships it to production.
# 1. Push your code to GitHub
pushforge # detect → secure → repo → commit → push
# 2. Ship it to production
deployforge # analyze → plan → deploy → wire → verify
# 3. Check what's reachable right now
deployforge status
deployforge verify # health-check every live URLThe whole surface of DeployForge
Small enough to remember, deep enough to automate production.
| Command | What it does |
|---|---|
deployforge | Full automated deployment — analyze → deploy → verify |
deployforge analyze | Show detected architecture and the deployment plan |
deployforge deploy --dry-run | Preview the entire rollout without touching anything |
deployforge init | Create .deployforge/config.yml for a project |
deployforge status | Show project, repository, and deployment status |
deployforge verify | Check every deployed URL is reachable and healthy |
deployforge security | Run the preflight secret scan independently |
deployforge doctor | Diagnose the environment and provider readiness |
deployforge config --set key | Store provider tokens in your OS keyring |
deployforge logs | Show recent deployment records |
From one command to a platform
The MVP ships without AI. These additions slot right onto the same core.
Auto env-wiring · shipped
NEXT_PUBLIC_API_URL and FRONTEND_URL set for you.
CORS auto-setup · shipped
Backend origins configured from the live frontend URL.
PushForge handoff · shipped
The natural second stage of the PushForge workflow.
deployforge metrics
Revenue-grade analytics from Vercel & Render in one table.
deployforge rollback
One-command rollback to a previous healthy deployment.
deployforge ai
LLM-assisted plan explanations and deployment summaries.
Ship in one command.
pipx install deployforge — then watch production light up.