Latency
If two devices are in the same city there is no reason for traffic to travel to a server on another continent and back. A direct connection shortens the path.
// NIJITECH PRODUCT · NETWORKING
Lattix
Devices connect directly, without passing through a central server.
Lattix is a zero-configuration, end-to-end encrypted peer-to-peer VPN. Written in Rust, with no server sitting in the middle of the traffic.
Product site:lattix.network
In short
Lattix is a peer-to-peer VPN that connects devices to each other without routing them through a central server. The connection is end-to-end encrypted and needs no configuration file editing. It is developed as open source.
Devices connect directly, without passing through a central server.
P2P
direct connection
E2E
end-to-end encryption
Rust
implementation
Açık
source code
The source code is developed openly on GitHub.
// WHY PEER-TO-PEER
The server in the middle is a single point of failure.
In a classic VPN all traffic passes through a central server. That server is at once a bottleneck, a source of latency and the single dependency of availability.
Bandwidth
A central server carries every user’s traffic and its capacity is shared. A peer-to-peer connection has no such shared ceiling.
Dependency
When the server in between goes down, a classic VPN stops. If devices are connected directly, that dependency disappears.
Every one of these steps runs on the same backbone: the niji core pipeline →
// SETUP AND SECURITY
Without editing a configuration file.
The longest part of setting up a VPN is usually configuration: key generation, address block selection, routing rules. Lattix aims to remove that step.
Zero configuration
When a device joins the network the connection forms on its own. No manual file editing.
End-to-end encryption
Only the endpoints can decrypt the traffic. No component in between — including the provider — can see the content.
Rust and open source
Memory safety is provided at the language level. Because the source is open, the security claim is open to inspection — you do not have to trust a closed box.
// FREQUENTLY ASKED QUESTIONS
Common questions
How does a peer-to-peer VPN differ from a classic VPN?
In a classic VPN all traffic passes through a central server. In Lattix devices connect directly to each other. That has three consequences: latency drops because the path is shorter, shared server capacity no longer forms a ceiling, and there is no server in between whose failure stops the connection.
Does setup require editing a configuration file?
No. Lattix is designed for zero configuration: when a device joins the network the connection forms on its own. The longest steps of a classic VPN setup — key generation, address block selection, routing rules — disappear.
Who can see the traffic?
Only the endpoints. The connection is encrypted end to end, and no component in between — including the provider — can decrypt the content. Because there is no central server, there is also no point where traffic accumulates.
Why is it written in Rust?
Memory safety bugs are among the most common security weaknesses in networking software. Rust prevents that class of error at the language level — rather than trying to detect it at runtime, it refuses to compile.
What difference does being open source make?
It makes the security claim inspectable. With a closed product you have to trust that the encryption really is end to end; with open source you can look. In a VPN that distinction goes straight to the product’s most basic promise.
Which operating systems does it run on?
It runs on Windows, macOS and Linux. Once devices join the same network, the difference in operating system does not affect the connection.
Can it be used on a corporate network?
Yes. It is designed for distributed teams and infrastructure owners building their own network. Because devices connect directly to each other, there is no central VPN server to operate.
What does adding a new device to the network involve?
The device joins the network and the connection forms on its own — no key generation, address block selection or routing rules. In a classic VPN those steps repeat per device, so the setup burden grows as the team grows.
Is Lattix a VPN service, or a tool for building your own network?
The second. It is not a service you subscribe to with your traffic passing through a provider’s servers, but a network layer where you connect your own devices to each other. In practice that distinction means there is no third party carrying the traffic — and therefore no third party to trust.
GET STARTED
Let us talk through the setup.
Let us work out together how it fits your current infrastructure, how a migration would run and which plan suits your business.
Talk to the team →