HazelJSEarly access
HazelJS Cloud
Shared registry. Managed apply. Same Agent OS.
Optional hosted control plane for teams — after local Agent OS already works on your laptop.
Apache 2.0 runtime stays yours. Cloud is a Team SKU, never a requirement.
Registry
DNA packages · versions
Apply
Desired state · environments
Fleet
Running agents · visibility
Local Store remains source of truth
Coming with Cloud
What teams get
Same Agent OS model — hosted when you want shared ops, not a different product.
Shared DNA registry
Promote and version Agent DNA packages across environments when the team is ready.
Managed apply
Hosted desired-state deploy for agents you already define and run locally.
Team visibility
A control-plane view of Running agents — without replacing hazeld on your machine.
Optional adapters
Kubernetes and cloud targets stay adapters. Local Store remains the source of truth.
Today vs later
Local works first. Cloud is optional.
Available now
Local Agent OS
- hazel new agent → hazel apply
- Agents stay Running under hazeld
- DNA, Skillgate, Gatekeeper, HITL on your Node app
- No account required
On the roadmap
HazelJS Cloud
- Shared registry for DNA packages
- Managed deploy for teams
- Optional hosted control plane
- Early access via waitlist
Waitlist
Get early access to Cloud
Be first when hosted registry and managed apply open. Keep shipping locally until then.
Join 9+ developers for early access to HazelJS Cloud
Optional Team SKU — never required to ship agents locally.
Do I need Cloud to use HazelJS?+
No. Local Agent OS is the product path today. Cloud is an optional Team SKU for hosted registry and managed deploy.
What happens if I join the waitlist?+
We email early-access updates when hosted registry and managed deploy open. You can keep building locally in the meantime.
Is Kubernetes required?+
No. Kubernetes is an optional adapter. Correctness does not depend on Cloud or a cluster.