Back to Latest Release
Clockwork Control Engineering Log
v1.2.0Sep 4, 2026•6 min read

Clockwork Control v1.2.0: The Modular Architecture Overhaul & Backup Relays

We built Clockwork Control to escape bloated legacy fleet managers like ManageWP. In v1.2.0, we completely rebuilt our core around a pluggable modular architecture, plus air-gapped S3 backup relays and ICANN domain tracking.

AR
Aaron Reimann
Founder & Lead Architect • Clockwork Web Dev
#Releases#Architecture#Modules#Backups

I’ve been managing WordPress client hosting since 2004. Over the last two decades, I’ve used almost every fleet management tool on the market: ManageWP, InfiniteWP, MainWP, WPMU DEV Hub, and half a dozen custom scripts in between.

Like a lot of agency owners, I got tired of the SaaS subscription tax. Paying $2 to $5 per site every single month just to monitor uptime and trigger updates on 200 sites adds up fast. But even worse than the price was the software bloat: monolithic dashboards filled with features we never asked for, slow database queries, and zero ability to customize the platform for how our team actually works.

When we started building Clockwork Control, the goal was simple: build a fast, modern, self-hosted command center for WordPress agency owners.

In Clockwork Control v1.2.0, we laid the cornerstone of that vision by introducing our Pluggable Modular Architecture.


1. Escaping the Monolith: Pluggable Modules

In most agency tools, every feature is hardcoded into the core application. Even if you never use Hetzner, Twilio, or Bill.com, those tables, background jobs, and navigation tabs sit in your database forever.

In v1.2.0, we rewrote Clockwork Control so that almost everything is an isolated, toggleable module:

┌────────────────────────────────────────────────────────┐
│                   CLOCKWORK CONTROL CORE               │
│         Sites Fleet • Servers • Users • Permissions     │
└───────────────────────────┬────────────────────────────┘
                            │
        ┌───────────────────┼───────────────────┐
        ▼                   ▼                   ▼
┌───────────────┐   ┌───────────────┐   ┌───────────────┐
│ Hosting Panel │   │ Backup Relay  │   │ Notifications │
│  • SpinupWP   │   │  • S3 Bucket  │   │  • Slack      │
│  • GridPane   │   │  • DigitalOc. │   │  • Mattermost │
│  • Pressable  │   │  • Glacier    │   │  • Mailgun    │
└───────────────┘   └───────────────┘   └───────────────┘

Why Modular Design Wins for Agencies

  • Pick and Choose Only What You Use: If you host on GridPane and use Slack, you enable those two modules. Pressable, Hetzner, Cloudways, and Twilio stay completely disabled.
  • Zero Database Bloat: Disabled modules don’t register cron workers, don’t ping external APIs, and don’t render menu items.
  • Isolate Failures: If an upstream API provider experiences an outage, that module fails gracefully in its own sandbox without taking down your entire command center.

2. Central Operations & Settings Hub

Once we moved to a modular structure, we needed a fast, intuitive way to configure everything. We built the Settings Hub (/settings):

  • Instant Search Across Settings: Need to find where to paste an S3 secret key or adjust cron timeouts? Just type in the search bar.
  • Clean Two-Tier Navigation: Easily switch between Operations, Hosting Panels, Notifications, Security Feeds, and System Updates.
  • Module Status Badges: See which modules are active, verified in production, or waiting for API credentials at a single glance.

3. The DigitalOcean Backup Relay & S3 Air Gap

One of the biggest security mistakes I see agencies make is running backups that push directly from client WordPress servers straight to an AWS S3 root bucket using credentials stored in wp-config.php.

If a client site gets compromised through an outdated plugin, the attacker finds those AWS keys in the database or config file and can delete your entire backup bucket.

In v1.2.0, we introduced the DigitalOcean Backup Relay Architecture:

[Client WordPress Site] 
        │ (Local database & file dump)
        ▼
[Encrypted SSH / Relay Push]
        │
        ▼
[Clockwork Control Backup Relay Droplet]
        │ (Verifies HMAC signature, validates checksum)
        ▼
[Private S3 Bucket with Object Lock / Air Gap]

