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

Clockwork Control v1.3.0: Decoupling SpinupWP & Automated Client Reports

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.

AR
Aaron Reimann
Founder & Lead Architect • Clockwork Web Dev
#Releases#Architecture#Reports#Multi-Host

When I first started sketching out Clockwork Control, I built it around the hosting stack we used every day at our agency: SpinupWP. It made total sense. SpinupWP is fantastic, their API is clean, and building around a single opinionated provider let us move fast.

But as our agency grew—and as other agency owners started testing Clockwork Control—reality hit: nobody runs 100% of their client sites on a single hosting platform.

Clients come to you with legacy sites on Pressable, WooCommerce stores on dedicated GridPane servers, or marketing sites on WP Engine. If our command center assumed every site followed SpinupWP directory structures and SSH conventions, it wasn’t a true fleet manager—it was just a SpinupWP dashboard.

In Clockwork Control v1.3.0, we did the heavy lifting to decouple core operations from SpinupWP and turn Clockwork Control into a true multi-host operational hub.


1. Provider-Aware Architecture & Decoupling

Here’s the thing about WordPress hosting: every host has its own opinions about where files live and how permissions work.

  • On SpinupWP, sites live in /sites/{domain}/files.
  • On GridPane, they’re in /var/www/{domain}/htdocs.
  • On custom Ubuntu VPS setups, you might find them in /var/www/html or /home/{user}/public_html.

In v1.3.0, we refactored our core models to be completely provider-aware:

// Provider-aware path resolution
$site->resolveWpPath(); 
// Understands SpinupWP, GridPane, Pressable, and custom conventions dynamically

What We Decoupled

  1. Daily Update Polling: Previously, daily plugin and theme update checks relied on SpinupWP’s API. In v1.3.0, update checks run directly via WP-CLI over SSH or through our Companion plugin, regardless of who hosts the server.
  2. SSL Live-Probing: Decoupled SSL certificate inspection from provider webhooks. Clockwork Control now probes edge TLS handshakes directly from our daemon workers.
  3. Backup Relays: Backup pushes no longer expect SpinupWP’s backup directory layout. Any server running Clockwork Companion can push offsite archives to our S3 relay.

2. Automated Client Reports & Scheduling

If you sell monthly WordPress care plans to clients, you already know this truth: if you don’t show clients what you did this month, they will eventually ask why they’re paying you.

Before v1.3.0, generating care plan reports meant either logging into a third-party SaaS tool or having a project manager spend hours copying update logs, uptime percentages, and security scan dates into a PDF template.

v1.3.0 introduces Automated Client Reports:

┌────────────────────────────────────────────────────────┐
│ CLOCKWORK WEB DEV — MONTHLY CARE PLAN REPORT           │
│ Client: Acme Corporation • August 2026                 │
├────────────────────────────────────────────────────────┤
│ • Fleet Availability: 99.98% Uptime (Zero P1 Outages)  │
│ • Software Maintenance: 14 Plugins Updated & Tested    │
│ • Security: Daily Malware Scans Clean • Zero Vulnerab. │
│ • Backups: 31 Daily Offsite S3 Archives Verified       │
│ • Core Web Vitals: Mobile LCP 1.8s (Good)              │
└────────────────────────────────────────────────────────┘
  • Report Templates: Choose what data your clients care about (uptime figures, plugin update histories, security scans, Core Web Vitals, and custom agency notes).
  • Scheduled Automated Dispatch: Set reports to generate automatically on the 1st of every month and email directly to client stakeholders.
  • Zero Third-Party Branding: Reports render cleanly with your agency’s name and colors.

3. Rolling 7-Day Fleet Uptime

We also upgraded our monitoring dashboard (/monitoring) with a rolling 7-Day Fleet Uptime Figure. Instead of only seeing real-time green/red dots, you can see a rolling average of your entire agency’s uptime over the past 168 hours.

When all 100+ sites across four different hosting providers show 99.98% 7d Uptime, you know your operations are dialed in.


How to Update

To update your installation to v1.3.0:

php artisan clockwork:update

This release laid the foundational architecture that made all of our recent multi-cloud and WordPress.org work possible. Check it out and let me know how the client reports work for your agency!

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.2.0Sep 4, 2026

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.

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→