Follow one request from source code to a finished response.
Hyjal joins compilation, component storage, routing, fresh execution, and metering into one legible path.
One continuous path. No hidden warm fleet.
The request lifecycle describes the real platform boundary from authored source through completed work.
-
BuildAssemblyLine compiles
Source becomes a portable WebAssembly component.
-
StoreThe artifact is available
The platform retains the execution-ready component.
-
RouteA request arrives
Hyjal selects the component needed for the work.
-
RunAfterburner executes
A fresh instance handles the request and is discarded.
Every handoff exists to move the request forward—not to preserve idle infrastructure.
Read the lifecycle as a request trace.
The trace makes the operating model concrete without turning the page into terminal theater.
- ArtifactComponent selected
The runtime receives the portable unit produced by AssemblyLine.
Ready - InstanceFresh execution begins
Afterburner creates an isolated runtime boundary.
Active - ResponseWork completes
The result leaves and the instance boundary closes.
Done
The request is the through-line; the infrastructure exists only to complete it.
Trace your own workload through Hyjal.
Start building now, or bring a request path to a technical walkthrough.