Find answers, fast.

Open Tenvo on both devices. On the remote device, note the device ID shown on screen. On your device, enter that ID and click Connect. The remote user will see a prompt to accept the connection.

Yes, Tenvo needs to be running on both the local and remote computer. (A portable Windows build that runs without installation is on the roadmap — for now the standard NSIS installer is the only Windows distribution.)

Go to Settings in Tenvo and set a persistent password. Once configured, you can connect to that device anytime without someone needing to accept the connection on the other end.

Yes, you can use basic remote access with just the device ID and one-time password. Creating a free account unlocks the address book and gives you 30 devices on the Free tier.

Yes. Tenvo connects through port 443 (HTTPS), which is open on virtually all networks including corporate firewalls. No port forwarding or special configuration needed.

No. Tenvo provides its own encrypted tunnel between devices over TLS (port 443). You do not need a separate VPN. It works from most networks, including behind NAT, falling back to our relay when a direct connection is not possible.

Connection speed depends on the internet speed of both devices. Try lowering the display quality in session settings, closing bandwidth-heavy applications, or connecting via a wired Ethernet connection instead of Wi-Fi.

Yes. If both devices are on the same network, Tenvo will route traffic directly between them for maximum speed and lowest latency.

All connections are encrypted with TLS over port 443 using a unique per-device certificate. Direct peer-to-peer connections are end-to-end encrypted. The client is open source (AGPL-3.0), so the encryption can be independently audited, and you can self-host the relay.

No. By default, every incoming connection requires your explicit approval. If you enable unattended access with a persistent password, only someone with that password can connect.

No. Our relay servers route encrypted packets without the ability to decrypt them. Session data is never written to disk. Once your connection ends, there is no trace of what was transmitted.

Yes, for personal use. The free plan includes up to 30 devices (with account), 1 concurrent session, 5 GB/mo of relay traffic, file transfer up to 5 MB, and session chat. No credit card required.

Stripe Checkout handles payment. The exact set of methods you see depends on your country and Stripe's current rollout — Visa/Mastercard/Amex are everywhere, with country-specific local methods (e.g. SEPA, iDEAL, BLIK in EU) appearing as Stripe enables them. Bank-transfer / invoice billing are not yet supported.

Yes. You can upgrade or downgrade your plan at any time. When upgrading, you pay only the prorated difference. Downgrades take effect at the next billing cycle.

EU/UK consumers have a statutory 14-day right of withdrawal under the Consumer Rights Directive — see the Refund Policy for the exact mechanism. Outside the EU/UK we don't offer a blanket money-back guarantee, but if a paid plan is genuinely broken for you, email support@tenvoai.com and we'll work it out.

Tenvo currently ships native clients for Windows 10/11 (64-bit), macOS 12+ (Apple Silicon + Intel universal binary, Apple-notarized), and Debian/Ubuntu Linux (.deb, glibc 2.31+). Connect from any of these to any other. Android, iOS, .AppImage, and .rpm are on the roadmap — see the next section for specifics.

Not yet. Today the Windows distribution is a single NSIS installer (~18 MB). A portable .exe and an MSI for Group Policy deployment are both on the roadmap. The NSIS installer is unsigned today (EV cert pending Cyprus business-registry clearance) — SmartScreen flags it on first launch; click "More info → Run anyway".

Not yet officially. The current installer writes to Program Files. A portable build is on the post-v0.14 roadmap. As a workaround, the installer is a single .exe — you can copy the installed `Tenvo\flutter_godesk.exe` + `librustdesk.dll` to a USB drive and they will run from there, but config + permissions persist on the host machine, not the USB.

Not yet. Both clients are in active development. Android is targeted Q3 2026, iOS shortly after. The /platforms/android and /platforms/ios pages have a waitlist — sign up there and we email when each ships. Until then, the desktop clients (Windows / macOS / Linux) cover every documented feature.

We currently ship a single .deb package built on Ubuntu 24.04. The binary depends on glibc 2.31+, so it works on Debian 11+, Ubuntu 22.04+, Mint 21+. .AppImage (universal, dependency-free) and .rpm (Fedora/RHEL) are roadmapped — sign up for the Linux waitlist on the /platforms/linux page. For Arch, the AGPL source is on GitHub; community AUR packages from forks build cleanly with the documented `cargo build --release --features flutter` + `flutter build linux` commands.

We are not certified for SOC 2, ISO 27001, or HIPAA today. Connections are encrypted with TLS using per-device certificates; direct connections are end-to-end encrypted. The client is open source, so the encryption is auditable. We will not claim certifications we do not hold.

We removed those sliders in 0.13.17 because they didn't actually affect the audio pipeline (the underlying cpal library mixes at the OS device level). Use your operating-system volume mixer to adjust per-app levels: Windows → right-click sound icon → Open Volume Mixer; macOS → System Settings → Sound → Output. Per-session gain controls inside Tenvo are on the roadmap.

No — not today. Tenvo is built and run by a small team (one full-time founder + part-time contractors). Support is async via support@tenvoai.com — we typically reply within 24 hours on weekdays and may take longer on weekends. There is no contractual SLA. The relay infrastructure runs on a single VPS today (not multi-region, no auto-failover). Once we cross 500+ paid users we will publish a real SLA backed by HA infrastructure (Phase G of our roadmap).

All relay traffic currently goes through a single VPS, so relay latency depends on your distance to it. For most desktop-control workflows this is acceptable, but users far from the relay will notice — which is why direct P2P (the default) matters: most sessions never touch the relay. Multi-region relay POPs, including an EU POP, are roadmapped per ADR-009. The Settings → Network panel shows the active relay region.

Yes — fully supported and documented. The relay is two Rust binaries (`hbbs` for rendezvous, `hbbr` for traffic relay) that run on any Linux box with a public IP, ~50 MB RAM at idle. Setup is a 10-minute exercise on a $5/month VPS. See the self-hosted-remote-desktop blog post for the step-by-step. Self-hosting bypasses our relay entirely and gives you full data sovereignty.

Tenvo is in early launch (May 2026). We have a small handful of paying users today and we publish honest numbers — no fabricated metrics on this site. If you'd like to be referenced as an early customer with a logo + 2-line testimonial in exchange for visible-on-the-pricing-page perks, email support@tenvoai.com. We will populate /partners and a customer roll-call page only once we have actual customers who opt in publicly.