p2p.kiwi

p2p.kiwi keeps remote control sessions private by combining full end-to-end encryption (E2EE) with a peer-to-peer mesh network, so mouse and keyboard input travels directly between your devices instead of through a p2p.kiwi cloud. According to the project's own description, there is no p2p.kiwi cloud and no forced accounts, which means the operator does not sit in the middle of your session and you do not have to create an identity to use it. This applies to the remote-control feature as well as the chat, voice, and screenshare functions that ship alongside it.

The two mechanisms that do the work

1. End-to-end encryption across every session type

p2p.kiwi describes itself as "Full E2EE" and lists the encrypted surface as:

• Remote control (mouse and/or keyboard)
• Chat
• Voice
• Screenshare

Because the same E2EE claim covers all four, the privacy property is not limited to the remote-control channel. If you are typing on a remote machine, that input stream is protected the same way a chat message or a voice call is.

The practical meaning of E2EE here: the devices at each end hold the keys, and the content is encrypted between them. A relay or intermediary that only forwards packets does not get readable input, keystrokes, or screen data.

2. A P2P mesh instead of a central cloud

The project states there is no p2p.kiwi cloud. Instead, devices form a P2P mesh network and connect to each other. That design has three privacy consequences worth separating:

The "no cloud" and "no forced accounts" points are the ones most often confused. They are separate: one is about where data flows, the other is about whether you need an identity. p2p.kiwi claims neither a cloud nor mandatory accounts.

What this means in a real remote-control task

Say you need to control a Windows desktop from a MacBook on a different network. With a cloud-relayed remote-control tool, your keystrokes and screen frames typically pass through the vendor's infrastructure. With p2p.kiwi's stated model, the two machines are peers in a mesh and the session is E2EE, so the readable content stays at the endpoints.

That said, "no cloud" does not automatically mean "no server ever touches a packet." NAT traversal and mesh connectivity can still involve coordination infrastructure in many P2P systems. The p2p.kiwi page does not detail its connection-establishment path, so treat the strong claim — no p2p.kiwi cloud, E2EE, no forced accounts — as what the project asserts, and verify the connection details in its docs and source if that distinction matters to you.

What is and is not claimed

Supported by the project description:

• Full E2EE
• Cross-platform: macOS ↔ Windows ↔ Linux
• P2P mesh network
• Remote control of mouse and/or keyboard, plus chat, voice, and screenshare
• No p2p.kiwi cloud
• No forced accounts
• Free and open-source

Not stated on the page, so do not assume it:

• Pricing tiers or paid plans (the page says free and open-source, but no pricing page is referenced)
• Whether any relay or signaling server is used for NAT traversal
• Specific cryptographic algorithms or key-exchange methods
• Login requirements beyond "no forced accounts"

How to check the privacy claims yourself

1. Go to the p2p.kiwi site and open the Docs section referenced on the page.
2. Look for how peers discover each other and whether any coordination server is involved in connection setup.
3. Review the source code via the "View the code" link, since the project is open-source — this is the most direct way to confirm the E2EE and mesh behavior rather than relying on the summary.
4. Install it on two of your own machines (for example macOS and Windows) and test a remote-control session to see the direct-connection behavior in practice.

The page provides Install, Screenshots, Docs, and Get involved entry points, and invites contributions, so the docs and repository are the intended places to verify details the landing page does not cover.

Yes. p2p.kiwi is described on its own site as "completely free and open-source," and the page explicitly states that contributions are welcome. The site provides two direct entry points for getting involved: a "Get involved" link and a "View the code" link. If you want to inspect the source, report issues, or contribute changes, those are the starting points the project itself points you to.

What the Project Says About Its Open-Source Status

The p2p.kiwi homepage makes three claims that matter for this question:

• Open-source: The project describes itself as "completely free and open-source."
• Contributions welcome: The page states, "p2p.kiwi is open-source and we welcome contributions."
• Code is viewable: A "View the code" link is presented on the page, alongside a "Get involved" link.

There is no p2p.kiwi cloud and no forced accounts, according to the site. That matters for contributors because it means the project is not gated behind a hosted service — the software itself is the product.

How to Get Involved

The page gives you two named entry points rather than a detailed contributor guide. Based on what the site provides:

1. Open the "Get involved" link on the p2p.kiwi homepage. This is the project's own pointer for people who want to participate.
2. Open the "View the code" link to reach the source repository. This is where you would inspect the code, and typically where contribution workflows (issues, pull requests) live.
3. Check the Docs link if you need to understand how the software works before contributing. The homepage lists "Install," "Screenshots," and "Docs" as its main navigation items.

