hello-rawpair/index.html
<!doctype html><html lang="en"><h1> We built this together.</h1></html> Same shared
document
Your project. Your
people. Your server.
Build together,
on your own server.
A shared editor, a persistent terminal and private app previews. All in one workspace, on a Linux host you control.
Pre-alpha Ubuntu 24.04 / 26.04 · amd64 / arm64
One environment to work in. Fewer
things to explain.
An in-page illustration
Two people. One workspace.
Try a shared edit below.
Everything here stays in this page.
Change the heading. See both views update.
Illustration only. This changes text in this page and does not execute code or contact a workspace.
hello-rawpair/index.html
<!doctype html><html lang="en"><h1> We built this together.</h1></html> Same shared
document
Illustrated page heading
We built this together. Private preview
In RawPair, shared edits appear in both editors. Save the file and refresh its preview to see your running page change. This illustration updates instantly.
Shared terminal Scripted output
alex@hello-rawpair:~$ python3 -m http.server 3000 \
--bind 127.0.0.1 --directory hello-rawpair
Serving HTTP on 127.0.0.1 port 3000 ...
127.0.0.1 - - "GET / HTTP/1.1" 200 -
# Both participants see the same session. Pick up where you left off
The session stays.
Close your browser and reconnect to the running terminal. Your coworker shares the same tmux session and processes.
This output is scripted. No command is executed here.
Stopping a workspace ends its processes. Files remain; after starting it again, rerun your development commands.
Hello from our workspace
We built this together.
This page is running in our shared workspace.
Made by Alex + Sam A little idea, running
Open it together.
Register an application’s port and open its HTTPS preview. Private previews require workspace membership.
An owner can explicitly share an application publicly. That does not grant editor or terminal access.
This is an illustrated page, not a hosted application. It makes no request to a workspace backend.
An illustration of the workflow. No signup, no backend connection, no code execution.
Made for the work between people
Get on the same page.
Then build something.
Open the same files. See the same output. Spend your time on the next idea.
Find the bug together.
Reproduce it in the same environment. Edit the same files and inspect the same running processes, without passing terminal output back and forth.
Shared files & processesGive a coworker a way in.
Walk through a project side by side. Leave the terminal running, close the browser and reconnect to pick up where you left off.
Persistent sessionsMake a weekend of it.
Bring friends into a small project. Keep another project in its own workspace, with separate files, processes and application previews.
Independent projects01 / Make it yours
A server.
A shared starting point.
Install the native packages on a fresh Ubuntu host. The setup wizard prepares your login, local or remote access, and two workspace slots.
Trying it on this machine?
Choose local setup. Open the printed login URL in a browser on the host. Setup creates local HTTPS certificates and asks before adding their certificate authority to system and browser trust stores. You can choose manual import instead. Firefox and Chromium-based browsers are supported.
Bringing someone else in?
Choose remote setup. Prepare management and wildcard preview DNS, reachable HTTPS and trusted certificates first.
v0.0.6
Ubuntu 24.04 / 26.04 amd64 + arm64
sudo apt update
sudo apt install -y ca-certificates curl python3
mkdir -p ~/rawpair-install
cd ~/rawpair-install
curl --fail --show-error --location --proto '=https' \
--output install.sh \
'https://github.com/rawpair/rawpair/releases/download/v0.0.6/install.sh'
less install.sh
bash install.sh --version v0.0.6Inspect the script with less; press q to exit.
The installer downloads the matching RawPair and Orqos packages, verifies checksums and runs setup. Bash is required; your sudo password may be requested.
02 / Your first shared session
From “it runs”
to “we built it.”
Start with a tiny page, using the Python included in your native installation. Then invite someone to change it with you.
Follow the walkthroughEveryone joins your deployment. rawpair.dev does not host workspaces. The operator creates accounts and workspace owners add members.
-
Create a place to work.
Sign in, choose New project workspace and select an unused host slot. Create it, then choose Start / reconnect.
-
Serve a little page.
In the shared terminal, create the walkthrough’s
hello-rawpair/index.html, then run:python3 -m http.server 3000 \ --bind 127.0.0.1 \ --directory hello-rawpair -
See what you’re making.
Under Applications, register a private application named
webon port3000. Check the connection, then open its HTTPS preview URL. -
Bring a coworker.
On a remote deployment, the operator runs
sudo rawpair user add. Add that username under Workspace members and send the workspace URL. Edit, save and refresh the preview together.
A few things to know
Before you
pair up.
Pre-alpha. Self-hosted.
For people you trust.
Do I need Docker?
No. This installation uses native Ubuntu packages with a matching Orqos runtime. Docker is available as a separate backend, with its own setup guide.
Separate Docker setupWhat kind of host do I need?
Use a fresh Ubuntu 24.04 / 26.04 machine or VM on amd64 or arm64, booted with systemd and cgroup v2. You need an ordinary user with sudo, internet access, free service ports and a private network range that does not overlap your LAN or VPN. The installation guide lists the exact requirements.
Host requirementsDo I need to install a language toolchain?
The packages include the RawPair runtime and its dependencies. The first-workspace walkthrough uses the included Python. For your own projects, the operator installs shared language tools, or you install them in your workspace home. Workspaces have no sudo and no automatic language installer.
What happens when I close my browser?
Your running workspace and its processes keep going. Reconnect to return to the shared terminal. Stop workspace ends its processes and keeps its files; start it again and rerun your development commands. After a host reboot, workspaces start stopped and you restart them yourself.
Can someone join from another computer?
Yes. Choose remote setup with reachable management DNS, wildcard preview DNS, HTTPS and trusted certificates. The operator creates their login, then a workspace owner adds them as a member. Local setup is for a browser on the host; a .localhost link will point a coworker at their own computer.
Who can open an application preview?
Registered previews start private and require workspace membership. An owner can explicitly share an application publicly, then make it private again. Public sharing exposes that application to anyone who can reach its URL; editor and terminal access still requires membership. Remote networking and trusted TLS are required for people on other machines.
Who is this ready for?
RawPair is pre-alpha, intended for one Linux host and people you trust with a shared workspace. Start with a small project you can restore from backup, and share any setup or collaboration issues. This site does not host your workspaces or create accounts for you.
Good work is shared work.