Open source · GDPR-compliant · Servers in Germany

Share your screen in seconds — no install.

Stream running. 00:00 0 B
Auffi

Need to get help? Enter the code the other person gave you.

or

Want to ask someone else for help?

Download the sharer
Connecting …

News

Download the sharer for Windows

You only need the sharer if you want to share your own screen — whoever is helping just opens this page and types in the code.

Standalone .exe (~30 MB) for Windows 10/11 with WebView2 pre-installed — standard on modern systems. If you see an error on launch, use the setup installer (~150 MB), which installs the WebView2 runtime for you. Linux packages (Debian/Ubuntu, Fedora, Arch) are on the dedicated download page; macOS is coming later.

Why Auffi?

🔒 End-to-end encrypted

WebRTC with DTLS-SRTP. The server only brokers the initial handshake — screen content, input and files flow directly between the browsers.

🇩🇪 Servers in Germany

Hosted on an IONOS VPS in Frankfurt. GDPR-compliant, no US cloud, no third-party trackers, no Google Fonts.

🆓 Open source (AGPL-3.0)

Full source code on GitHub. Self-host, audit or fork it — backend, viewer and sharer are all documented.

👤 No account needed

9-digit code, connect, done. An account is only for unattended access — that is, when you regularly connect to the same devices.

Frequently asked questions

Do I need an account to use Auffi?

No. For ad-hoc help, a 9-digit connection code is all you need. You only need an account for unattended access (your own devices paired permanently).

Can the server see what I'm sharing?

No. WebRTC encrypts every stream end-to-end with DTLS-SRTP. The signaling server only brokers the initial handshake — pixels, mouse movements and files flow directly between the browsers.

Is Auffi GDPR-compliant?

Yes. Servers in Germany (IONOS Frankfurt), no IP addresses stored in plaintext, no trackers, no logging of content. The full audit lives in the repo at docs/security-review-2026-05.md.

Can I self-host Auffi?

Yes. The code is AGPL-3.0-licensed on GitHub. Backend, viewer and sharer all run in Docker Compose; the guide is in ops/README.md.