Clear visibility
Next.js 16
A fast interface that gives our team and clients a useful view of sites, health and activity.
Under the hood
Reliable technology, backed by people who own the outcome.
Pulse runs real hosting operations, so the architecture favours predictable workers, auditable actions, recoverable backups and infrastructure our team can support properly.
Infrastructure with context
The platform begins with the estate it is responsible for.
Pulse keeps infrastructure health and capacity close to the sites it supports. That gives the team a practical route from a customer report to the application, the node beneath it and the wider condition of the fleet.
- Operational state across managed nodes
- Capacity and resource context in one view
- A direct relationship between sites and infrastructure
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.
Clear visibility
SSL and edge context
Pulse keeps certificate, origin and cache context visible so the right checks happen quickly.
The surrounding layers
Hosting health is more than whether a server responds.
Runtime, routing, certificates, WordPress state and site-level checks all affect the customer experience. Pulse keeps those layers visible without turning them into separate products to operate.
DNS and routing
Cloudflare connection and domain context remain attached to the managed estate.
PHP and runtime
Runtime versions can be reviewed across the fleet instead of checked one site at a time.
Design principles
Clear, accountable and recoverable.
The service should make hosting safer and easier without hiding what happened. Every important action should be visible, attributable and supported by a recovery path.
Actions are audited
Long jobs run safely in the background
Backups are indexed and visible
Server actions execute locally
Important changes leave a clear record
A managed outcome
Technical detail should lead to a clearer service.
The value is not the number of checks on screen. It is that the right information reaches the team responsible for the outcome, with enough context to act and a clear record of what happened afterwards.