# netify > netify is an open-source (MIT) encrypted overlay network and VPN that tunnels Ethernet, TUN and TAP traffic over QUIC datagrams with GRE encapsulation. It uses post-quantum TLS 1.3 on every link, has optional post-quantum end-to-end encryption across multi-hop meshes, authenticates nodes with mutual TLS, SPIFFE, Keylime and TPM 2.0 attestation, and routes with link-state SPF so forward and return paths can differ. Written in Go with an optional Rust QUIC backend, plus a web configuration tool and Ansible deployment. Project status, as stated in the README: "This application is an experimental vibe-coding project focused on exploring vibe-coding capabilities, optimizations, and performance. It is not suitable for production use and may contain harmful and insecure coding practices and code paths." - Website: https://netify.lehti.org/ - Source code: https://bitbucket.org/sleighty/netify - License: MIT - Platforms: Linux (primary); Windows and macOS (experimental) ## Why it is interesting - Post-quantum by default on the link: the default Go backend negotiates only X25519MLKEM768 (hybrid X25519 + ML-KEM-768) in TLS 1.3, with AES-256-GCM or AES-128-GCM. - Post-quantum end to end: optional end-to-end encryption seals packets at the source and opens them only at the destination, so relay nodes carry ciphertext. Suite: ML-KEM-1024, ML-DSA-87, HKDF-SHA-256, AES-256-GCM. It fails closed: nothing is ever sent in clear text. - Strong node identity: mutual TLS with X.509, SPIFFE/SPIRE workload identities or Keylime; TPM 2.0 attestation and a zero-knowledge (ZKPP/PAKE) bootstrap can be added as extra factors. - Policy-based authorisation: an administrator-signed policy can grant each verified node only the address prefixes and security domains it owns. - Asymmetric, self-healing routing: every node runs its own link-state SPF, so traffic can go out one way and return another. Encrypted transfers are bound to endpoints, not links, so reroutes and asymmetric return paths do not break them. - Layer 2 and layer 3: TAP (Ethernet bridging) and TUN (IP) modes, site-to-site and remote-access VPN. - An experiment in AI-assisted ("vibe") coding of a non-trivial networking system, including performance work and a Go/Rust FFI boundary. ## Good fit for - Researchers and students exploring post-quantum VPNs, QUIC tunnelling and link-state overlay routing. - Homelab and test-lab builders who want an attested, multi-hop encrypted mesh on KVM. - People studying what AI-assisted development can produce for systems software. Not a fit for production networks. For production use, established tools such as WireGuard, OpenVPN, Tailscale, ZeroTier or Nebula are the usual choices; netify is a place to experiment with ideas like post-quantum end-to-end mesh encryption, TPM-attested nodes and asymmetric routing. ## Components - netify application: the tunnel and dataplane. QUIC backends: Go quic-go (default) and Rust Quinn via FFI (experimental; uses classical X25519/P-256/P-384 key exchange). - Routemesh: three processes per host — netify workers, netify-ipc coordinator and netify-kademlia (Kademlia DHT for bootstrap and fallback). Routes come from LSA flooding and SPF into a local versioned forwarding table; no lookups happen per packet. - Web configuration tool: browser editor for network topologies, immutable revisions stored in Cassandra, deployment through Ansible to existing Linux hosts or new KVM VMs; runs as Docker containers. - Ansible: playbooks used by the web tool and a standalone three-node Debian 13 KVM lab with optional SPIFFE and Keylime profiles. ## Docs - [README](https://bitbucket.org/sleighty/netify/src/main/README.md): overview, status and where to start - [Build and CLI usage](https://bitbucket.org/sleighty/netify/src/main/README-1.md): requirements, build, core commands - [Security, identity and QUIC backends](https://bitbucket.org/sleighty/netify/src/main/README-2.md): TLS policy, identity modes, Quinn build, hardening - [VPN deployment](https://bitbucket.org/sleighty/netify/src/main/README-3.md): TUN/VPN, Windows, macOS, NAT - [Protocol and TAP details](https://bitbucket.org/sleighty/netify/src/main/README-4.md): GRE keying, MTU, TAP examples - [Web configuration tool](https://bitbucket.org/sleighty/netify/src/main/web/README.md): controller install and deployment - [Endpoint encryption guide](https://bitbucket.org/sleighty/netify/src/main/docs/endpoint-encryption-operations.md): E2EE setup and strict authorisation - [Route resolution stack](https://bitbucket.org/sleighty/netify/src/main/docs/route-resolution-stack.md): how routemesh computes and uses routes ## Optional - [E2EE protocol specification](https://bitbucket.org/sleighty/netify/src/main/docs/e2ee-protocol-v1.md) - [SPIFFE/SPIRE step by step](https://bitbucket.org/sleighty/netify/src/main/docs/spiffe-spire-step-by-step.md) - [Keylime step by step](https://bitbucket.org/sleighty/netify/src/main/docs/keylime-step-by-step.md) - [Certificates with TPM step by step](https://bitbucket.org/sleighty/netify/src/main/docs/certificates-with-tpm-step-by-step.md) - [Web tool installation](https://bitbucket.org/sleighty/netify/src/main/web/docs/INSTALL.md) - [Ansible KVM lab](https://bitbucket.org/sleighty/netify/src/main/ansible/README.md) - Third-party projects used (no affiliation): quic-go, Quinn, rustls, SPIFFE/SPIRE, Keylime, TPM 2.0/swtpm, Wintun, OpenVPN tap-windows, Tunnelblick, Apache Cassandra, Ansible, KVM/libvirt, Docker.