Several bees, one scheduler
One full cycle runs eight phases: buffer, dispatch, transit, acquire, transfer, return, swap, ingest. Below, two bees run those phases against two machines at once, routed by the Hive scheduler. The rail tracks the phase the highlighted bee is in right now. The hardware moves the data; the scheduler decides.
Three rules the design never breaks
Drone vendors will change over the life of the site. These three rules never do.
Data never touches the bee
The Pollen has its own storage, battery, optics, and radio. The drone just carries it, like a truck hauling a locked box. It can't open it, and it never sees what's inside.
Any bee that lifts it, works
No vendor software, no special integration. The mount is bolts and a weight limit. Today it hangs from a drone. Tomorrow it can ride a truck, sit on a pole, or bolt straight onto the machine.
The Hive is permanent
The fiber, the computers, and the ingest shelf go in before the first flight and stay after the last one. The docked cartridges are the storage, and empty slots are the backup buffer if the internet line goes down.
The parts change. The Hive doesn't.
The container goes in first: internet, computers, and a secure site network. It's useful on day one, before a single drone flies.
HSU deployedBackhaul liveProve the two hard parts separately: automated flying on off-the-shelf drone hardware, and the optical link on a simple mast rig. Then show them working together.
Ops proofLink physics proofSealed module v1Move to open drones running open autonomy software. The blossom, the Pollen, and the Hive don't change at all. Only the drones do.
Autonomy layerUniversal dockEventually the machine maker builds this into their own equipment. When they do, they build to the published Pollen interface, on the same blossoms, into the same Hive.
Published interface specThe scheduler is the product on top
The scheduler decides which bee goes where, and when. It watches every machine's buffer, every bee's battery, and every blossom's health, and plans pickups all day, like a delivery route that never stops updating. Drones come and go over the years. The scheduler and its data stay.
Site state
How full each machine's buffer is, where the machines will pause next, whether each lid works, the weather, each bee's battery, and how many empty cartridges are on the shelf.
Assignment
The fullest machine gets the readiest bee. Each bee flies at its own altitude so they never cross paths. A broken lid gets skipped instead of found mid-flight. Every decision is written to the log.
Adapter per airframe
The scheduler speaks one language. Each drone system plugs in through a small adapter, and switching drone vendors means switching the adapter. The decisions and the data stay put.
The building the data lands in
The Hive is a shipping container that goes in before the first flight. One end is the equipment room: the carrier handoff, a 100 Gbps switch, the Pollen ingest shelf, an edge computer, and a UPS, all in one 42U rack. The other end is a working site office with four desks. The ingest bay is a slot in the wall, so cartridge swaps never go through the office.
One clear handoff
The 100 Gbps line is a carrier circuit, and every carrier circuit needs a demarcation point: the exact spot where the carrier's gear ends and ours begins. One panel, one test point. When the line has a problem, you know in minutes whose side it is on. It is also where the circuit gets grounded and surge protected. The panel is sized for two circuits from day one: a second line or a backup path is the cheapest upgrade the Hive will ever get, and the space costs nothing now.
A private line, not internet
An EPL is a point-to-point line that behaves like one very long Ethernet cable from the Hive to the datacenter. Fixed bandwidth, no sharing, no public internet anywhere in the path. At hundreds of terabytes a day you need guaranteed throughput, and the security story stays one sentence long: machine, sealed cartridge, private line, training cluster. The data never touches the internet.
Two destinations
The GPU cluster gets the hot data the models train on. S3 storage gets everything, cheap and forever. A cartridge at the Hive is only wiped and reused after the far end confirms the data is safely written, and safely written ultimately means it is in S3. The Hive only ever holds a few days of data. It is a staging point, not a warehouse.
The drawing reads left to right the same way the data moves: bees drop Pollen in the wall bay, the cartridges plug into the rack and become the storage, the rack hands the traffic to the demarc, and the private line carries it to the two far ends. The amber path is the same color as the beam in the animations on purpose. It is the same data, still moving, on glass now instead of air.
WIRELESS FIBER - A FIBER PATCH CORD MADE OF LIGHT
Wireless fiber is a data link made of light. The same small lasers used inside datacenters send 10 to 100 Gbps through open air, both directions at once. It ends wherever the data is, not wherever you managed to dig a trench.
Light, not radio
No licenses, no crowded radio bands, no interference from all the other radios on site. Big electric machines don't bother it. And it's hard to snoop: you'd have to hover inside a 14-foot cone directly above a working machine.
Wide cone, short gap
Long-range laser links need pencil-thin beams and motorized aiming. This makes the opposite trade: the distance is only 15 feet, so the beam can be a wide 50 degree cone instead. If the other end is anywhere in that cone, the link works. That's why a hovering drone can hold it.
Layer 1, nothing more
The link is just a pipe. It has no network address, doesn't open the traffic, and passes encrypted data straight through. It can't read what it carries. Same idea as Rule 01: nothing in the middle ever sees the data.
The honest downsides: it needs a clear line of sight, and lenses hate dirt and rain. The 15-foot gap is short enough that weather barely matters, the lid keeps the lens covered except during a pickup, and the machine buffers hold days of data for when the bees can't fly.
Why the numbers work
The 50° cone gives the drone a 7-foot circle to hover in. Modern drones hold position about ten times tighter than that, so hitting it is easy. Each machine makes a terabyte an hour. A bee visits every five or six hours, picks up about 5 TB, and one bee can cover six or seven busy machines. At the Hive, the docked cartridges are the storage itself, and the 100 Gbps line carries everything to the GPU cluster with room to spare. Nothing is erased until the far end confirms. The 100 Gbps head fits in the same cartridge and empties a full shift in 13 minutes.
Bees make roughly 5 TB pickups, each flying at its own altitude so they never cross paths. At full size, six pads and six bees cover about 40 busy machines making around 640 TB a day, and the 100 Gbps line still carries all of it. Extra slots on a machine cover bad weather. Extra slots on the shelf cover an internet outage. Extra pads cover a broken drone. Every backup on site is the same thing: a spare slot.
How many bees?
Set your site below. The calculator works out drones, pads, cartridges, Hives, and the yearly cost against doing it by hand. The number people always guess wrong: drones per machine is a fraction.
Your site
What manual handling really costs
The alternative to bees is people: a tech drives to each machine, stops it, swaps the drive, and either carries it back or mails it. Set your labor numbers below. The result is usually a surprise, and the surprise is not the wages. It is the stoppages.