Crucible — Platform Support & Build Matrix

All artifacts autobuild in .github/workflows/build.yml. Every build step was verified locally before commit (PWA build, PyInstaller CLI binary, multi-arch Docker image + run).

What runs where

Platform Artifact Backend (control plane + GUI) Abliteration adapter (torch)
Windows 10 (11 intentionally NOT targeted) CLI .exe + Docker Desktop optional (pip install torch)
macOS (Intel + Apple Silicon) CLI binary + Docker ✅ (MPS)
Linux x86_64 (any distro) AppImage · .deb · Docker · CLI ✅ (CUDA/CPU)
Linux ARM64 / Raspberry Pi Docker arm64 · CLI arm64 CPU only / use a GPU node
Kali · Whonix · Tails · forks AppImage · .deb · Docker optional
Android Capacitor APK thin client → remote node n/a
iOS Capacitor archive thin client → remote node n/a
Any browser / OS installable PWA thin client → remote node n/a

Two tiers, by design

"All Linux distros" — by format, not allowlist

There is no verifiable public list of distros that have "promised to refuse age verification" — age verification is an app/website/jurisdiction-level concern, not something baked into a Linux distro. So Crucible ships in universal portable formats:

This covers every Linux edition — current, privacy-focused, or a fork released tomorrow — without tracking anyone's policy stance.

Build it

# locally
docker build -t crucible . && docker run -p 8400:8400 crucible    # backend + GUI, any OS w/ Docker
bash packaging/build_appimage.sh                                  # portable Linux (CI/Ubuntu)
pyinstaller --onefile --name crucible --paths backend packaging/cli_main.py   # native CLI

# in CI: push to main or tag v* → all platforms build & attach to the release