Deploys
Build source apps with Railpack and BuildKit, or run prebuilt Docker images when CI already owns the image.
Bring your VPS. Keep control.
Forge Cloud connects to your VPS through a signed Agent, then keeps projects, deployments, databases, domains, secrets, transactional email, backups, and access boundaries in one tenant control room.
Workspace → Servers → Connect serverForge generates a short-lived, server-specific installation command after you create the registration. The command installs only Forge Agent on the selected VPS.
Operating surface
Forge is not a generic dashboard. It coordinates deployments, databases, DNS, secrets, transactional email, and qualified recovery operations on the servers your workspace connects.
Build source apps with Railpack and BuildKit, or run prebuilt Docker images when CI already owns the image.
Project-scoped Postgres and Redis with generated runtime URLs, backup metadata, and controlled public access.
Generated service domains, custom domains, exact DNS verification, and managed HTTPS routing.
Encrypted environment variables, file imports, Doppler connections, and project-aware variable suggestions.
Project sender identities, per-domain DKIM, SMTP submission, STARTTLS enforcement, and transactional API keys.
Encrypted server and off-site backups, integrity evidence, and restore status where the target reports a qualified recovery capability.
Deploy surface
Forge Cloud keeps the app, database, worker, domain, and secret controls in one project. Build from source with Railpack, run a prebuilt Docker image, or ship a static site without changing platforms.
Product surface
The public site can be bold. The app itself should stay dense, calm, and built for repeated work: projects first, service state visible, dangerous actions behind clear controls.
Full-stack deployment surface for a production application.
projectmain branch, 2 hours ago
main branch, 6 hours ago
billing-v2, 4 minutes ago
snapshot sealed 04:12 UTC
Migration path
Move a Railway project into your Forge workspace without rebuilding the stack by hand. Services, variables, databases, and domains arrive as project resources you can inspect before deploying to a connected server.
Use a Railway personal API token to inspect projects, environments, services, variables, and deployment settings.
Select the target environment and services, skip platform-only values, and decide how databases should be recreated or imported.
Forge creates the project, maps service variables, links fresh database credentials, imports supported domains, and can queue deploys.
Railway project
production env
web
Next.js
api
Node
postgres
DB
Forge stack
connected VPS
web
deployed
api
env linked
postgres
managed
Included in the import
Capability ledger
GitHub App or token source access, webhooks, branch selection, root directories, release commands, and health-gated promotion.
Run prebuilt images directly when your CI already publishes containers, including private images the selected server is authorized to pull.
Project-scoped databases with runtime credentials, generated variables, data tools, and target-qualified recovery actions.
Generated service hostnames, custom domains, exact DNS verification, and managed TLS.
Encrypted local variables, env/json/yaml import, optional Doppler connections, and safe variable reveal flows.
Project-owned domains, sender identities, DKIM keys, SMTP config, API keys, and STARTTLS enforcement.
Encrypted server and off-site backup options, integrity evidence, restore status, and project data migration workflows.
Workspace-owned server registration, signed Agent jobs, health reporting, bounded logs, and explicit workload placement.
Production model
Customers connect the servers they control without operating the Forge Cloud control plane. Workspace permissions and signed Agent jobs keep each tenant's resources separate.