What Is p2p.kiwi?

p2p.kiwi is a free, open-source remote control tool that connects macOS, Windows, and Linux machines directly to each other over an end-to-end encrypted (E2EE) peer-to-peer mesh network. It lets you control another computer's mouse and keyboard, and it also bundles chat, voice, and screen sharing. There is no p2p.kiwi cloud and no forced accounts, so if you want cross-platform remote control without routing your input through a vendor's servers or signing up for a login, this is the model it offers.

What p2p.kiwi actually does

The project describes itself as "Skype's nerdy little sister, but E2EE" — a compact communication and control tool rather than a full remote-desktop suite. Its stated capabilities:

• Remote control — mouse and/or keyboard input sent to another machine
• Chat — text messaging between peers
• Voice — audio calls
• Screenshare — viewing another machine's screen
• P2P mesh network — peers connect to each other rather than through a central relay

The headline use case is cross-platform remote control: MacOS ↔ Windows ↔ Linux in any direction, according to the project description.

The two design choices that matter most

End-to-end encryption

Traffic between peers is E2EE. Combined with the absence of a p2p.kiwi cloud, this means the project positions itself so that the operator does not hold your session content. That is the main reason someone would pick this over a mainstream remote-desktop product.

No cloud, no forced accounts

There is no p2p.kiwi-hosted backend and no mandatory sign-up. You are not creating an account with a company to move your own mouse between your own machines. The trade-off is implicit: without a vendor cloud, peer discovery and connectivity depend on the mesh itself, so your network environment matters more than it would with a relay-backed service.

Platform and licensing summary

Who this fits, and who it doesn't

Reasonable fit if you:

• Need to drive a Windows box from a Mac (or Linux, or the reverse) and want the input path encrypted end to end
• Prefer not to create an account with a remote-access vendor
• Want chat, voice, and screenshare in the same tool as remote control
• Are comfortable with open-source software and, if needed, reading the code or docs

Look elsewhere if you:

• Need a managed service with a support contract and an SLA — this is a community open-source project
• Want zero setup and rely on a vendor's relay to punch through difficult networks
• Need enterprise fleet management, audit logging, or centralized policy controls; nothing in the project description indicates those

Getting started

The project's own entry points are Install, Screenshots, and Docs, plus a View the code link for the source and a Get involved path for contributors. Start with Install for your platform, then check Docs for how peers are paired and connected — that pairing step is where a mesh tool typically differs most from a cloud service, so it is worth reading before you rely on it.

Because the project publishes no pricing page, payment platforms, or account tiers, treat "completely free" as the project's own description of its current state rather than a guarantee about future hosting or support arrangements.