Beta — the 50-user cohort has not opened
Forge Cloud Dev
Development environments that ship with your agents
The escape hatch from local-vibe-coding: your repos, secrets and services in declared workspaces on Docker or Hetzner Cloud, with agents working inside them rather than beside them.
What it does
Every claim below names the workspace package that implements it, so it can be checked against code rather than taken on trust.
Workspaces
A resource model and state machine for development environments — created, started, stopped, destroyed, with the transitions enforced rather than assumed.
@forge/workspace
Manifests
Declare a workspace once. The manifest is parsed and validated up front, so a bad environment fails before anything is provisioned.
@forge/manifest
Providers
One stable interface over local Docker and Hetzner Cloud. The same manifest runs on a laptop and on a cloud box.
@forge/provider
Production mirrors
Mirror production data into a development workspace under an explicit lifecycle, rather than passing dumps around.
@forge/mirror
Agent slots
Agents run inside a Docker workspace with the same tools a developer has, rather than bolted on beside it.
@forge/agent-host
Volume backups
On-demand backups of a workspace's data volumes with retention: an rsync to a Storage Box on Hetzner, a tarball on Docker.
@forge/volumes
One of several
Forge Cloud Dev is where code gets written. The rest of the platform builds it, ships it, signs into it and watches it — each piece a product in its own right, and each one a link that was checked by hand rather than assumed.
- forge-controlBeta
Mission Control Dashboard
Deploys and operates this product. Host assignment, compose, secrets and DNS for every Forge app live there rather than here — including the roll that put this page in front of you.
- forge-gitBeta
Self-Hosted Git Platform
Hosts this repository and runs its CI. Every image the control plane deploys is built by a forge-git pipeline on a merge to main.
- forge-authBeta
Centralised identity for the platform
The identity provider a workspace authenticates against — one set of OAuth credentials shared across every Forge app instead of per-app auth wiring.
Signed, versioned templates for Forge
Where the templates a workspace is created from are published and bought. The @forge/templates and @forge/marketplace-client packages in this repo are the client half.
- forge-hostingIn Development
Git-Push Deployments
Takes an application from a git push to a running container. A sibling rather than a dependency: Forge Cloud Dev is where the code is written, forge-hosting is where the result runs.
Not wired into a workspace today.
- forge-error-trackerIn Development
Error Tracking & Uptime
Watches what happens after a deploy. Not wired into a workspace today — listed because it is the other half of the loop, not because this repo calls it.
Not wired into a workspace today.
- forge-bizBeta
The business plane
The same mission engine — objective, work packages, agents, verdict — pointed at business work instead of source code. Shares the model this repo runs missions on.
Not wired into a workspace today.
How it compares
Each of these names what the other product does better, and carries the date its pricing was last checked by a human.
Be in the first fifty
The beta cohort is capped at fifty and has not opened. Leave an address and you will hear once, when it does.