brainstate

discover · compare · collections · requirements · contribute · feed · watching · stats · help with your tokens

dont-be-evil-company/p2p.kiwi · source

Snapshot 0 · 2026-11-04T12:47:27Z · TypeScript · MIT

Content fingerprintfc22adbc1a9916fb13fc97e148df7c867eedfcc73669a8855d75c07341ba9a5a

GitHub description at capture

p2p.kiwi 🥝, Cross-Platform screen 🖥️ sharing 📡 made simple ⚡.

README at capture

<div align="center">

![p2p.kiwi logo](logo.png)

# `p2p.kiwi` - P2P Conferencing and Screen Sharing

[![Downloads](https://img.shields.io/github/downloads/dont-be-evil-company/p2p.kiwi/total.svg?style=for-the-badge)](https://p2p.kiwi/)
[![Discord](https://the-dont-be-evil-company.com/assets/badges/discord.svg)](https://the-dont-be-evil-company.com/discord)
[![GitHub release (latest by date)](https://img.shields.io/github/v/release/dont-be-evil-company/p2p.kiwi?style=for-the-badge)](https://github.com/dont-be-evil-company/p2p.kiwi/releases/latest)

[Install](#install) •
[Website](https://p2p.kiwi/) •
[Privacy Policy](./PRIVACY.md) •
[Terms of Service](./TOS.md) •
[Code of Conduct](./CODE_OF_CONDUCT.md)

<p></p>

`p2p.kiwi` P2P Conferencing and Screen Sharing is a simple and
easy-to-use screen sharing tool for Mac, Windows, and Linux.

It utilizes a peer-to-peer connection to share your screen with others,
without the need for an account. STUN and optional TURN servers are still
used to exchange ICE connectivity information.

That is not a signaling server for chat or media keys.

![p2p.kiwi open-graph image](open-graph.png)

</div>

## Install

## Install Manually

Grab the latest release from the [GitHub releases page](https://github.com/dont-be-evil-company/p2p.kiwi/releases/latest).

## Install via Arch Linux `AUR`

```sh
paru -S p2p-kiwi-bin`
```

or

```sh
yay -S p2p-kiwi-bin`
```

## Install via Homebrew

```sh
brew install --cask p2p-kiwi
```

## `E2EE` (End-to-End Encryption)

> [!WARNING]
> Don't determine whether the call is `E2EE` by checking whether WebRTC reports `DTLS-SRTP`.
> `DTLS-SRTP` is expected to encrypt transport.
>
> Our actual `E2EE` guarantee comes from [`MLS`-managed application keys](https://www.rfc-editor.org/rfc/rfc9420.html) encrypting the media with [`SFrame`](https://www.rfc-editor.org/rfc/rfc9605.html).

### `E2EE` (End-to-End Encryption) Architecture

```
┌─────────────────────────────────────────────┐
│                  MLS                        │
│       membership + E2EE key management      │
├─────────────────────────────────────────────┤
│                 SFrame                      │
│       E2EE encryption of media frames       │
├─────────────────────────────────────────────┤
│               DTLS-SRTP                     │
│          WebRTC transport security          │
├─────────────────────────────────────────────┤
│               ICE / UDP                     │
│               networking                    │
└─────────────────────────────────────────────┘
```

**`MLS` answers:**
"Who is in this encrypted group, and what cryptographic secrets should they possess?"

**`SFrame` answers:**
"How do I encrypt this video/audio frame so infrastructure carrying it can't read it?"

**`DTLS-SRTP`** answers:
"How do I securely transport WebRTC media over this connection?"

### `E2EE` (End-to-End Encryption) Example

```
     MLS Group
┌─────────────────┐
│ Alice Bob Carol │
└────────┬────────┘
         │
 derives E2EE keys
         │
         ▼
      SFrame
   encrypt media
         │
         ▼
     DTLS-SRTP
         │
 WebRTC transport
         │
         ▼
        Peer
```