Self-hosted remote desktop— v1.0.11 is out
Your familiar desktop.
Wherever you work.
Open NikoDesk, connect through your own server, and keep working on your computer from anywhere. No accounts — and no third party ever sees your screen or files.
Before you download · a server of your own (public address), two commands to set up; already running RustDesk Server? You're ready.
A different place.
The same familiar flow.
Back to your desktop
Find a computer in your device list and keep working with your keyboard and mouse. Switch displays, go full screen and keep familiar shortcuts close.
Bring your files along
Move files and copy text between computers without breaking your flow. You stay in control of transfer and access permissions.
A view that fits the task
Choose clarity for reading or responsiveness for interaction. See connection details and adjust the picture while you work.
Give the screen a different view
Choose an animated preset or your own picture. Use a connection reminder or automatic activation. The controlled screen shows its privacy status; local exit requires the system login password.
A remote desktop shouldn't ask you to sign up or hand over your device list. If a service can be self-hosted, it should be.
Why NikoDesk exists
A connection that
only concerns you.
Most services keep your device list and connection history, and relay your screen through their servers. NikoDesk works the other way: registration, discovery and relay all run on hardware you own.
Solid: P2P direct (preferred) · Dashed: your relay (fallback)
Registration you own
Your device list, online status and keys live only on your server. No accounts, no cloud sync.
Direct first
If a direct connection can be punched through, it is. Only when the network says no does traffic fall back to your own relay.
Never calls out
Without private-server settings, the client contacts no public rendezvous server. Hard-coded, not promised.
Leave anytime
The server side is the open-source RustDesk Server OSS — no proprietary formats. When you're done with it, replace it.
Trust, where you can see it.
"Secure" is a claim, not an argument. These three things you can check yourself.
Choose who connects
Manage passwords and access rules on the remote computer. Grant viewing, input and file permissions separately, and end a session at any time.
Permissions stay visible
Screen capture, input, camera and microphone follow system permissions. Allow access when needed and revoke it afterwards.
Open for inspection
Built on the native RustDesk core under AGPL-3.0. Source code, build instructions and release notes are available on GitHub.
Who it's for —
and who it isn't.
One thing first: NikoDesk needs a server that belongs to you. Not a flaw — the premise.
- You have a machine with a public address — a VPS, a NAS or an always-on computer — or you'd gladly add one
- You already run RustDesk Server and want a more considered client
- You care where your device list and connection history live
- You'd trade one setup session for lasting independence
- You want to create an account and reach any computer right away
- You'd rather not touch servers, Docker or the command line
- You need things not yet offered, like controlling a phone or a web client
If the right column sounds like you, skip the install for now. Connections that never touch a third party need a server you run — a trade-off made on purpose, not a gap to close later.
Two processes are all
the server you need.
Start rendezvous and relay
hbbs handles device registration and discovery, hbbr handles relaying. Two Docker commands are enough, or reuse an existing RustDesk Server OSS setup. See the self-hosting guide.
Set up both devices
Enter the same server address and public key on both devices. Allow screen capture and input access as needed.
Make your connection
Enter the remote device ID and access password. Save frequently used computers locally for next time.
# A machine with a public address, two commands $ docker run -d --name hbbs --net=host \ rustdesk/rustdesk-server-oss hbbs -r relay.yourdomain.com $ docker run -d --name hbbr --net=host \ rustdesk/rustdesk-server-oss hbbr # Fill the server public key into both clients $ cat ./id_ed25519.pub OeVuKk5nlHiXp+AppNnWyYwf1yNnKy= ✓ Rendezvous ready · relay listening
Choose your system.
macOS 12.3+ · DMG DMG package. Not Developer ID signed or notarized; read the release notes before installing. Windows x64 · Portable
Standalone EXE Currently unsigned; Windows may show a security notice. Installation notes are on the release page. Android ARM64 · Controller
Release-key signed APK Connect to your computer from your phone. Remote control of the phone is not supported.
Changes, compatibility and known limitations: release notes · Try the nightly preview · Platform support
Before you begin,
let's be clear.
A few limitations, stated up front. Also the questions we hear most.
Do I need my own server?+
Do downloaded updates install automatically?+
Can I control an Android phone remotely?+
How is NikoDesk related to RustDesk?+
NikoDesk · Remote desktop on your own server