Darwvin

Introducing RemoteOpsX: SSH, SFTP, tunnels and server health in one app

A MobaXterm alternative for Linux, RemoteOpsX puts SSH, SFTP, tunnels and server health in one desktop app. The Free plan covers up to three servers.

Published 10 min read

RemoteOpsX is a desktop app for SSH, SFTP, port forwarding, server health and runbooks. As of October 2026 it runs on Linux, with Windows in beta and macOS in preview, and an Android app is in preview. The Free plan covers up to three servers and does not ask for payment details.

One server, several windows

A routine fix on one production server often means juggling several tools. You open a shell to read the logs, copy a config file with an SFTP client, keep a database tunnel alive in a second terminal, and check load and disk space by hand. The steps for the restart live in a text file or in someone's head.

ssh deploy@web-01.example.com                                 # window 1: a shell
sftp deploy@web-01.example.com                                # window 2: a file transfer
ssh -N -L 5432:db-01.internal:5432 deploy@web-01.example.com  # window 3: a database tunnel

Each window keeps its own copy of the host name, user, port and key path. A tunnel lives in one terminal, and when it drops, the database client in another window just fails. None of this is broken, but it gets hard to keep straight once you have more than a handful of servers.

If you searched for a MobaXterm alternative for Linux, the main difference is where the tool runs. MobaXterm's site describes it as a "tabbed SSH client for Windows", and RemoteOpsX is a desktop app for Linux. If you are looking for a Termius alternative, the practical differences are platform coverage and where credentials live. Termius lists iOS among its platforms, and RemoteOpsX has no iOS app. Termius's site describes sync through an encrypted vault, while RemoteOpsX keeps credentials in your operating system's keyring. RemoteOpsX puts the terminal, the file browser, tunnels, health checks and runbooks in one app.

Who it is for

RemoteOpsX fits best when your workstation runs Linux and you already work in SSH every day. It suits an operator who moves between a handful of production and staging hosts, reaches some of them through a bastion, and wants file transfers, tunnels and health checks next to the terminal. If you are moving off a Windows tool such as MobaXterm, check first that your workstation runs Linux, because Linux is the platform to start with.

It is a poor fit right now if your workstation runs Windows or macOS and you need a fully released build, or if you want an iPhone or iPad client. Windows is in beta, macOS is in preview, and there is no iOS app.

What RemoteOpsX does today

These are the features the app has as of October 2026. Where a feature has a command-line equivalent, we show it, so you can check the behavior against tools you already know.

An SSH terminal with tabs and split panes

Open each server in its own tab, and split a tab into panes when you need one. A common layout is a log tail in one pane and a shell in the other, which is the same thing you would otherwise do with two windows.

An SFTP browser with a transfer queue

If you want an SSH client with SFTP in the same window, this is the part that replaces a second tool. Browse remote folders, move files in both directions and follow progress in a transfer queue. The OpenSSH sftp(1) manual calls the program "a file transfer program" that "performs all operations over an encrypted ssh(1) transport".

Local, remote and dynamic forwarding, with bastion routes

If you want an SSH tunnel manager rather than a script, this is the part to read. Local forwarding (-L) forwards connections from a port on your machine to a host and port on the remote side. Remote forwarding (-R) works the other way, from a port on the server back to your side. Dynamic forwarding (-D) makes ssh act as a SOCKS server on a local port. A bastion route follows the same idea as the -J option: ssh connects to a jump host first, then sets up a TCP forwarding from there to the final destination. The ssh(1) manual covers these options, and RFC 4254 section 7 defines the TCP/IP port forwarding messages underneath them.

ssh -L 8080:10.0.4.21:80 ops@bastion.example.com    # local forward
ssh -R 9000:localhost:3000 ops@bastion.example.com  # remote forward
ssh -D 1080 ops@bastion.example.com                 # SOCKS proxy
ssh -J bastion.example.com deploy@10.0.4.21         # jump host

Routes can also live in your OpenSSH config, which the app imports. The ssh_config(5) manual says that ProxyJump makes a connection to the jump host and then establishes "a TCP forwarding to the ultimate target from there":

Host bastion
    HostName bastion.example.com
    User ops
    IdentityFile ~/.ssh/id_ed25519

Host db-01
    HostName 10.0.4.21
    User postgres
    ProxyJump bastion

For the commands in more depth, read SSH port forwarding explained.

Agentless server health over SSH

If you want a server monitoring SSH client rather than a second dashboard, this is the part that matters. Health covers load, memory, disks, processes, listening ports and failed services, and the app reads them over SSH. "Agentless" means there is no agent to install on the server or keep updated. The commands below are the Linux commands an operator would type by hand to see the same categories.

uptime               # load averages
free -h              # memory and swap
df -h                # disk usage
ps aux --sort=-%cpu  # processes by CPU
ss -tlnp             # listening TCP ports
systemctl --failed   # failed systemd units

The app reports the same categories for each server, next to your session.

Runbooks that pause before risky steps

