01
Preview deploys
Every change can get its own URL so you can review before production traffic touches it.
DeploymentsBuild workflowRollback-ready
From sourceto live URLwithout drama.
Forgeon turns code into production releases with source analysis, build automation, immutable artifacts, runtime orchestration, domains, health checks, logs, and rollback safety.
Launch runway
production / app-web / deploy-v42
v42
Deployment sequence
source → build → runtime → edge
01
readyCode received
Git, upload, template, CLI, or image
02
doneProject detected
Framework, runtime, ports, commands
03
runningArtifact created
Container image, static output, or bundle
04
queuedService scheduled
Region, compute profile, env, replicas
05
armedTraffic connected
Domain, SSL, routing, health checks
Build
1m 04s
Health
passing
Region
sgp
Release
v42
Workflow engine
A deployment is not one button. It is a chain of decisions.
Forgeon coordinates source intake, framework detection, build execution, artifact storage, runtime scheduling, domain routing, SSL, health checks, and rollback targets as one connected release workflow.
source-awareartifact-basedhealth-gatedrollback-ready
01
Source intake
Git / Upload / CLI / Image
4 paths
02
Build pipeline
Detect, install, build, package
cached
03
Artifact registry
Immutable release output
v42
04
Runtime scheduler
Compute, env, replicas
auto
05
Edge router
Domain, SSL, routing
live
06
Rollback target
Previous healthy release
ready
Release timeline
Every release leaves a trail.
A clean deployment platform should not feel like magic smoke. Every important step is visible, timestamped, and connected to the final URL your users open.
00:00
Deployment requested
Forgeon receives the source and creates a deployment intent with project, tenant, environment, and trigger metadata.
00:12
Source analyzed
The platform detects framework, runtime, build command, output directory, exposed port, and required runtime behavior.
01:04
Build completed
A versioned artifact is produced and attached to the deployment so the release can be reproduced, promoted, or rolled back.
01:28
Runtime started
Forgeon schedules the service, injects runtime env vars, connects logs, and waits for healthy readiness signals.
01:41
Live URL ready
Traffic is routed to the healthy deployment with domain, SSL, preview URL, and rollback target available.
deployment logs
[source] repository synchronized
[detect] nextjs app router detected
[build] installing dependencies
[build] creating optimized production build
[artifact] uploaded image forgeon/app:v42
[runtime] container started on port 3000
[edge] ssl certificate active
[health] deployment is ready
[source] repository synchronized
[detect] nextjs app router detected
[build] installing dependencies
[build] creating optimized production build
[artifact] uploaded image forgeon/app:v42
[runtime] container started on port 3000
[edge] ssl certificate active
[health] deployment is ready
[source] repository synchronized
[detect] nextjs app router detected
[build] installing dependencies
[build] creating optimized production build
[artifact] uploaded image forgeon/app:v42
[runtime] container started on port 3000
[edge] ssl certificate active
[health] deployment is ready
Real-time visibility
Logs should feel alive, not buried.
Watch build output, runtime events, health checks, and routing changes as the deployment moves from queue to live URL.
Build logs
Follow dependency install, compile output, and build failure reasons.
Runtime logs
Inspect boot events, container output, health signals, and crash loops.
Release modes
Ship carefully when it matters. Move fast when it does not.
02
Production promotion
Promote a known-good build to production instead of rebuilding from scratch and praying twice.
03
Rollback safety
If a deploy goes sideways, return traffic to the previous healthy artifact quickly.
Health-gated traffic
“Built” is not the same as “safe to receive traffic.”
A deployment should only become live after the runtime starts, health checks pass, routing is ready, and rollback metadata is in place.
1
passedBuild artifact exists
2
passedRuntime container booted
3
passedPort responded
4
passedDomain route attached
5
passedSSL certificate active
6
readyPrevious release retained
Deployments
Deploy like the platform knows what can go wrong.
Build from source, produce immutable releases, stream logs, verify health, attach domains, and keep rollback close enough to save the day.
forgeon deploy --source .