Operator UI
Next.js 16
Fast technician-facing app with server-rendered pages where possible and focused client interactivity where needed.
Under the hood
Built deliberately boring where it matters.
Pulse runs real hosting operations, so the architecture favours predictable workers, auditable actions, easy backups and infrastructure you can reason about.
Long-running tasks
PHP workers
Backups, syncs, updates, smoke tests and operational jobs run outside the request path.
Panel state
SQLite
Simple, boring and easy to back up at BMT scale. We do not add database complexity for theatre.
On-server execution
Per-host agent
Each managed server performs local actions through an authenticated HTTPS agent instead of brittle remote shell glue.
Off-site backups
Wasabi / S3
Backups live in object storage with a visible index and restore history.
DNS and SSL
Cloudflare API
DNS records and Let’s Encrypt DNS-01 challenges are driven from the same operational context.
Design principles
Control plane, not magic box.
Pulse should make hosting operations safer and quicker without hiding what happened. Every important action should be visible, attributable and recoverable.
Actions are audited
Long jobs run as workers
Backups are indexed
Agents execute locally
Self-hosted direction stays open