The platform
Eight components, one control plane
Each of these runs our own products in production today. Below: what every one of them does, whether it is live, the command or endpoint you reach it with, and how the pieces fit together.
Component matrix
What it does, its status, its command or endpoint, and where it answers.
| Component | What it does | Status | CLI / API | Live |
|---|---|---|---|---|
| forge-control | Builds, deploys, secrets and DNS for every app on the fleet. | Live | forge app-deploy | Open ↗ |
| forge-git | Self-hosted Gitea plus fgit, the merge CLI the whole federation pushes through. | Live | fgit pr merge | Open ↗ |
| forge-auth | Sign-in, API keys, organizations and entitlements for your apps. | Live | forge login | Open ↗ |
| packr | The private package registry every deploy installs its dependencies from. | Live | npm config set @blueforge-studio:registry https://api.packr.blueforge.studio | Open ↗ |
| gateway | Multi-tenant AI gateway: one endpoint, per-tenant key swap, usage by org. | Live | POST /v1/proxy | Open ↗ |
| error tracker | Self-hosted error tracking, proxied from every site on the fleet. | Live | POST /api/events | |
| marketplace | Signed, versioned agent-stream templates with Stripe test checkout live. | Beta | POST /v1/publish | Open ↗ |
| promotion site | A catalog site per product, filled from its own deploys. | Beta | Open → |
How they compose
A push lands on forge-git; forge-control builds and deploys it; forge-auth decides who may; packr serves the packages the build installs; the promotion site publishes the result as your catalog. The gateway, the error tracker and the marketplace attach to that spine.
Quickstart
Three commands from an empty terminal to a deployed app:
npm i -g @blueforge-studio/forge
forge login
forge app-deployQuestions
Is BlueForge self-hosted?
Yes — this is our own production fleet: forge-git is Gitea, forge-control builds and deploys, and every host runs behind our own Caddy. The docs cover how to integrate with it, and each component page says plainly what is live and what is still closing in.
Do I have to move my code off GitHub?
No. The registry, the sidecars and the public packages work from any CI — GitHub Actions included. Keep your remote, validate your sidecars in your pipeline, and register each deploy with POST /api/deployments using a forge-auth org key.
Am I locked in?
No. Your code stays in git, your sidecars are two YAML files in your repo, and every service speaks HTTP with documented endpoints. The catalog fills itself from your deploys — stop deploying and it goes quiet; nothing else breaks.