A runbook is a written list of steps you repeat, such as checking disk space, rotating logs or restarting a service. RemoteOpsX runbooks pause for confirmation before risky steps, so a restart waits until you confirm it. The outline below is illustrative. It shows the idea, not the app's file format.

Restart nginx on web-01 (illustrative outline)
1. Check free space on /var/log                   read only
2. Test the nginx configuration                   read only
3. Restart nginx                                  pauses for confirmation
4. Request the homepage and expect HTTP 200       read only

Credentials in the operating system's keyring

Passwords and other credentials go into the operating system's keyring: Secret Service on Linux, Keychain on macOS and Windows Credential Manager on Windows. The app's database holds only references.

The freedesktop.org Secret Service specification describes a collection as "a collection of items containing secrets". Apple's Platform Security guide says that keychain items are encrypted, and that the keychain "provides a secure way to store" short sensitive items such as keys and login tokens. Microsoft says Credential Manager "lets you view and delete your saved credentials for signing in to websites, connected applications, and networks".

Anyone who can use your unlocked session can use the keyring too, so lock your session when you step away.

Importing what you already have

RemoteOpsX imports your OpenSSH config, and it has readers for MobaXterm, Termius and Royal TS exports built from their published formats. Review the imported list before you connect to anything. Check host names, ports, user names, jump hosts and key paths, because an import can carry entries you no longer use, and a reader can only map what the export contains.

How the app and our service split the work

The app connects directly to your servers. Darwvin's service handles sign-in, subscriptions and device approval, and nothing else. Your server traffic does not pass through that service. Keep your usual habits anyway: key-based login, host key checks and a locked operating system session.

Platforms as of October 2026

PlatformStatusWhat it means for you
LinuxDesktop appThe platform to start with
WindowsBetaGood for testing; expect changes
macOSPreviewNot yet a fully released build
AndroidPreviewFeatures may change
iPhone and iPadNot availableThere is no iOS app

Status changes quickly during beta and preview, so check the product page before you plan a rollout.

Moving from another tool

  1. Save or copy your session list from the old tool. Keep your ~/.ssh/config as well.
  2. Import into RemoteOpsX: the OpenSSH config, or a MobaXterm, Termius or Royal TS export.
  3. Review the imported list before the first connection. Check names, ports, user names, jump hosts and key paths.
  4. Connect to one server that is not critical. Run the health check, then do one SFTP transfer.
  5. Keep the old tool installed until each critical server works from the new one.

Move one group of servers at a time, staging first and production last. The SSH config guide explains the directives in an OpenSSH config file.

Check these after any import, whichever tool produced it:

  • A user name carried over from an old profile that no longer exists on the server.
  • A jump host that is missing from the list, or listed under the wrong name, so the route fails.
  • Two entries for the same host with different ports, one of them stale.
  • A key path that still points to a file you have since replaced.

Start on the Free plan

The Free plan covers up to three servers and does not ask for payment details, so you can try the app on real work before you decide on a paid plan. Pick the three servers you touch most often, such as a web host, a database behind a jump host and a machine you use for batch jobs.

  1. Get the app for your platform from the product page.
  2. Sign in, and approve the device when the app asks.
  3. Import your OpenSSH config, or add your three servers by hand.
  4. Run a health check on one server, then open one tunnel and close it again.
  5. Use the documentation as your reference, and contact support if an import looks wrong.

Paid plans are listed on the pricing page. The alternatives page is where to compare the app with other tools.

What the app does not include yet

As of October 2026, RemoteOpsX does not yet offer single sign-on, an iOS app, a fully released macOS build or AI features. Windows is in beta, and macOS and Android are in preview, so expect changes on those platforms.

FAQ

Is RemoteOpsX free?

The Free plan covers up to three servers and does not ask for payment details. Paid plans are listed on the pricing page, so you can test the workflow on your own servers before you decide.

Does RemoteOpsX send my server passwords to Darwvin?

No. The app connects directly to your servers, and Darwvin's service only handles sign-in, subscriptions and device approval. Credentials are stored in your operating system's keyring, and the app's database holds only references.

Can I import sessions from MobaXterm, Termius or Royal TS?

Yes. RemoteOpsX has readers for MobaXterm, Termius and Royal TS exports built from their published formats, and it imports OpenSSH config. Review the imported list before you connect, because a reader can only map what the export contains.

Does RemoteOpsX run on macOS and Windows?

As a desktop app it runs on Linux today. As of October 2026 Windows is in beta and macOS is in preview, so neither is a fully released build. There is an Android app in preview and no iOS app.

Does RemoteOpsX replace a monitoring system?

No. The health view shows load, memory, disks, processes, listening ports and failed services, read over SSH. It is meant for an operator working in a session, not as a substitute for a dedicated monitoring system.

Does RemoteOpsX install software on my servers?

It does not install an agent. Server health is read over SSH, which is what agentless means here.

References

Get product news by email

We use your address only for these emails. The unsubscribe link is in every email. Read our privacy policy.