The site does not spell out a contribution process beyond these links, so the repository itself is the place to look for contribution guidelines, issue trackers, and coding conventions.

What You'd Be Contributing To

Understanding the scope helps you decide whether your skills fit. According to the site description, p2p.kiwi is:

So contributions could span cross-platform desktop code, networking/mesh logic, encryption, chat/voice/screenshare features, or documentation — depending on where the repository needs help.

Practical Notes Before You Contribute

• Start from the project's own links. The homepage's "Get involved" and "View the code" links are the authoritative entry points; anything else is secondhand.
• Read the Docs first if you are unfamiliar with the architecture. The site lists Docs as a primary resource.
• No account is required to use the software, per the site, which also suggests there is no hosted contributor portal — contribution happens through the code repository.
• Pricing is not a barrier. The project describes itself as completely free, and the page shows no pricing links or payment platforms.

If your goal is simply to use p2p.kiwi rather than contribute, the same homepage links (Install, Docs) cover that path. If your goal is to contribute, begin with "Get involved" and "View the code," then follow whatever process the repository defines.

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.

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.

p2p.kiwi is a free, open-source, cross-platform tool that combines P2P mesh remote control (mouse and keyboard) with E2EE chat, voice, and screenshare. It differs from typical remote control or chat apps in three structural ways: there is no p2p.kiwi cloud, there are no forced accounts, and the connection is a peer-to-peer mesh rather than a client-to-server relay. If you need a hosted admin console, centralized user management, or a service that works without any direct peer connectivity, p2p.kiwi is not the right fit.

The core architectural difference: no cloud, no forced accounts

Most remote control and chat products route traffic through vendor infrastructure. That infrastructure typically also holds your account, device list, and session metadata.

p2p.kiwi inverts this. Per the project's own description, "There is no p2p.kiwi cloud and no forced accounts." That means:

• No central server holding your sessions. The vendor does not operate a relay or broker that your traffic passes through.
• No account requirement. You are not asked to register an identity with the project to use it.
• Open source. The code is public and contributions are welcomed, so the privacy and encryption claims can be inspected rather than trusted.

The trade-off is direct: you give up the convenience of a web dashboard, centralized device management, and vendor-provided NAT traversal infrastructure.

What p2p.kiwi actually does

It is not only a remote control tool and not only a chat app. The project positions itself as a combination, described as "Skype's nerdy little sister, but E2EE."

How it compares on the dimensions that matter

Encryption scope

Typical remote control apps often encrypt the transport (for example, TLS to a relay server) but terminate that encryption at the server. p2p.kiwi describes full E2EE covering remote control, chat, voice, and screenshare. The distinction is where encryption ends: at the vendor's server, or at the peer.

Network topology

Typical tools use a hub-and-spoke model: your device connects to the vendor's server, and the other device connects to the same server. p2p.kiwi uses a P2P mesh, so peers connect to each other rather than through a central hub.

Identity and onboarding

Typical tools require an account, often tied to email or a corporate directory. p2p.kiwi has no forced accounts, which removes a central identity store but also removes centralized access revocation and auditing.

Cost and licensing

p2p.kiwi is described as completely free and open-source. Typical commercial remote control and chat products usually gate features, device counts, or commercial use behind paid tiers.

When p2p.kiwi is the better choice

• You want remote control and real-time communication in one tool rather than two.
• You specifically do not want a vendor cloud or a mandatory account.
• You want to verify privacy claims by reading the source.
• You work across macOS, Windows, and Linux and need all three to interoperate.

When a typical remote control or chat app is the better choice

• You need a web admin console, centralized device inventory, or SSO.
• You need guaranteed connectivity in restrictive networks where direct peer connections fail and only a relay works.
• You need compliance reporting, session recording with audit trails, or role-based access control managed by an IT department.
• You need vendor support with an SLA.

How to evaluate it yourself

1. Check the platform coverage against your own machines (macOS, Windows, Linux).
2. Confirm your network allows direct peer connections; a P2P mesh depends on peers being reachable.
3. Read the source if encryption and no-cloud claims are the reason you are switching.
4. Test remote control, chat, voice, and screenshare as separate workflows, since each is a distinct feature even under one E2EE umbrella.

The project provides install instructions, screenshots, and documentation on its site, plus a public code repository for review.