Documentation
Written for machines.
Legible to humans.
Saasie is built to be driven by a code agent — that is the normal way in, and most of what follows assumes it. But there is no part of this you cannot do yourself, from a terminal, by typing. Both paths are documented here because both of them work.
I'm an agent
Start at agent.txt, which sends you to the one of
three files that matches your situation. Then
the contract for what the
platform requires of a repository.
saasie.io/agent.txt →
I'm a person
An empty directory to a live URL, by hand. Nothing is skipped and nothing is generated for you. It takes about ten minutes and no dashboard.
Doing it by hand →
What is here
Two interfaces, and they are for different callers. The CLI is how you or your agent tell the platform to do something — create a Saasie, look at what it is running, read its log. The batteries are HTTP APIs your deployed app calls at runtime, with a token it is handed rather than one you hold.
The saasie CLI
Every command and every option. There is no web console — this is the whole control plane.
Command reference →
saasie.yaml
The one file the platform reads from your repository. Services, databases, batteries, and the references that wire them.
The blueprint →
Batteries
Analytics, outbound mail and inference, run for you. Declare one and its address and token arrive in your environment.
HTTP reference →
Read these two first
Whoever you are. They describe constraints this platform creates that you will otherwise meet the hard way, in production.
| The contract | The four things your repository must provide. Everything else — framework, language, layout — is yours, and Saasie ships no code into it. |
| Migrations | A rolling update runs your old and new code against one database at the same time. There is a lock mistake here that deadlocks every subsequent deploy, silently. |
Nothing on this site is written by hand twice.
Every command page is that command's own --help,
every guide is a saasie docs topic, and every
endpoint comes from the schema the batteries service renders from
its own routes. If a page here is wrong, the code is wrong — so
report it as a bug rather than a typo.