FAQ
Frequently asked questions about Alluno's features, licensing, and security
Common questions about Alluno, answered.
Source & Licensing
Is Alluno open-source or closed-source?
The desktop application and backend services are all proprietary. The source code is not publicly available for redistribution, modification.
Closed-source, distributed as compiled binaries via GitHub Releases
Closed-source and operated by Alluno
Proprietary, usage governed by our Terms of Service
Why is GitHub used if it's closed-source?
GitHub is used for:
- Release distribution: Compiled desktop app binaries are published on GitHub Releases
- Issue tracking: Users can report bugs and request features via GitHub Issues
- Community engagement: Discussions and feedback
The repositories do not contain the application source code.
Does Alluno use open-source technologies?
Yes. While Alluno itself is proprietary, it is built on top of many open-source technologies that we gratefully acknowledge. See our Credits page for the full list, including Rust, FFmpeg, WebRTC, QUIC, Nuxt, and more.
Security & Encryption
Does Alluno use end-to-end encryption?
Yes. Alluno uses end-to-end encryption for all remote desktop sessions. The encryption is provided by the underlying transport protocols, not a custom implementation.
Peer-to-Peer (Direct)
When a direct connection is established via WebRTC, all media streams are encrypted using DTLS-SRTP (Datagram Transport Layer Security for Secure Real-time Transport Protocol). Keys are exchanged directly between peers.
QUIC Transport
QUIC connections use TLS 1.3 built into the protocol, providing encryption, authentication, and integrity by default. There is no unencrypted QUIC.
How does key exchange work?
DTLS handshake is performed directly between the host and viewer. Session keys are negotiated per-connection using ephemeral key pairs, meaning each session has unique encryption keys that cannot be reused.
TLS 1.3 handshake establishes session keys. Supports 0-RTT and 1-RTT connection establishment for low-latency encrypted connections.
The signaling channel (used to coordinate peer connections) is secured via HTTPS/TLS. Signaling data includes SDP offers/answers and ICE candidates required for peer discovery.
What happens in relay mode?
When a direct peer-to-peer connection cannot be established (due to strict NAT or firewall), traffic is relayed through a relay server.
What does Alluno NOT have access to?
- Screen content, keystrokes, and file transfers are encrypted end-to-end
- Session encryption keys are negotiated directly between peers
- Relay servers forward encrypted packets without decryption capability
- See our Privacy Policy for full details on what we do and do not collect
What protocols and standards are used?
| Layer | Protocol | Encryption |
|---|---|---|
| Media transport | SRTP | AES-128-CM or AES-256-CM |
| Key exchange | DTLS 1.2+ | Ephemeral ECDH key pairs |
| QUIC transport | QUIC | TLS 1.3 |
| Signaling | HTTPS | TLS 1.2+ |
| API communication | HTTPS | TLS 1.2+ |