Statio Deploy

Deploy to your own server with a git push. No SSH, no open ports.

Documentation · Deploy your first app · How it works

Statio ships your Docker image to your own server with a git push. Your GitHub Actions workflow builds and signs the image. An agent on your server receives it, checks the signature against the repo you authorised, and recreates the container.

git push ─▶ CI builds and signs ─▶ agent on your server ─▶ deployed

• No SSH and no deploy port. CI reaches the agent over a private Tailscale network. The agent is not reachable from the internet.
• Signed deploys only. The agent verifies a keyless cosign signature before it runs anything.
• Domain and DNS in the same deploy. The agent configures NPMplus and Cloudflare with credentials the workflow never sees.
• One Actions step. Build, sign and deploy together. No deploy scripts.

Tailscale carries the deploy signal alone. Your app's public traffic takes the ordinary path, through a reverse proxy on 80 and 443.

On the server:

curl -fsSL https://statio.accentio.dev/install.sh | sudo sh

The installer detects your OS and architecture, downloads the binary from GitHub Releases, verifies its checksum, and writes it to /usr/local/bin/statio. You also need Docker on the server and a Tailscale account. In CI you install nothing; the Action downloads the binary.

sudo statio upgrade   # update the binary and restart the agent
sudo statio doctor    # check the environment

Three commands, once each:

sudo statio init server     # on the server: configure and start the agent
sudo statio app add api     # on the server: accept an app and pin its signer
statio init repo            # in your repo: write statio.yaml and the workflow step

Then set the two Tailscale secrets plus your app's secrets, and push. The tutorial covers every step, including the Tailscale console.

• Deploy your first app takes you from an empty server to a working push.
• How-to guides cover domains, secrets, rollback, dependencies and several servers.
• Reference documents statio.yaml, the CLI, the Action, the pipeline and every error code.
• Explanation covers the design and the security model.
• Contributing covers building, testing and proposing changes.

_{Made by accentiostudios.}