Architecture

Stranola is designed so that a deployment becomes faster at As you add machines, instead of slowing down.

Vocabulary

• NetEdge — the web server you're using right now: the orchestrator. Manage your machine fleet, save images and recipes, and control the It starts PXE/DHCP and tells netdd when and where to run.
• netdd — the transfer engine. A complementary binary that NetEdge is executed on the source machine (the master) and on each client; it is who performs block-level reading, compression, and distribution peer-to-peer transfer of a disk image.
• Recipe — a saved set of netdd parameters: compression, chunk size, transport, what to do when a client disconnects, etc. You set up a recipe once and reuse it for every deployment that requires it behave the same way. See Recipes.
• Deployment — a specific execution: a recipe applied to a set of a specific set of nodes, right now. NetEdge starts netdd on the master and tracks each client's progress, speed, and health until Finish. See Deployments.

Real P2P Swarm

Each machine that receives data redistributes it to the others. The source sends each block only once; the more machines that join in, the sooner it finishes the entire group.

        ┌─────────┐
        │ origen  │  envía cada bloque una vez
        └────┬────┘
             │
   ┌─────────┼─────────┐
   ▼         ▼         ▼
 ┌────┐   ┌────┐   ┌────┐
 │ PC │◄─►│ PC │◄─►│ PC │   los peers se intercambian bloques entre sí
 └────┘   └────┘   └────┘

Large-Scale Hybrid Multicast

In large deployments, a single broadcast feeds the entire network. The Error correction restores lost data without retransmissions, and P2P It acts as a safety net. It's optional—pure P2P is still the default mode.

Live View

Each deployment continuously reports its status while it is running — speed of data transfer, progress per node, and link health — so you always know exactly how a clone is progressing, not just whether it's finished. See Deployments.