Mia Connect
Remote desktop you host yourself. One VNC-compatible protocol connects a Windows, Linux or Android machine to another, straight between the two computers whenever the network allows it and through your own relay when it does not.
Download Mia Connect
One installer per platform and per processor. The table below holds the package published right now; older releases are kept in a second table underneath it. Once installed, the client updates itself from your own Mia Connect server.
| Platform | Version | Download |
|---|---|---|
| Windows | v0.1.9 | Downloadmiaconnect-0.1.9-x64.exe |
| Linux (.deb)Debian, Ubuntu, Mint | v0.1.9 | Downloadmiaconnect_0.1.9_amd64.deb |
| Linux (.rpm)Fedora, RHEL, openSUSE | v0.1.9 | Downloadmiaconnect-0.1.9-11.x86_64.rpm |
| Android | Not published yet | ask us for early access |
Older versions
Every release we still publish a package for, newest first. Take one of these only if a machine already runs it or you have a reason to stay; anyone starting now wants the version in the table above. One package is missing on purpose: the .rpm for 0.1.2 claimed directories the Fedora icon theme already owns, so dnf refused to install it, and we withdrew it rather than leave a download that cannot be used. Separately, the .exe for 0.1.1 through 0.1.3 needs the Microsoft Visual C++ 2015-2022 Redistributable installed first, or the app opens with a "MSVCP140.dll was not found" box. 0.1.4 and every .exe since carries that runtime inside itself and needs nothing from the machine.
| Platform | Version | Download |
|---|---|---|
| Windows | v0.1.8 | Downloadmiaconnect-0.1.8-x64.exe |
| v0.1.7 | Downloadmiaconnect-0.1.7-x64.exe | |
| v0.1.6 | Downloadmiaconnect-0.1.6-x64.exe | |
| v0.1.5 | Downloadmiaconnect-0.1.5-x64.exe | |
| v0.1.4 | Downloadmiaconnect-0.1.4-x64.exe | |
| v0.1.3 | Downloadmiaconnect-0.1.3-x64.exe | |
| v0.1.2 | Downloadmiaconnect-0.1.2-x64.exe | |
| v0.1.1 | Downloadmiaconnect-0.1.1-x64.exe | |
| Linux (.deb)Debian, Ubuntu, Mint | v0.1.8 | Downloadmiaconnect_0.1.8_amd64.deb |
| v0.1.7 | Downloadmiaconnect_0.1.7_amd64.deb | |
| v0.1.6 | Downloadmiaconnect_0.1.6_amd64.deb | |
| v0.1.5 | Downloadmiaconnect_0.1.5_amd64.deb | |
| v0.1.4 | Downloadmiaconnect_0.1.4_amd64.deb | |
| v0.1.3 | Downloadmiaconnect_0.1.3_amd64.deb | |
| v0.1.2 | Downloadmiaconnect_0.1.2_amd64.deb | |
| v0.1.1 | Downloadmiaconnect_0.1.1_amd64.deb | |
| v0.1.0 | Downloadmiaconnect_0.1.0_amd64.deb | |
| Linux (.rpm)Fedora, RHEL, openSUSE | v0.1.8 | Downloadmiaconnect-0.1.8-10.x86_64.rpm |
| v0.1.7 | Downloadmiaconnect-0.1.7-9.x86_64.rpm | |
| v0.1.6 | Downloadmiaconnect-0.1.6-8.x86_64.rpm | |
| v0.1.5 | Downloadmiaconnect-0.1.5-7.x86_64.rpm | |
| v0.1.4 | Downloadmiaconnect-0.1.4-6.x86_64.rpm | |
| v0.1.3 | Downloadmiaconnect-0.1.3-5.x86_64.rpm | |
| v0.1.1 | Downloadmiaconnect-0.1.1-2.x86_64.rpm | |
| v0.1.0 | Downloadmiaconnect-0.1.0-1.x86_64.rpm |
Every download is checksummed
The download folder carries a sha256sums.txt next to the packages. Before you install, run the two lines below inside that folder and check every line answers OK. Mia Connect is distributed from this site, so a mirror offering a different hash is not ours.
cd downloads sha256sum -c sha256sums.txt
What the installer puts on the machine
The client application and its icon. On first run it registers itself with the Mia Connect server it is pointed at and takes back its own nine-digit Mia address, which is the number you hand to whoever wants to connect. No background service is installed yet, so the machine answers while the app is open, not at the login screen.
What it needs to run
Windows 10 or 11 on 64-bit x86, or a 64-bit x86 Linux desktop on Debian, Ubuntu, Mint, Fedora or RHEL. Nothing has to be installed alongside it: every .exe since 0.1.4 carries the Windows runtime it needs inside itself. On Linux the client works out which display server it is standing on at start-up and says so out loud, since 0.1.8, instead of letting a connection go quiet and leaving you to guess. Sharing works on an Xorg session as before; on a Wayland session - the default on current Fedora and Ubuntu - since 0.1.9 the desktop's own screen-cast dialog appears and the person sitting there picks the screen to be seen, after which the picture streams the same way. That dialog cannot be answered in advance, so an unattended Wayland machine still wants an Xorg session, and on Wayland the session is view-only: someone at that keyboard keeps their own mouse until remote control is released for it.
For a whole office at once
The Windows installer takes NSIS's own /S switch, and the Linux packages install from a script with apt-get or dnf, so a batch of machines can be done without anyone clicking through pages. Each one then registers itself with your console on its first run; the server address is chosen in the client, not passed to the installer.
How a session finds its way through
Mia Connect tries the fastest path first and only falls back to slower ones. Nothing needs a port forward.
1. The server introduces them
Both clients are registered with your Mia Connect server. It passes the two ends each other's address and nothing more.
2. Same network, direct
On one LAN the session goes straight between the machines. Frames never touch the server, which is where the low latency comes from.
3. Different networks, still direct
Where the two machines can reach each other over the internet, they do so directly, without any third hop.
4. Behind NAT, punched open
When both sides sit behind a router, a UDP hole-punching attempt opens a path between them and the session stays peer to peer.
5. Last resort, your relay
If nothing else works, the frames are relayed through your own server. Yours, not somebody else's cloud, and still encrypted.
Encryption you decide on
The same RFB 3.8 protocol runs with the transport encrypted or not, chosen per connection. Standard VNC tools keep working either way.
What is inside the client
Built for the two jobs remote desktop is actually asked to do: support a machine, and work on one from elsewhere.
Every monitor, not just one
The client reports its whole display setup the moment it registers, so the person connecting sees what is really there.
- Per-monitor inventory on the server
- Choose one screen, or take them all
- Mixed resolutions and DPI per monitor
- Resize the guest screen mid-session
- Multi-seat workstations handled correctly
VNC-compatible, not VNC-limited
An RFB 3.8 protocol core means the tool that already works in your environment keeps working, with our extensions on top.
- RFB 3.8 handshake and authentication
- ZRLE and Tight encodings
- Encrypted transport, switched per session
- Works with standard VNC viewers
- Works as a server for standard VNC clients
Support before anyone logs in
A service installed at boot answers the door at the login screen, which is exactly where most support calls start.
- Starts with the operating system
- Reachable at the login and lock screens
- Unattended access password per machine
- Attended sessions still need a yes
- Reboots into a still-reachable machine
Files, clipboard, the usual work
The parts that make a remote session usable rather than merely visible.
- Two-way clipboard, including images
- File transfer in both directions
- Full-screen and windowed viewing
- Keyboard shortcuts sent deliberately
- Ctrl-Alt-Delete when you need the real thing
Your server, your records
The management console, the client API and the relay run on hardware you control, on three ports you open yourself.
- Console on 5099 for the administrator
- Client API on 5199
- Relay on 5299 for the fallback path
- Machine registry with hardware details
- Connection history kept in your database
Updates that follow your schedule
Clients ask the server whether a newer build exists. You publish one when you want the fleet to move.
- Version check against your server
- Publish a release when it is ready
- Nothing phones home to a vendor
- Faults reported to your own mailbox
- Audit trail of what each machine runs
The details that matter day to day
Small things that decide whether a remote session is pleasant or tolerable.
Latency first
Peer-to-peer whenever the network allows it, so the picture follows the mouse instead of lagging behind it.
From any device
Start a session from the desktop client, from a laptop, or from an Android phone in the corridor.
No third party
There is no vendor cloud in the path and no account to trust with your machine list.
Told when it breaks
Client and server faults arrive as mail alerts with the machine, the version and the stack.
Why Mia Connect
A short list of the reasons people pick it over the alternatives.
No per-seat subscription
Install it on the machines you own. The cost is the server you already have and the licence you agree with us once.
Greek software, Greek support
Built and supported by Mia Solutions, with documentation and people answering in Greek and English.
The hardware you have
64-bit and ARM packages for Windows, Ubuntu, Fedora and Android, built and published per processor rather than one file that hopes to fit all.
Provable downloads
Every package on this page is published with its SHA-256 checksum, so what you install is what we built.
Visible on the console
Which machine is online, what it reports for hardware and monitors, who connected to it and when.
Start small, grow
Two machines and one server on a Tuesday afternoon, or a few hundred seats behind one console. Same software.
Try it on two machines
Download the client, tell it which Mia Connect server to register with, and connect. We will set the server up with you if you would rather not.
Accelerate innovation with world-class tech teams We'll match you to an entire remote team of incredible freelance talent.