For every WordPress site

One panel, no inbound.

Install Remotera WP and watch health, updates, security and backups across your fleet. The panel never connects to your site — data arrives signed by the agent.

0 inbound connectionsArchitecture
256-bit command signaturesSecurity
300s default heartbeatAgent
10 min to set up a siteInstall
24/7 external uptime probesUptime
1 plugin per siteAgent
3 steps to first snapshotSetup
100% signed commandsProtocol
Capabilities

Health, updates, security
and backups in one place.

01

Site inventory

PHP version, disk usage, cron schedules and database size for every site, each value stamped with the moment it was read.

02

Update control

Core, plugin and theme updates are queued from the panel and carried out by the agent on its next check-in.

03

Uptime probes

External checks watch every address, and a missed probe is reported separately from a silent agent.

04

Security findings

Vulnerabilities and hardening gaps ranked by severity, refreshed from a multi-source feed.

05

Restore on demand

Queue a restore from the panel; the agent pulls the snapshot from its signed URL and restores the site. No inbound connection is ever opened.

06

Client reports

Branded HTML or PDF reports for each client, built from the same readings the panel shows.

Process

Three steps.
First snapshot in minutes.

site.txt
1# panel → add site
2Site       acme-store
3Token      ••••••••••••••••••••
4Inbound    none
Awaiting the agent — nothing is guessed
Architecture

The agent calls.
The panel listens.

No inbound connections, no stored WordPress password, no assumptions. The plugin on each site starts every exchange and pulls queued work from the panel.

0inbound connections
1outbound channel
5verification layers
Data freshness Sample reading
HeartbeatAgent signal 42s ago
InventoryPHP · disk · cron · database 6m ago
UptimeExternal probe 1m ago
Security feedVulnerabilities · hardening 12m ago
BackupEncrypted snapshot 3h ago
CronScheduled events unknown · data gap
Every value carries the moment it was read. Missing stays missing.
Operating principles

A missed heartbeat is not a healthy site.

The panel is built around one rule: missing data is never a good default. If a reading has not arrived, you see that — with its age — instead of a reassuring green tick.

RULE 01

Unknown stays unknown

A missing reading is marked as a gap, with the time it was last seen. It is never backfilled with a healthy value.

RULE 02

No admin password

The panel stores a site token, never your WordPress login. There is no credential to leak or rotate by hand.

RULE 03

No inbound connection

The agent starts every exchange. The panel has no route into your site, so there is no open door to defend.

RULE 04

No mutable reports

A report is frozen when it is generated. What your client opens is exactly what was measured.

Signals

Reads your stack.
Not your admin password.

Fourteen signal groups, collected on the site and delivered signed. No admin password, no agentless scanning, no inbound access.

Fourteen signal groups · inventory, uptime and security included No admin password stored · No inbound access
Security

Trust is
non-negotiable.

Every instruction is signed, every payload is replay-safe, and every backup is encrypted at rest. Security is a property of the protocol, not a setting you remember to turn on.

HMAC-SHA256 Signed commands Encrypted at rest EU hosted No inbound

Signed commands

Every queued command carries an HMAC-SHA256 signature. Unsigned or tampered payloads never run.

Replay protection

A one-time nonce and a dedup key mean a command runs at most once, even if it is delivered twice.

Encrypted backups

Snapshots and backups are encrypted at rest. Access happens only through the panel and its signed requests.

Frozen reports

A report payload is pinned at generation. The PDF your client opens cannot change afterwards.

Under the hood

Signed at the panel.
Verified at the site.

The protocol is deliberately small: an agent checks in, receives signed work, and reports what happened. No general-purpose runner, no remote code execution, no inbound tunnel.

HMAC-SHA256

Canonical JSON, signed on the panel and verified on the site.

Dedup key

At-most-once execution, even across repeated deliveries.

Pre-signed URLs

Restores are pulled by the agent, never pushed inbound.

PHP 7.4+ agent

WordPress 6.0 and newer. One plugin per site.

1// the agent starts the exchange
2POST /api/v1/agent/heartbeat
3Authorization: Bearer ••••••••••••
4 
5{
6 "agent_version": "1.2.0",
7 "protocol_version": 1,
8 "blocks": [ … signed readings … ]
9}
FAQ

Everything you need
to know about the panel.

Still deciding? These are the questions that come up before the first site is connected.

01 Does the panel connect to my WordPress sites?
No. The agent starts every exchange: it sends signed snapshots and pulls queued commands. The panel never opens an inbound connection to your site.
02 How are commands authenticated?
Every command carries an HMAC-SHA256 signature and a dedup key. The agent ignores unsigned or replayed payloads, so only instructions queued in the panel run.
03 What happens when a site goes silent?
Heartbeat and uptime are separate signals. Missing readings are marked unknown with their data age — an empty value is never shown as healthy.
04 Where do backups go, and who restores them?
Backups are encrypted at rest in Remotera’s storage. Restores are started by the agent from a pre-signed URL — the panel never opens a connection to your site.
05 Do I need to host the panel myself?
No. The panel runs on Remotera’s infrastructure; you sign in at backoffice.remotera.uk. Only the plugin is installed on each WordPress site, and it connects outbound.
Stack

Trusted by
forward-thinking teams.

The tools behind Remotera, chosen for speed, reliability and a small operational surface.

GoAgent & workers
ReactPanel interface
TypeScriptShared contracts
DockerReproducible deploys
PostgreSQLPrimary datastore
RedisQueues & cache
ElasticsearchSearch & logs
GeminiModel routing
OpenAIModel routing
ClaudeModel routing
GitHubSource & CI
CloudflareEdge & DNS
LinuxRuntime
WordPressThe site
S3Encrypted backups

Your sites keep running.
The panel keeps watching.

Signed, timestamped, never assumed healthy. Add the first site in about ten minutes and see the readings arrive on their own.

No inbound connections · No WordPress admin password · EU hosted