Inside hive
hive is a thin portal, on purpose. It boots first, binds before the workloads are ready, and renders the whole dashboard by aggregating each daemon's API, so you always have an honest view of the stack.
What happens when you open it
- 01
Boots first
hive starts with your device under doctor's supervision and binds its socket before any workload is confirmed healthy, so the portal is reachable the moment you power on.
- 02
Shows honest readiness
Open it mid-startup and you get the buzzing screen: one bee per service, from an empty cell (starting) to a bee in flight (active). It dismisses itself the moment the fleet is ready.
- 03
Aggregates the daemons
hive renders the dashboard by fetching each daemon's HTTP API over local loopback and passing your session through. It holds no storage client of its own.
- 04
Degrades one panel, not the page
If a service is down, its panel says unreachable while the rest keeps working, and it recovers on its own once doctor brings the service back.
Yours only, and stores nothing.
hive binds to 127.0.0.1, so nothing off your device can reach it. Your browser talks to hive alone; hive's server fetches everything else over local loopback on your behalf and passes your session straight through without storing anything. Signing in creates your Deeplake credential on your machine, managed by honeycomb, not by the portal.
See securityscoped to project · api-gateway · widen to share
Under the hood
- portal
- 127.0.0.1:3853
- model
- server-side proxy that aggregates each daemon API
- boot
- OS service at startup, watched by doctor
- binding
- loopback only
- stores
- nothing, session pass-through
Common questions
How is the dashboard up before the daemons are?
hive binds its socket before any workload is confirmed healthy. Open it mid-startup and you get a readiness screen, one bee per service, that dismisses itself the moment the fleet is ready.
Why does one broken service not break the page?
hive holds no storage client of its own. It renders by aggregating each daemon's API, so a down service shows unreachable on its panel while the rest keeps working, recovering once doctor restarts it.
Does hive store my session or credentials?
No. hive passes your session through to the services that own your data and stores nothing. Signing in creates your Deeplake credential on your machine, managed by honeycomb.
One honest view of the whole stack.
hive installs with the rest of the stack and opens itself when setup finishes.
Windows (PowerShell): irm https://get.theapiary.sh/install.ps1 | iex
Download