Ask the other person for their 9-digit code, enter it on auffi.app and click Connect. You'll see their screen live — and can control it remotely with their permission. No account, no installation.
Download the sharer, start it, pass the displayed code to your helper and confirm the connection. They'll then see your screen.
A one-time connection code generated by the sharer. It's valid for at most 10 minutes, and the server rate-limits connection attempts per IP — so no one can guess codes.
Yes. The stream is end-to-end encrypted with DTLS-SRTP, the servers are in Germany, and there are no third-party trackers. Every spontaneous connection (code) must be confirmed on the sharer; for your own paired devices, the device password protects access instead. More on privacy (German).
Not for spontaneous help. You only need an account for unattended permanent access to your own device — such as your home PC.
Open source · GDPR-compliant · Servers in Germany
Need to get help? Enter the code the other person gave you.
Create an account and pair your own devices once — after that you connect any time with a fixed device ID and device password, without anyone having to click on the device.
Connections over our relay now run without the 10-minute limit. Also: sending a file waits for “Accept”, safer unattended access, clearer error messages. To the download.
The sharer for Windows is now available as a direct download — no installation, no sign-up. Standalone .exe or setup installer with WebView2.
Pair once, connect anytime: the new dashboard manages your own devices with auto-accept and a device password. A fixed device ID instead of a throwaway code.
Plasma 6 and GNOME 47 now work natively via GStreamer/PipeWire — no more XWayland fallback, no more flickering cursor.
New name, new domain auffi.app, same open-source code. Existing sessions keep running unchanged.
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.
WebRTC with DTLS-SRTP. The server only brokers the initial handshake — screen content, input and files flow encrypted directly between the sharer app and the browser; only if firewalls block that does our TURN relay forward the still-encrypted packets.
Hosted on an IONOS VPS in Frankfurt. GDPR-compliant, no US cloud, no third-party trackers, no Google Fonts.
Full source code on GitHub. Self-host, audit or fork it — backend, viewer and sharer are all documented.
9-digit code, connect, done. An account is only for unattended access — that is, when you regularly connect to the same devices.
Switching from TeamViewer, AnyDesk & co.? Remote support software compared: 8 tools →
Read more: Screen sharing without installation · Open source remote support · Free remote support
Head-to-head: RustDesk alternative · AnyDesk alternative · Quick Assist alternative
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).
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 encrypted directly between the sharer app and the browser; only if firewalls block that does our TURN relay forward the still-encrypted packets.
Yes. Servers in Germany (IONOS Frankfurt), no IP addresses stored in plaintext, no third-party trackers, no logging of content. The full audit lives in the repo at docs/security-review-2026-05.md.
Yes. The code is AGPL-3.0-licensed on GitHub. Backend, viewer, dashboard and TURN server run in Docker Compose, the sharer is a desktop app for Windows and Linux; the guide is in ops/README.md.
This device is password-protected. Please enter the device password.