Documentation

VIGIL-MESH is an end-to-end encrypted, all-QUIC private mesh in which every network behaves like a local broadcast domain: broadcast and IP multicast cross the tunnel (mDNS, SSDP, LAN games, business UDP) just as they would on a switch. The relay infrastructure — the vigies — is operated by vigil.design, yet anyone can deploy their own private vigie: it self-configures and only ever serves its own workspace.

Where to start

The documentation can be read in any order, but each article stands on its own and answers a specific question. Start with how the mesh network works if you are new to VIGIL-MESH, then explore local broadcast, security, self-hosting a vigie and performance.

How the mesh network works

The three roles (the node, the vigie, the controller), the immediate connection through a relay followed by seamless migration to the direct path, and the principle of zero inbound ports on the node side. -> /en/docs/reseau-mesh

L2 broadcast and encrypted multicast

Your devices discover and talk to each other as if they were plugged into the same switch: mDNS, SSDP, LAN games and business UDP cross the mesh, multicast included and encrypted. -> /en/docs/l2-multicast

Deploy your private vigie

Your relay, on your server, for your traffic only: when it is useful, how it self-configures against the controller, and why it stays blind to your data. -> /en/docs/vigie-privee

Performance: measurements and goals

What is actually measured on the bench, what is demonstrated, and what remains a design goal — every figure carries its truth badge. -> /en/docs/performances

Security model

A single end-to-end encryption layer, relays that are structurally blind, a controller that never sees the content of your flows. -> /en/docs/securite

Recommended paths

I am just discovering it

Read How the mesh network works first to understand the roles and the immediate connection, then L2 broadcast and encrypted multicast to see how your devices find one another on their own.

I am evaluating it for my company

Focus on L2 broadcast and encrypted multicast for business use cases, on the Security model for compliance, then on Deploy your private vigie to keep the relay in-house.

I am technical

Go through everything in order: mesh network, L2 broadcast and multicast, private vigie, performance, then the security model — each page builds on the previous one.