Remmina is the client most Linux desktops reach for first. On Ubuntu it is already installed, it opens RDP, VNC, SPICE and SSH sessions from one window, and it costs nothing.
Remmina is the client most Linux desktops reach for first. On Ubuntu it is already installed, it opens RDP, VNC, SPICE and SSH sessions from one window, and it costs nothing. Then one day you need to reach a machine that sits behind somebody else's router, or help a colleague on a Mac, or connect at 2 a.m. to a server nobody is logged into, and the tool that felt complete suddenly asks for an IP address you don't have.
That moment is the whole subject of this guide. Remmina is a good client. It is not a remote access service, and most searches for a Remmina alternative are really searches for the parts a client was never meant to provide. Below: what Remmina does, exactly where the line between client and service falls, and which tool fills each gap.
What Remmina actually is
Remmina is a GTK desktop application for Linux, licensed under the GPL and maintained by a volunteer team on GitLab. It is a front end: each protocol comes from a plugin built on an existing library. RDP goes through FreeRDP, VNC through libvncclient, and there are plugins for SPICE, SSH, SFTP and X2Go. You save connection profiles, group them, set resolution and colour depth per profile, and open several sessions in tabs.
Everything Remmina does starts from one assumption: the machine you want is reachable at an address you already know, and something on that machine is listening. An RDP server on port 3389, a VNC server on 5900, an SSH daemon on 22. Remmina's job begins once that path exists. It does not create the path.
- Mixed protocols in one place. RDP to a Windows box, VNC to a lab machine and SSH to a router, all from saved profiles.
- LAN administration. Inside one network, where every host has a stable address, it is fast and needs no account anywhere.
- Packaging. It ships in the repositories of every major distribution and as a Flatpak, so installing it is one command.
- No middleman. Traffic goes straight from your client to the target's server, with no vendor in the path.
If your work fits inside that list, you may not need an alternative at all. The trouble starts at its edges.
Where a client stops and a service starts
A remote access service is a client plus the infrastructure that lets two devices find each other and agree to talk. Remmina has the first half. The second half breaks down into five jobs, and each one is something you either build yourself or pay someone to run.
- Discovery. A service gives each device a stable ID. You connect to an ID, not an IP, so it doesn't matter that the target's home address changed overnight.
- NAT traversal. Most machines sit behind a router that drops unsolicited inbound connections. A service brokers a hole-punched direct connection between the two sides, so neither has to open a port.
- A relay. When hole punching fails, as it often does behind carrier-grade NAT or strict corporate firewalls, traffic goes through a relay server that both sides can reach with outbound connections.
- The listening side. Remmina needs a server on the target: xrdp, a VNC server, GNOME Remote Desktop. A service ships its own agent that installs on Windows, macOS and Linux and behaves the same on each.
- Identity and policy. Who may connect, to which devices, with what approval, and a record afterwards. With a bare client this lives in scattered passwords and firewall rules.
None of this is a flaw in Remmina. A client is not supposed to run relay servers. The point is that when people say Remmina doesn't work for them, the failing piece is nearly always on this list, and switching to another client with a nicer interface fixes nothing.
Four situations where the difference hurts
These are the cases that come up most often when a Linux user starts looking for something else.
The target is behind a router you don't control
A parent's laptop, a client's office PC or a machine on mobile data has no public address for you to type in. The textbook fix is port forwarding, and exposed RDP is one of the most common ways attackers get into small networks; the mechanics are in RDP brute-force attacks. Behind CGNAT, forwarding isn't even possible because you don't own the public address, as remote desktop behind CGNAT explains. A service with NAT traversal and a relay removes the problem, which is the idea behind remote desktop without port forwarding.
Nobody is logged in on the other end
Unattended access to a Linux host through Remmina means configuring xrdp or a VNC server to start before login, choosing a desktop session it can actually run, and keeping that working across distribution upgrades. Wayland makes it harder, because screen capture now goes through portals that often expect a person to click Allow. Wayland remote desktop support and headless Linux remote desktop cover the details. An agent that runs as a system service and registers the device once is a different amount of work.
The other person isn't on Linux
Remmina runs on Linux only. When the person who needs help uses Windows or a Mac, you need a way for them to install something, read out a code and approve you, all in under a minute. That flow requires the same agent on all three platforms and a broker between them, which is exactly what a client cannot offer.
More than one person needs access
Saved profiles in one user's home directory don't scale to a team. Once three technicians share forty machines, you need a shared device list, access you can revoke in one place and a record of who connected where. That is the territory of remote desktop audit logging, and a desktop client was never built to hold it.
Remmina alternatives, sorted by the gap they fill
Pick by what is missing, not by which interface looks nicer. The table compares the usual candidates on the jobs from the list above.
| Option | What it is | Reachability without open ports | Target platforms | Who runs the infrastructure |
|---|---|---|---|---|
| Remmina | Client only | No | Whatever server you install | You |
| Tenvo | Managed service built on RustDesk | Yes: direct P2P, managed relay as fallback | Windows, macOS, Linux | Us |
| Self-hosted RustDesk | Open-source client plus a server you run | Yes, through your own relay | Windows, macOS, Linux, Android | You |
| NoMachine | Client and server on the NX protocol | You handle it: UPnP, a forwarded port or a VPN | Windows, macOS, Linux | You |
| RDP or VNC over a VPN | Network layer plus your existing client | Yes, the VPN provides it | Whatever server you install | You or the VPN vendor |
Tenvo is our product, so weigh this paragraph accordingly. It is built on RustDesk and keeps what Remmina users tend to value: a native Linux client and a client licensed under AGPL-3.0. What it adds is the service half. Devices get IDs, connections go direct peer-to-peer when the network allows, and fall back to a relay we operate on two servers in Frankfurt when it doesn't. Native clients run on Windows, macOS and Linux, and a browser client is in public beta.
Be precise about security. Sessions use TLS with a certificate per device. A direct peer-to-peer connection is encrypted end to end between the two machines. When a session falls back to the relay, TLS terminates at the relay, which means we, as its operator, are in a position to see that session. If that matters for a particular machine, the background is in remote desktop encryption explained.
Pricing: Free is $0 for non-commercial use, with up to 3 devices, one session at a time, 2 hours a day in total across relay and direct connections, and 5 GB a month of relay traffic. Lite is $2.99 a month for up to 50 devices with no daily time cap. Pro is $7.99 a month. The full breakdown is on the pricing page.
Running your own RustDesk server makes sense only when a written requirement forces it: a compliance rule that bars third-party infrastructure, an isolated network, a data-residency clause. Then self-hosted RustDesk is the right answer, and our RustDesk self-hosting tutorial covers the setup. Without such a requirement it is the more expensive path once you count the server, patching, certificate renewal, key custody and being the person paged when the relay goes down. The hidden costs of self-hosting puts numbers on that, and our RustDesk comparison lays the trade-offs side by side.
NoMachine performs well on a LAN or over a VPN you already have; see NoMachine on Linux and its alternatives. A VPN plus Remmina is a sensible setup for one admin and a handful of servers they own, because it keeps Remmina and fixes only reachability. It does nothing for the Windows user who needs help in the next five minutes, and the trade-offs are laid out in remote desktop vs RDP vs VPN.
When Remmina is still the right tool
Keep it for what it does best. If you administer machines on one LAN, connect over RDP to Windows servers that already sit behind a VPN, or jump between SSH and VNC sessions on lab hardware, Remmina is quick, its profiles are plain text files you can copy between machines, and it needs no account. There is no reason to replace that with a service. For protocol choice in those setups, VNC vs RDP for modern remote access is a useful companion.
Many Linux users end up with both: Remmina for the hosts they can reach directly, a remote access service for everything outside the LAN. That is not a compromise. They are two tools for two different problems.
Moving the off-LAN machines over
If the service half is what you are missing, the move is small, because you are not replacing Remmina everywhere.
- List the machines you reach through port forwards, dynamic DNS or someone reading an IP address to you over the phone. Those are the candidates; LAN hosts can stay in Remmina.
- Install the Tenvo client on one of them and on your own Linux desktop, and connect by device ID. Check whether you get a direct connection on the networks you care about.
- For unattended hosts, set the client to run as a service and configure a permanent password before you walk away from the machine.
- Close the port forwards and remove the dynamic DNS records you no longer need. An open 3389 or 5900 left behind is the main risk this exercise removes.
- Keep the Remmina profiles for LAN machines and delete the ones that now go through Tenvo, so nobody falls back to the old path out of habit.
The Free plan is enough to try this on a personal setup. For client work or anything commercial, start on Lite, since Free is limited to non-commercial use.
If the machines you need sit outside your network, download Tenvo for Linux, Windows or macOS and connect by ID in a couple of minutes; the step-by-step Tenvo tutorial walks through the first session. Remmina can keep the LAN.