Client sites never have direct write or delete permissions on your master S3 archive. All dumps route through the Relay Droplet, which verifies the payload before cold-storing it. If a site gets hacked, your offsite backups remain 100% untouched and safe.


4. ICANN RDAP Domain Expiration Tracking

How many times has a client’s website gone down, not because the server crashed, but because their marketing manager left the company and the domain registration expired without anyone noticing?

v1.2.0 integrates direct ICANN RDAP Domain Tracking:

  • Monitors registrar expiration dates for all client domains automatically.
  • Alerts your team at 60, 30, and 7 days before expiration.
  • Prevents the nightmare of losing a client’s domain name to domain squatters.

The Foundation is Set

v1.2.0 was the release where Clockwork Control stopped being an internal script and became a true, extensible open-source platform.

You can update anytime with:

php artisan clockwork:update

Thanks to everyone who has given feedback so far. There’s a lot more coming!

Published for Clockwork Control operators
View on GitHub

Other Major Releases

Chronological changelogs and architectural deep dives

v1.11.0Oct 14, 2026

Clockwork Control v1.11.0 introduces the Email Auth Client Notice Composer for 1-click white-labeled client deliverability notices, full inline monthly Client Report emails with embedded brand logos, chronic server saturation detection with trailing 48-hour spike tracking, and robust AiRemedy autonomous healing resilience.

v1.10.1Oct 4, 2026

Clockwork Control v1.10.1 delivers drag-and-drop reorderable site settings module cards with asynchronous persistence, the complete sunsetting of the legacy LLAR module in favor of native Gatekeeper, server fleet UI simplifications, mobile navigation icon color consistency, and scheduled job recording reliability fixes.

v1.10.0Oct 3, 2026

Clockwork Control v1.10.0 is officially released! Featuring the new EmailAuth module (RFC 7208 SPF lookup limits & void tracking, RFC 7489 DMARC enforcement, multi-selector DKIM probing via Cloudflare/Google DNS-over-HTTPS), 28-day real-user Core Web Vitals field data from Google CrUX, AiRemedy diagnostic accuracy scorecards with automated 60-minute resolution outcomes, plugin update failure streaks, settings card reordering, and client uptime alert subscribers via SMS & transactional email.

v1.9.0Sep 29, 2026

We tagged Clockwork Control v1.9.0. Introducing AiRemedy—our autonomous server incident triage and self-healing engine powered by Claude Sonnet 4.5 via OpenRouter—along with universal ⌘K QuickJump search, fleet update & reboot history, in-app visual feedback pins, and module security hardening.

v1.8.1Sep 27, 2026

We tagged Clockwork Control v1.8.1. We completed our migration away from WordFence Login Security and Limit Login Attempts Reloaded to our native Gatekeeper engine—eliminating client scare tactics and ads—while shipping a modular TypeScript frontend, bundled ECharts, and sub-4s developer gates.

v1.7.0Sep 13, 2026

We just tagged v1.7.0. It prepares Clockwork Renegade for eventual submission to the WordPress.org Plugin Directory (currently in active fleet testing before submitting) with a 256-bit Connection Key, plus a visual Scheduled Jobs dashboard so you finally know what your cron queue is doing.

v1.6.0Sep 11, 2026

We tagged v1.6.0 with native Vultr cloud compute discovery and a huge fix for GridPane API rate-limiting, thanks to a great community PR from Karena Kreger (@karenalenore).

v1.5.0Sep 10, 2026

v1.5.0 fixes one of the most annoying problems in WordPress care plans: false downtime alarms during plugin updates. Plus offsite S3 Glacier cold-storage backup relays and security hardening.

v1.4.0Sep 8, 2026

When you manage 100+ WordPress sites, scrolling through tabular lists causes cognitive fatigue. v1.4.0 introduces the Visual Fleet Grid with automated headless screenshots, draggable dashboard cards, and native authentication.

v1.3.0Sep 6, 2026

Clockwork Control started with deep SpinupWP roots. In v1.3.0, we did the hard work of completely decoupling core infrastructure to support true multi-host WordPress fleets, plus automated monthly client reports.

Clockwork Web Dev
Brought to you by Clockwork Web Dev

A real WordPress development agency building battle-tested operational tooling to run client fleets with zero bloat and total control.

Visit Clockwork Web Dev→