Allowing anyone, no matter where they are, equal access to the Internet.

Utilizing Wireleap technology, we provide a new type of VPN service that's pretty fast, looks like regular HTTP/2 traffic, has multi-protocol support, multiplexed connections, onion encryption & routing and increased privacy.

Get started

Wireleap is a public interest technology with the goal of enabling more access to knowledge and resources on the Internet for more people, no matter where they are.

The technology stack is still under heavy development, and not yet feature complete, but should work for most as a consumer VPN replacement.

$ curl ifconfig.co/country

United States


$ wireleap start

$ wireleap exec curl ifconfig.co/country

Netherlands


$ wireleap reload

$ wireleap exec curl ifconfig.co/country

Switzerland

Why Wireleap?

Wireleap is building the technology stack for “A Routing Layer on the Internet that Enforces Net-Neutrality”. It's an ambitious goal, but when something is important enough, you do it despite the challenges. The real-world feedback gained from running Wireleap in production at EqualAccess will be pushed upstream in order to improve the technology, along with support for continued research and development. Besides, it's pretty cool tech, you should check it out!

Tunnel anything

Tunnel whatever traffic you want, how you want, seriously.

Only want to tunnel a specific browser session? No problem. Want to use an application that doesn't support the SOCKS5 protocol? Check. Prefer to just tunnel all your outgoing TCP and UDP traffic? Done.

Any application that supports the SOCKS5 protocol can be configured to route its traffic via the connection broker.

As there is no standard across applications for proxy settings, some wrapper scripts are included (called via exec).

Network connections from arbitrary programs can be intercepted and tunneled through the configured circuit.

And finally, all traffic on the system can be tunneled by starting tun.

$ curl --proxy socks5h://$(wireleap config address.socks) URL


$ export ALL_PROXY="socks5h://$(wireleap config address.socks)"

$ curl URL


$ google-chrome \
  --proxy-server="socks5://$(wireleap config address.socks)" \
  --user-data-dir="$HOME/.config/google-chrome-wireleap" \
  --incognito


$ wireleap exec curl URL

$ wireleap exec git clone URL

$ wireleap exec chromium-browser [URL]


$ wireleap intercept curl URL

$ wireleap intercept ssh USER@HOST


$ wireleap tun start

$ firefox

Circuit

You are in total control. Define the circuit that fits your needs.

Want lower latency? Choose 1 hop. Want more privacy? Choose 3, or even 10 hops! Prefer to select the exact relays used in the circuit, just specify them in the whitelist. Whatever you need, you decide.

The circuit defines which relays will be used to transmit traffic. Each relay assigns itself a role related to its position in the connection circuit. A Fronting relay provides an on-ramp to the routing layer, while a Backing relay provides an exit from the routing layer. Entropic relays add additional entropy to the circuit in the routing layer.

$ wireleap config circuit.hops 3


$ wireleap config circuit.whitelist "wireleap://relay.example.com:13490"

$ wireleap config circuit.hops 1

Privacy

Worried about privacy?

Onion encryption & routing: Traffic is encapsulated in layers of encryption, analogous to layers of an onion. The encrypted data is transmitted through a series of network nodes called onion routers, each of which “peels” away a single layer, revealing only the information required by the node to perform its job. Required information could include the data's next destination address, resulting in each intermediary knowing only addresses of the immediately preceding origin and the immediately following destination.

There are no user accounts: Access to the service is performed through the use of accesskeys. They are used to cryptographically and independently generate tokens by the client for each relay in the routing path, and included in the appropriate encrypted onion layer of traffic being sent, allowing the relay to authorize service. This increases the degrees of separation between payment information and network usage.

FLOSS

MIT licensed source code.

The easiest way to get started is by using the official pre-compiled release binaries. But, if you would like to build from source, browse the code or contribute ‐ head over to Wireleap's GitHub.

Decentralized relays

3rd party operated relays - coming soon!

Currently, equalaccess.net is operating all relays to verify network stability. We're actively working with other entities in preparation to deprecate the majority of our relays and replace them with 3rd party operated relays, and then scale up...

GUI

Graphical User Interface - coming soon!

At the moment, only command-line client software is available. A lightweight, cross-platform graphical user interface is under development and will be released shortly.