A custom Puppy Linux variant built from Ubuntu Jammy packages. No tray, no panel, no clutter, just a fast, low-footprint desktop for hardware everyone else gave up on.
A tuned JWM setup with the traditional panel and tray removed entirely, just a themed desktop and a real terminal, nothing sitting idle in the background.
A GTK3 application launcher and a taskbar written from scratch for Vantum in python, built to replace the taskbar rather than imitate it. Still under active development.
Binary compatibility with Ubuntu 22.04 LTS — install most Ubuntu software without friction, through a package manager that's been fixed to actually work.
Thunar, urxvt, epdfview, galculator, GParted. System necessities
are just shell scripts in gtk-dialog
File manager. Handles mounting, browsing, and basic archive extraction without pulling in a full desktop stack.
The default terminal. Lightweight, customized for ease of use.
Lightweight PDF viewer, GTK-based. No Motif, no dated toolkit look.
Modern enough to handle most websites, ligthweight enough to feel fast
Basic and scientific calculator, GTK, small footprint.
Partition editor. GTK-only, no GNOME desktop dependency despite the name.
Most Puppy variants keep the traditional desktop shell. Vantum rebuilds the shell itself — no tray, a custom launcher, and a package manager that's actually been debugged end to end.
It's a 0.01 Beta. Core system and package management are solid; the desktop shell (Vantask, Conky) still has open bugs listed in the roadmap above.
Old, low-spec machines — the kind most modern distros have quietly stopped supporting well.
Not automatically yet — that's the single biggest item left before 1.0. See the roadmap.
Vantum is a custom Puppy Linux build assembled using Woof-CE against Ubuntu Jammy packages. The entire build process (including every failure and fix) is documented in the repository. This is a 0.01 Beta: persistence is still being built, and a couple of desktop-shell bugs are open. Not a finished product. A thing that's being made, in the open.
Read the debug log