Deploy your team's small apps to one server you own.

Everything a small app needs

Deploying, signing in, sharing, backups and monitoring come built in, on a machine you own.

• $ sitesolide deploy

  -> project my-app, service

  -> application code

  -> Caddy fragment, through the validated path

  -> verify

  https://my-app.example.com/ 200

  my-app.example.com 200

  Deploy in one command

  Run sitesolide deploy in a folder: a static site, or an app in Bun, Node, Python, Go or any binary. It builds, installs, restarts, then checks the app answers on HTTPS.

• Caddy*.example.com

  my-app.example.com notes.example.com app.acme.comown domain

  webcx23 · fsn1 · debian-13

  memory34% disk21% load0.18

  my-app24 MB notes31 MB crm27 MB docsstatic

  systemd · no containers

  A server you own

  One machine you rent, at Hetzner or any Debian 13 server. Caddy serves every app on HTTPS, at its own subdomain or on your domain, and systemd runs them. Apps, data and secrets stay on it: no containers, no per‑seat bill.

• Google Workspace Microsoft Entra Okta OpenID Connect my-app Sign in with Google

  Your company's sign-in

  Google Workspace, Entra, Okta or any OpenID Connect provider in front of private apps, which write no sign-in code and learn who came in.

• Share my-app

  alice@acme.comShare

  Aalice@acme.comperson

  Everyone at acme.comdomain

  $ sitesolide share alice@acme.com

  Shared like a doc

  Open an app to a colleague by their work email, or to everyone at your domain, from the CLI or the dashboard. It holds from their next request.

• sst_••••••••••••••••••••••••••••

  Alice's laptopActive

  alice@acme.com

  Private sites onlyCreates projects

  my-app (created), notesRevoke

  Team tokens, not root SSH

  Colleagues and agents deploy over HTTPS with a personal token, scoped and revoked in one click. Only the owner holds SSH.

• Backupsmy-app

  24 h agonow

  14:03ScheduledRestore

  13:04Scheduled2.4 MB

  12:41Before restore2.3 MB

  Hourly backups

  Each project's data snapshotted hourly, SQLite copied consistently, optionally to an encrypted bucket. Restore from the dashboard.

• $ sitesolide deploy --json

  {"type":"step","message":"project my-app, service"}

  {"type":"step","message":"Caddy fragment, through the validated path"}

  {"type":"step","message":"verify"}

  {"type":"result","ok":true,"command":"deploy","slug":"my-app","kind":"service","dryRun":false,"url":"https://my-app.example.com/","status":200}

  {"type":"error","message":"secret missing on the server: /etc/sitesolide/my-app.env","hint":"ask the owner to create this file and its variables in the dashboard's Secrets section, then run deploy again; never put secret values in the repository"}

  sitesolide mcp

  detect deployask status logs sharing shareask lock_status

  /llms.txt

  # sitesolide

  > deploys a team's small software to one Debian server

  ## Docs

  - [Agents](docs/agents.md): the --json events

  - [The manifest](docs/manifest.md): every key

  Built for agents

  Every command speaks --json, one event per line, each error with a hint. sitesolide mcp serves deploy, logs and sharing to Claude Code, Codex or Cursor, and llms.txt indexes the docs.

• Checksevery minute

  my-app.example.com

  notes.example.com

  example.com

  sitesolide monitor, example.com: 1 downDOWN https://my-app.example.com/ answered 502

  sitesolide monitor, example.com: 1 recoveredRECOVERED https://my-app.example.com/ answered 200 (after 8 min)

  Heartbeatpinged every minute

  A monitor that tells you

  Every site checked each minute: one message to Slack, Discord, Google Chat or ntfy when it goes down, one when it recovers. A heartbeat notices the machine itself dying.