Skip to content

Statio

Deploy to your own server with a git push. No SSH, no inbound deploy port. Signed deploys delivered over a private Tailscale network.

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, no deploy port

CI reaches the agent over a private Tailscale network. Your reverse proxy still serves the app on 80 and 443.

Signed deploys only

The agent verifies a keyless cosign signature before it runs anything.

Domain and DNS included

The agent configures NPMplus and Cloudflare during the deploy, with credentials the workflow never sees.

One Actions step

Build, sign and deploy in a single step. No deploy scripts.

On the server:

Terminal window
curl -fsSL https://statio.accentio.dev/install.sh | sudo sh
  • Deploy your first app walks 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: why Tailscale replaces SSH, and the security model.