DEV Community

Hironobu Tozuka
Hironobu Tozuka

Posted on

I built a cross-platform remote access tool because I wanted unlimited remote sessions

#showdev #productivity #remotedesktop #security

I’m an independent developer building FlashDesk, a cross-platform remote access tool for Windows, macOS, and Linux.

Website: https://flashdesk.io/

The reason I started building it was simple: I wanted a remote access tool that I could use freely across multiple machines, multiple windows, and multiple sessions without running into artificial limits.

Most remote access tools work well for one simple connection. But once I wanted to monitor multiple remote machines, open several viewer windows, switch between remote desktop and SSH, transfer files, or keep a record of what happened during a session, the workflow started to feel fragmented.

So I started building FlashDesk.

What FlashDesk does

FlashDesk combines several remote access features into one app:

  • Remote desktop
  • SSH
  • File transfer
  • Chat
  • Connection management
  • Session recording and playback
  • Multiple remote viewer windows
  • Windows / macOS / Linux support

The goal is not just to make another remote desktop app.

The goal is to make a practical tool for developers, IT support, remote maintenance, and people who often need to work across multiple machines.

Why I think multiple sessions matter

A lot of remote access workflows are not just “connect to one PC and fix one thing.”

Sometimes you want to:

  • monitor several remote machines at once
  • keep one remote desktop open while using SSH on another machine
  • compare behavior across multiple environments
  • support more than one user or device
  • watch logs, terminals, and GUI apps at the same time

That is why I wanted FlashDesk to make multiple remote windows and sessions feel natural instead of treating them as an edge case.

Trust is the hardest part

Remote access software is sensitive.

Asking someone to install a tool that can view or control a computer is a much higher trust barrier than asking them to try a note-taking app or a small CLI tool.

Because of that, I’ve been working on making the security and connection model as clear as possible.

Security page:
https://flashdesk.io/security.html

I’m trying to explain things like:

  • how connections are established
  • when direct connections are used
  • when relay servers may be used
  • what kind of data is handled by the server
  • how distributed apps are signed
  • what users should check before trusting the software

I still think this part is difficult. Too little information looks suspicious, but too much technical detail can become unreadable.

What I’m looking for

I’m mainly looking for feedback from developers, sysadmins, IT support people, and power users.

I would especially appreciate feedback on these points:

  1. Does the website look trustworthy enough for a remote access tool?
  2. Is the security explanation clear?
  3. Is the positioning understandable compared with tools like AnyDesk, TeamViewer, RustDesk, or Remote Desktop?
  4. What would stop you from trying it?
  5. Are there any features you would expect from this type of tool?

You do not need to install it if you are not comfortable testing remote access software from an independent developer.

Even feedback on the website, wording, security page, or product positioning would be useful.

FlashDesk:
https://flashdesk.io/

Thanks for reading.

Top comments (0)