REMOSSH — a Next.js browser IDE for servers you already control

[willyarisky]

Hi, I'm Willy, the maker of REMOSSH.

I built it because I kept needing to check a project or continue a long-running task on a VPS when I wasn't at my normal workstation. I wanted the server to remain the development environment instead of moving the project into a hosted container.

REMOSSH connects to a server over SSH/SFTP and puts a Monaco-style editor, terminal, Git controls, and port forwarding in the browser. It also detects tmux, with GNU screen as a fallback, so a build, test suite, or coding-agent session can survive a closed tab or a device change.

The web app is built with Next.js 15.5 and React 19. One of the more interesting UI problems has been treating the browser as disposable while keeping the state of the remote workspace understandable: reconnecting terminals, showing persistent sessions, and making it clear which work is still running on the server.

You can try it here: https://remossh.com/

There is a free plan for one active server connection. I'm affiliated with the product, and I'm mainly looking for blunt feedback on the first-server setup, reconnection UX, and what security information you would expect before connecting a non-production server.

[Raghuvaranlokati]

Hey, this is a really interesting project! I can see the appeal of exposing SSH and services through a browser—it's like a unified access layer for remote environments.

A few thoughts after looking at it:

UI/UX:

The interface looks clean and minimal, which is good for this type of tool

Maybe consider adding a quick search or filter to find servers/services faster as the list grows

Tooltips on the action buttons (connect, edit, delete) would help new users

Security concerns (since you asked for blunt feedback):

This is essentially a web-based SSH client with saved credentials, which makes it a high-value target for attackers

Have you considered integrating with existing SSH key management instead of storing passwords?

Are credentials encrypted at rest? It wasn't clear from the description

Adding 2FA or IP allowlisting would make this feel much more enterprise-ready

Potential use cases:

This would be great for small dev teams who need quick access to multiple staging environments

Could also be useful for support teams who jump between servers frequently

Nice work overall! The execution looks solid. Are you planning to open-source it or keep it private?