Getting it

No download button.
Two commands instead.

Packaging, code signing and auto-update aren't built yet, so there is no installer to give you -- and a "Download" button that hands you an unsigned binary your OS then refuses to open isn't a favour. Here's what genuinely works today.

Run it from source

One dependency, no native modules, nothing to compile. npm install pulls the Electron runtime once -- it's a large download -- and then it starts.

1

Get the source

git clone https://github.com/MIR-2025/splitser.git
cd splitser
2

Install and start

npm install
npm start

That's the whole build. The only dependency is electron.

3

Or keep it running after you close the terminal

./splitser          # start, detached
./splitser status
./splitser stop
./splitser restart

The bundled launcher starts the app in its own session, so closing the terminal doesn't take it with you.

About the --no-sandbox flag

npm start passes --no-sandbox, and you should know why: an npm-installed Electron ships chrome-sandbox without the SUID-root bit on Linux, so it won't launch otherwise. It's a development convenience, not the shipping configuration -- a packaged build sets the helper up properly and drops the flag.

Where each platform actually stands

It's one Electron codebase with no per-OS forks, so all three should work. Only one of them has actually been run, and it would be dishonest to present the other two as equal.

Linux

Verified

Developed and verified

Built and run daily on X11 / XFCE.

Minimum Modern glibc (~Ubuntu 20.04+ or equivalent), X11 or Wayland

macOS

Untested

Should run -- not yet built or tested

Same codebase, no per-OS fork. Nobody has run it there yet, so it is unproven.

Minimum macOS 11 (Big Sur) or newer

Windows

Untested

Should run -- not yet built or tested

Same codebase, no per-OS fork. Nobody has run it there yet, so it is unproven.

Minimum Windows 10 or newer (x64 / arm64)

Minimums track Electron 32 / Chromium 128. Pinning a different Electron for release moves these floors.

What it needs, and where it puts things

Runtime
Electron ^32 (Chromium ~128) -- that is the whole runtime
Dependencies
One: electron. No native modules, so nothing compiles per platform
Network
None of its own. No server, no backend, no account, no sync, no telemetry
Your data
~/.config/splitser · ~/Library/Application Support/splitser · %APPDATA%\splitser

That directory holds history.json, bookmarks.json, session.json and settings.json as plain readable JSON, plus vault.enc as AES-256-GCM ciphertext. Back it up or delete it; it's your data and it never leaves the machine.

What isn't built

Stated as plainly as the feature list, so you can tell which is which.

Installers

Signed, packaged builds -- AppImage and .deb, a notarized .dmg, a signed Windows .exe -- plus auto-update. Until then it runs from source.

2-D splits

The grid is columns only today. Rows within a column are next.

Workspaces

Named, saved pane layouts you can switch between.

Ad-block and extensions

Electron loads unpacked Chrome extensions with only partial API coverage, so no promises of uBlock-grade blocking.

Autofill on submit

The vault captures a login on request today; offering to save it when you submit a form is still to come.

Mobile

Desktop only. There is no mobile build and none planned yet.

Want the short version?

It tiles real browser panes, it fills your passwords, it keeps everything on your machine, and you have to build it yourself for now.

See what it does