Your entire server infrastructure at your fingertips
XPipe is a new type of shell connection hub and remote file manager that allows you to access your entire server infrastructure from your local machine. It works on top of your installed command-line programs and does not require any setup on your remote systems. So if you normally use CLI tools like ssh
, docker
, kubectl
, etc. to connect to your servers, you can just use XPipe on top of that.
XPipe fully integrates with your tools such as your favourite text/code editors, terminals, shells, command-line tools and more. The platform is designed to be extensible, allowing anyone to add easily support for more tools or to implement custom functionality through a modular extension system.
It currently supports:
Note that this is a desktop application that should be run on your local desktop workstation, not on any server or containers. It will be able to connect to your server infrastructure from there.
Installers are the easiest way to get started and come with an optional automatic update functionality:
You can also install XPipe by pasting the installation command into your terminal. This will perform the .msi setup for the current user automatically:
powershell -ExecutionPolicy Bypass -Command iwr "https://github.com/xpipe-io/xpipe/raw/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1"
If you don’t like installers, you can also use a portable version that is packaged as an archive:
Alternatively, you can also use the following package managers:
choco install xpipe
.winget install xpipe-io.xpipe --source winget
.You can install XPipe the fastest by pasting the installation command into your terminal. This will perform the setup automatically.
The script supports installation via apt
, dnf
, yum
, zypper
, rpm
, and pacman
on Linux:
bash <(curl -sL https://github.com/xpipe-io/xpipe/raw/master/get-xpipe.sh)
Of course, there are also other installation methods available.
The following debian installers are available:
Note that you should use apt to install the package with sudo apt install <file>
as other package managers, for example dpkg,
are not able to resolve and install any dependency packages.
The following rpm installers are available:
The same applies here, you should use a package manager that supports resolving and installing required dependencies if needed.
There is an official AUR package available that you can either install manually or via an AUR helper such as with yay -S xpipe
.
There’s an official xpipe nixpkg available that you can install with nix-env -iA nixos.xpipe
. This one is however not always up to date.
There is also a custom repository that contains the latest up-to-date releases: https://github.com/xpipe-io/nixpkg.
You can install XPipe by following the instructions in the linked repository.
In case you prefer to use an archive version that you can extract anywhere, you can use these:
Alternatively, there are also AppImages available:
Note that the portable version assumes that you have some basic packages for graphical systems already installed
as it is not a perfect standalone version. It should however run on most systems.
Installers are the easiest way to get started and come with an optional automatic update functionality:
You also can install XPipe by pasting the installation command into your terminal. This will perform the .pkg
installation automatically:
bash <(curl -sL https://github.com/xpipe-io/xpipe/raw/master/get-xpipe.sh)
If you don’t like installers, you can also use a portable version that is packaged as an archive:
Alternatively, you can also use Homebrew to install XPipe with brew install --cask xpipe-io/tap/xpipe
.
Prior to major releases, there will be several Public Test Build (PTB) releases published at https://github.com/xpipe-io/xpipe-ptb to see whether everything is production ready and contain the latest new features.
In case you’re interested in trying out the PTB versions, you can easily do so without any limitations. The regular releases and PTB releases are designed to not interfere with each other and can therefore be installed and used side by side.
XPipe is a desktop application first and foremost. It requires a full desktop environment to function with various installed applications such as terminals, editors, shells, CLI tools, and more. So there is no true web-based interface for XPipe. Since it might make sense however to access your XPipe environment from the web, there is also a so-called webtop docker container image for XPipe. XPipe Webtop is a web-based desktop environment that can be run in a container and accessed from a browser via KasmVNC. The desktop environment comes with XPipe and various terminals and editors preinstalled and configured.
XPipe follows an open core model, which essentially means that the main application is open source while certain other components are not. This mainly concerns the features only available in the homelab/professional plan and the shell handling library implementation. Furthermore, some CI pipelines and tests that run on private servers are also not included in the open repository.
The distributed XPipe application consists out of two parts:
Additional features are available in the homelab/professional plan . For more details see https://xpipe.io/pricing.
If your enterprise puts great emphasis on having access to the full source code, there are also full source-available enterprise options available.
You have more questions? Then check out the FAQ.
For information about the security model of XPipe, see the security page.
For information about the privacy policy of XPipe, see the privacy policy.
In case you’re interested in development, check out the contributing page.