FAQ
How Arqut connects, what it can see, and how to verify what you install.
Getting started
What is Arqut?
Do I need to open ports or set up port forwarding?
Does it work behind CGNAT?
What do I install, and where?
How does Arqut find my services?
Security and privacy
Is my traffic encrypted?
What can Arqut see?
Not the contents of your traffic. Most connections are peer to peer — data goes straight between your app and your home network and never touches our infrastructure. When a direct path cannot be established, traffic is relayed through a TURN server instead.
A TURN relay forwards packets without being a party to their encryption. Your session is protected by two independent layers: the encrypted WebRTC transport, and a WireGuard tunnel inside it. The keys for both are negotiated directly between the app in your hand and Arqut Edge on your network. The relay holds neither, so what passes through it is ciphertext it has no way to read.
What the relay does see is connection metadata — the IP addresses and ports at each end, and the timing and volume of traffic. Our servers also hold your account data and run the signaling that introduces two peers to each other.
You do not have to take our word for any of this. The relay is the pkg/turn package in arqut-server-ce, it is Apache-2.0 licensed, and it is the same code that runs our hosted relay. And if you would rather no third party sit in the path at all, run the Community Edition — then the relay is yours.
What data do you store, and where?
Who is behind Arqut?
How do I report a security vulnerability?
SECURITY.md with a private reporting channel, and you can email contact@semilimes.com with SECURITY in the subject line. We acknowledge reports within three business days.What happens when I share access with someone?
Open source and licensing
Is Arqut open source?
How do I verify what I am installing?
Every Community Edition release ships with a SHA256SUMS file, a Sigstore signature over those checksums, an SPDX software bill of materials, and a GitHub build provenance attestation.
You can confirm a download matches its published checksum, confirm the checksums were signed by the release workflow itself, and confirm which commit and tag produced the binary. The exact commands are in each repository’s README under Verifying Downloads. Signing is keyless, so there is no long-lived private key that could be stolen.
What third-party code is included?
NOTICE and a THIRD_PARTY_LICENSES file listing every component actually compiled into the released binaries, generated from the build closure rather than written by hand. No GPL, LGPL, or AGPL code is distributed with either project.