Inside queen
queen is the control plane above every machine running the stack. It is built on a simple rule: your orchestrator holds custody of your credential, queen coordinates, and it never reads your memory. Coming soon.
How the fleet stays coordinated
- 01
Presence
Each daemon sends a cheap heartbeat on a fixed interval, plus a richer status diff only on change, with TTL reaping so dead ephemeral agents never pile up in the fleet view.
- 02
Enrollment
Every agent, even an ephemeral sub-agent, gets its own attributable, revocable identity. Warm hosts vouch for their children; cold hosts exchange a short-lived join token for a per-agent credential. No shared forever-key.
- 03
Signed commands
One primary authority signs every command against a pinned public key and brokers credentials. If the authority goes down, workers degrade to autonomous, not to dead.
- 04
Recovery and revocation
Revoking a device and rotating the Deeplake credential are two honest, separate steps. Lose every custodian and the answer is a written re-link path, never a hidden backdoor.
A control plane with a hard boundary.
queen's coordination state lives behind an edge API and holds only what it needs: identity, devices, fleets, enrollment, presence, leases, and encrypted blob metadata. No memory content, no prompts, no session text, no plaintext credentials. Presence never writes into your memory dataset, and idle daemons never poll it for coordination work.
See the whole stackscoped to project · api-gateway · widen to share
Under the hood
- model
- orchestrator-custodian
- credential custody
- your orchestrator, not the cloud
- presence
- heartbeat plus status-on-change, TTL reaped
- identity
- per-agent, revocable, signed against a pinned key
- reads memory
- never
Common questions
What is the orchestrator-custodian model?
Your long-lived orchestrator holds custody of the Deeplake credential, not the cloud. queen coordinates identity, presence, and encrypted blobs it cannot decrypt. Workers stay disposable.
How does a new device enroll without two machines open?
Approve it in the cloud, and an existing custodian device finishes the cryptographic rewrap next time it is online. A headless server enrolls with a short-lived join token that cannot read or decrypt anything.
What is the control plane allowed to hold?
Only coordination state: identity, devices, fleets, enrollment, presence, leases, and encrypted blob metadata. No memory content, prompts, session text, or plaintext credentials.
The fleet starts with the machines you run today.
Install the stack now, and those machines become the fleet queen will observe and steer when the cloud layer ships.
Windows (PowerShell): irm https://get.theapiary.sh/install.ps1 | iex
Get the stack