v0.2.0 Public Beta

Self-hosted static releases, roll back in seconds.

Deploy a build directory to your own infrastructure with content-hash versions, preview URLs, and prod/beta environments. No build service — bring your own output.

Feels like a one-command CLI deploy, but you own the storage and domains.

  • One command release to prod/beta/preview
  • Incremental uploads via content hashes
  • Instant rollback by switching refs
Get Started
Install CLI: npm install --global sitepod Demo instance — data may be reset. Self-host for production.

CLI

Deterministic Output
zsh — deploy → preview → rollback
$ sitepod deploy --prod
◐Scanning ./dist
→12 new, 30 reused (71%)
✓Released to prod
url: https://acme.example.com

Engine

Immutable State
Control Plane (Refs)
prod
refs/heads/main
beta
refs/heads/dev
Data Plane (Snapshots)
c8f1a2... 2m ago
index.html e4b1...
app.js 92a8...
Content Addressable
e4b1...
HTML
92a8...
JS
7f2c...
CSS
SYSTEM ONLINE

Pointer-based releases. Rollback is a ref switch.

Positioning

2x2

A quick map of where SitePod fits among common static deployment workflows.

Directory upload
Git-driven
Platform-hosted
Surge
CLI uploads a folder
GitHub Pages / Cloudflare Pages
Git push builds & deploys
Self-hosted
SitePod
Directory-first with versioned refs
DIY CI + OSS/CDN
Custom scripts & pipelines

System Components

SitePod separates the Control Plane (API/Auth) from the Data Plane (Serving) to guarantee stability and performance.

Control Plane

  • Built-in Auth (PocketBase)
  • Environment Management
  • Preview URL Generation

Data Plane

  • Content-Addressed Storage
  • Caddy Web Server
  • Automatic SSL/TLS

Zero Dependencies

No Docker. No Kubernetes. Just one binary. Runs on any Linux VPS with 512MB RAM.