THE COMMAND LINE TOOL
One file,
then you’re set.
saasie is what your code agent uses to make a Saasie, push it, and watch it go live. It is a single file with nothing to install alongside it.
macOS & Linux
curl -fsSL https://saasie.io/install.sh -o install.sh
less install.sh
sh install.sh
Read it first — we would rather you did, and install.sh is about 130 lines of POSIX sh. It picks the right build, checks it against the published checksums, and puts it in /usr/local/bin or ~/.local/bin. In a hurry, curl -fsSL https://saasie.io/install.sh | sh runs the same script.
Then
saasie --version
saasie docs
saasie docs states what the platform asks of a repository, and nothing about how to build one. Point your agent at saasie.io/agent.txt and it knows the rest — whether it is building something new or deploying a project you already have.
You install it once. It checks for a newer version a few times a day and replaces itself, so there is nothing to keep up with.
OR TAKE THE FILE YOURSELF
- saasie-darwin-arm64 macOS, Apple silicon
- saasie-darwin-x64 macOS, Intel
- saasie-linux-x64 Linux, x86-64
- saasie-linux-arm64 Linux, arm64
- saasie-windows-x64.exe Windows, x86-64
Current version · SHA256SUMS — on macOS and Linux, chmod +x the file before running it. Worth saying plainly: those checksums are served from this host, so they catch a broken download, not a bad day at Saasie. What protects you in transit is TLS.
IF YOUR AGENT RUNS BEHIND AN ALLOWLIST
- saasie.io:443 the installer, the agent instructions, the downloads
- api.saasie.io:443 the control plane — every saasie command
- git.saasie.io:2222 the Git remote your agent pushes to
- *.saasie.app:443 your Saasie, so your agent can check it works
Nothing else needs to be reachable. If saasie.io is blocked there is no second source to fall back on — a good agent will tell you so rather than improvise. Works with your agent goes through it agent by agent: which ones need the network opening, which already have it, and which cannot do this at all.
NOW ASK FOR SOMETHING