XPipe, a brand-new type of remote file browser and shell connection hub
Hey HN, I built this over the last year as I always wanted to have an easy file and terminal access to all of my servers, including containers and clusters that you normally can't connect to with existing solutions out of the box. At first glance it might not look very novel, but if you dig a little deeper, you will see that the entire foundation of how it communicates with remote systems is completely different from any other solution out there. What happens in the background can essentially be explained this way: It launches a local shell process like cmd, sh, etc. and in it executes a…
In plain words
XPipe is a remote file browser and shell connection hub that provides file and terminal access to servers, containers, and clusters. It uses a novel communication approach by launching local shell processes and routing connections through their standard input and output streams, automatically detecting remote environments and adapting its communication method accordingly. The tool is designed for developers and system administrators who need unified access to diverse remote systems that existing solutions cannot typically connect to out of the box.
written from the facts on this page · September 2026
From the sources
In the maker’s words, at launch
Hey HN, I built this over the last year as I always wanted to have an easy file and terminal access to all of my servers, including containers and clusters that you normally can't connect to with existing solutions out of the box. At first glance it might not look very novel, but if you dig a little deeper, you will see that the entire foundation of how it communicates with remote systems is completely different from any other solution out there. What happens in the background can essentially be explained this way: It launches a local shell process like cmd, sh, etc. and in it executes a command that opens a remote shell connection such as ssh user@host. All communication is then done through the stdin/stdout/stderr of that process. From there, it detects what kind of server and environment, e.g. shell type, os, etc. you have logged into and adjusts how it talks to the remote system. By then using file system related commands such as ls, rm, touch, etc. and its equivalents, it can realize a functional file manager that works on essentially every system without any protocol requirements. For other types of connections, it can just execute things like docker exec -i to open a shell into a container and work the same way. Right now it supports: - SSH by running your locally installed SSH CLI client - Docker, Podman, LXD, and Kubernetes containers - WSL, MSYS2, and Cygwin environments on Windows - Various other things like some VMs for VMware and Proxmox, but work is still going on on there This approach to delegate everything to your installed tools is also utilized for other tasks. That means that I can save a lot of development time while you can happily use the tools you are comfortable with in conjunction with XPipe. In fact, XPipe doesn't ship with any libraries or tools for remote shell connections, protocol handling, or terminal integration at all. It just delegates everything to your own text editor, terminal emulator, RDP clients, and more. Due to its nature, XPipe has to handle a lot of sensitive information like passwords, keys, and more. To tackle the topics of security and privacy, I put an emphasis on security settings and created a dedicated security page in the docs that should hopefully contain all relevant information. There is also a password manager integration, so you don't have to store any sensitive information in XPipe itself if you use a compatible password manager. As it is a common use case to synchronize connection information across many systems, e.g. your desktop at home and laptop for travel, there is also a git integration which allows you to have XPipe automatically synchronize all connection information with a remote git repository of your choice. It supports any git remote repository, advanced authentication measures like SSH auth, GPG signing, and more. You can also use this for collaboration if you're working in a team. The early stage development has been quite challenging as this new approach requires a completely new implementation, but I am confident that it's ready now. I appreciate any kind of feedback from you to guide me in the right development direction from here. Enjoy!
Does the same job
all alternatives →- XAXPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more2025 · xpipe.io · ▲175
Hey HN, I built XPipe as I always wanted to have an easy file system and terminal access to all of my remote systems, including containers, virtual machines, clusters, and more that you normally can't connect to with existing solutions out of the box. XPipe is a new type of connection hub that allows you to access your entire server infrastructure from your local desktop. It can make your life easier when working with any kind of servers by eliminating all the commonly tedious tasks that come up when interacting with remote systems, either from the terminal or from a graphical interface.…

- WAWarp, a Rust-based terminal2022 · warp.dev · ▲946
Hi HN community, I’m Zach, founder and CEO of Warp, and am excited to show you Warp, a fast Rust-based terminal that’s easy to use and built for teams. As of today, Warp is in public beta and any Mac user can download it. It works with bash, zsh, and fish. The terminal’s teletype-like interface has made it hard for the CLI to thrive. After 20 years of programming, I still find it hard to copy a command’s output; I always forget how to use `tar`; and I always have to relearn how to move my cursor. To fix fundamental accessibility issues, I believe we need to start innovating on the terminal,…

- SSSink – Sync any directory with any device on your local network2025 · github.com · ▲151
i made sink. it's a simple little tool that continuously syncs folders between 2 devices. no cloud, no email, flash drives, no bs. it just uses your local wifi. run it on your machines, tell them to trust each other, and you're set. and if you manage to edit the same file at once, it handles the conflict and saves both copies. for anyone who just wants to get files from point a to b without the headache. hope it makes your life a bit less annoying. github: https://github.com/sirbread/sink binary:…
- PAPypipe – A Python command-line tool for pipeline processing2023 · github.com · ▲213
pypipe is a command-line tool for writing data pipelines in Python. When working with data processing in the terminal, I often find myself wanting to pass the output of commands to Python for further processing. In such cases, one can either write one-liners or create regular Python scripts and connect them through pipes. However, using pypipe makes this process more convenient and efficient.
More dev tools this month
the category →



Open-source GTM skills for technical founders
Dev tools · 29d ago · gtmcofounder.com

OpenTrailPaper is open-source bike computer firmware for the LilyGO T5S3 4.7" E-Paper PRO. It supports offline maps, GPX routes, FIT recording and Bluetooth sensors.
Dev tools · 2d ago · opentrailpaper.com

Launched alongside, June 2024
the whole month →

La Growth Machine▲1,216Create personalized, multi-channel conversations at scale
AI · 2024 · lagrowthmachine.com


PyjamaHR▲1,132Hiring on autopilot. The AI applicant tracking system (ATS).
Work · 2024 · pyjamahr.com