If you've built something — a CLI tool, a terminal app, a small utility — you can list it on Snaproot in three commands. GitHub Actions builds the binary. Snaproot distributes it. No servers to run, no infra to pay for.
Install the CLI, then authenticate with your GitHub account. Your browser will open automatically.
iwr -useb https://snprt.pages.dev/install.ps1 | iex
No PATs, no settings menus. One command and a browser click.
Run this inside your project folder. It asks a few questions and creates a snprt.yml manifest.
snprt init
The manifest declares your app's name, description, and what permissions it needs at runtime:
| Permission | Risk | Meaning |
|---|---|---|
| network | low | App makes HTTP/HTTPS requests |
| filesystem | low | App reads or writes files |
| environment_variables | low | App reads env vars |
| admin_rights | high | App needs elevated privileges |
Users see these before installing. Apps that need admin rights show a HIGH RISK warning.
From inside your project folder:
snprt push
This single command:
From Cargo.toml, .csproj, or snprt.yml — no argument needed.
Adds a GitHub Actions workflow to your repo that builds a native binary for Windows and Linux.
Creates a v{version} tag and pushes. GitHub Actions picks it up automatically.
GitHub Actions builds the binary, uploads it to GitHub Releases, and notifies the Snaproot registry. Your app is live.
namit/myapp, not someoneelse/myapp.
snprt init asks for your project type. Currently supported:
| Type | Build command | Targets |
|---|---|---|
| rust | cargo build --release | Windows, Linux |
| dotnet | dotnet publish (Native AOT) | Windows, Linux, macOS |
Anyone can install your app with:
snprt install yourusername/yourapp
The binary is downloaded directly from your GitHub Release, SHA-256 verified, and placed in
~/.snprt/bin/ — no admin password, no installer.