Queen scheduler
Orchestration.
Decides where workloads run, manages placement, handles failover. No manual intervention required.
Queen scheduler
Constraints first. Placement second.
Region and isolation requirements narrow the candidate set before a workload receives its execution host.
node-anode-bnode-cnode-dPlacement logic
Request to running. Milliseconds.
Request
A deployment manifest hits the Hives API. Queen parses runtime preference, region affinity, resource limits, and scheduling constraints.
Evaluate
The placement engine scores every available node: capacity, proximity, load, cost, and compliance zone. Constraints are hard. Preferences are soft.
Route
Queen selects the optimal node and reserves resources atomically. If unavailable, the next-best candidate is chosen within the same evaluation pass.
Deploy
Nectar on the target node receives the compiled module, restores from snapshot, and begins serving traffic. Health checks confirm liveness within 200ms.
Global presence
15 regions.
One scheduler.
Queen places workloads where your users are. Automatic failover between regions. Zero configuration.
Let Queen decide.
Automatic placement. Automatic failover. You ship code.