Push anything, get a built artifact back, with the logs in a web page.
saggar is a build engine: hand it a git URL, a tarball or a path, and it works out what to build, builds it in a disposable environment, and streams the logs while it runs. Green artifacts come back as registries. docker pull and apt install address the store directly. saggar.dev builds nothing itself: you pair your own runners (a home PC, a workstation, a fleet) and the hub coordinates while your hardware computes.
From the terminal
In the browser
Every format from one tree
One submission fans out per format and architecture: deb, rpm, snap, flatpak, AppImage, container. The jobs land as one group.
Logs while it builds
Every phase streams its output as it happens; a failure names the phase, the exit code and the log tail.
Your own registries
Green artifacts are served back where they land: docker pull and apt install address the store directly, multi-arch through one tag.
Builds on push
Watches poll a repo and take forge webhooks; a push matching a branch or tag glob becomes a job, with commit status reported back.
Tests gate the green
The same pipeline runs the tree's own suite; structured results name the failing cases, no log scraping.
One box or a fleet
Your machines do the building: workers pull jobs from a hub, so no inbound ports and NAT are fine, while a single process runs the whole pipeline alone.