Build Swarm v3
Connecting...
Drones Online
--
Total Cores
--
Queue Depth
--
Received
--
Blocked
--
Active Assignments
0
No active assignments
Success Rate
--
Avg Build
--
Total Builds
--
Failed
--
Build Time
--
0 / 0 packages
0%
Completed 0
Building 0
Queued 0
Blocked 0
Queue Depth Over Time
Build Rate (per minute)
Fleet CPU Utilization
--%
avg across fleet
Control Panel
Hardcoded IPs in every config
Adding a drone meant editing files on every node. One typo bricked the cluster.
Zero observability
No health checks, no metrics, no idea if a drone was alive or stuck.
Gateway centralized routing
Hub-and-spoke was cleaner but the gateway was a single point of failure.
State lived in memory
Crash the orchestrator, lose everything. Config drift ate 70% of debug time.
SQLite-backed control plane
Every state change persisted. Restart the service, pick up exactly where you left off.
Auto-discovery + circuit breaker
Drones register themselves. Unhealthy nodes get fenced automatically.
Needed 0
Delegated 0
Received 0
Blocked 0
| Package | Status | Assigned To | Failures |
|---|---|---|---|
| No queue data | |||
Avg Build Time
--
Success Rate
--
Total Builds
--
Build Duration Distribution
Drone Performance
| Package | Drone | Status | Duration | Time |
|---|---|---|---|---|
| No history data | ||||
| # | Time | Source | Type | Summary | Latency | Status | |
|---|---|---|---|---|---|---|---|
| No protocol data — waiting for traffic... | |||||||
Select a packet to inspect
SQL Explorer
Tables
Activity Feed
0