How to Install and Start Using p2p.kiwi

p2p.kiwi is a free, open-source, end-to-end encrypted (E2EE) peer-to-peer tool for cross-platform remote control, chat, voice, and screenshare. You install a client on each machine you want to connect — macOS, Windows, or Linux — and the machines form a P2P mesh directly between themselves, with no p2p.kiwi cloud and no forced accounts. This guide covers how to get it installed and how to start a first session.

What you need before you start

• Two or more machines running macOS, Windows, or Linux. The project describes itself as cross-platform across all three (MacOS ↔ Windows ↔ Linux).
• Permission to install software on each machine.
• A network path between the machines. Because it is a P2P mesh with no central cloud relay described on the site, the machines need to be able to reach each other directly — for example on the same LAN, or over a network that allows direct peer connections.
• No account is required. The site states there are no forced accounts, so you should not expect a sign-up step.

Step 1: Get the installer

Go to the p2p.kiwi site and use the Install entry point. The homepage lists Install, Screenshots, and Docs as the primary links, so Install is the intended starting point for new users.

If you prefer to build or inspect it yourself, the site also links to the source code and states the project is open-source and welcomes contributions.

Step 2: Install on each machine

Run the installer on every machine you want in the mesh. Because the project is cross-platform, the same product covers macOS, Windows, and Linux — but you install the appropriate build for each operating system.

Repeat this on each device. A mesh needs at least two peers before anything can connect.

Step 3: Confirm the app launches

After installing, open the app on each machine. The site's Screenshots page is the best reference for what the interface should look like, and Docs covers the specifics of pairing and using each feature. Use those two pages rather than guessing at menu names, since the exact UI is documented there.

Step 4: Connect the machines and start a session

Once the app is running on two or more machines, use the app's pairing/connection flow (documented under Docs) to bring them into the same mesh. After they are connected, the features described by the project become available:

For a first test, the simplest useful task is remote control: connect two machines, then try moving the mouse and typing on the remote machine from the local one. If that works, chat, voice, and screenshare use the same peer connection.

Why there is no cloud step

p2p.kiwi describes itself as having "no p2p.kiwi cloud and no forced accounts." That means there is no central service to log into and no account to create as part of setup. The trade-off is that connectivity depends on the peers reaching each other directly rather than on a relay the vendor operates — so if two machines cannot establish a direct path, that is the first thing to check.

Common sticking points

• Only one machine installed. A mesh needs peers; install on at least two.
• Wrong build for the OS. Match the installer to macOS, Windows, or Linux.
• Peers can't see each other. Since the design is P2P without a described cloud relay, verify the machines have a direct network path (for example, same LAN) before troubleshooting the app itself.
• Unsure what a screen should look like. Compare against the Screenshots page and follow Docs for the exact flow.

Where to go next

• Install — download and set up the client.
• Screenshots — see the interface before and after setup.
• Docs — the authoritative reference for pairing and each feature.
• Source code — read or contribute, since the project is open-source.