Ingress
Route the request directly to runnable application code.
The platform identifies the workload and creates execution without a container scheduler in the request path.
Request → runtimeProduct APIs
Every API request gets exactly the runtime it needs.
Serve customer-facing APIs through fresh, isolated WebAssembly execution that arrives with the request and disappears after the response.
The request path stays short. The operating burden gets shorter.
Hyjal removes the warm fleet from API delivery without asking the application to give up a normal request and response model.
Isolation
Keep one customer request separate from the next.
Every request receives a fresh instance with no application memory inherited from prior work.
Fresh by defaultDemand
Let API capacity match the traffic that actually arrives.
Concurrency expands with incoming requests and returns to zero without a warm pool or autoscaling threshold.
0 → demandFrom incoming request to released capacity.
The API runtime completes one bounded lifecycle for every request, making isolation, metering, and release part of normal execution.
-
RouteRequest enters
Hyjal routes the request to the deployed WebAssembly component.
-
StartRuntime appears
Afterburner creates a fresh isolated instance for the work.
-
HandleApplication responds
Your normal request handler runs inside the component.
-
MeasureExecution is metered
Consumption reflects the work performed for the request.
-
ReleaseCapacity returns to zero
The instance ends when the response is complete.
API infrastructure that starts with the request and ends with it.
Bring the endpoint. Leave the warm fleet behind.
Start building in the Hyjal console, or walk through an existing API workload with the team.