Built by Agencies • Open Source & Community-Driven

We built it for our stack.
We gave you a huge start to finish yours.

Clockwork Control runs our agency’s production fleet every day. For the platforms we don’t personally host on (like WP Engine, Kinsta, or Cloudways), the contracts and modules are already built. If your agency hosts client sites on these providers, you can help test the endpoints with live credentials, verify response parsers, and submit pull requests back to the platform.

Not a Developer? That’s Okay

Test your account, let Claude do the coding, open a PR

You don’t need to write Laravel contracts by hand. Test the module against your real agency account, paste any quirks or raw JSON errors into Claude, and let AI generate the exact fix.

01

Get the Repo

Clone the repository and spin it up locally. All modules are bundled under modules/ ready to run.

02

Add Keys to .env

Manually paste your agency’s API token or SSH keys into your local .env file. Never share live keys with AI!

03

Let Claude Code It

If an endpoint returns an unexpected envelope, don't debug it. Just copy the JSON error to Claude: “Fix this parser and make Pest tests pass.”

04

Submit a PR

Run ./vendor/bin/pest to verify tests, push your branch, and open a Pull Request. We review and merge fast!

Important Security & AI Safety Rule

Always enter live API credentials directly into your root .env file manually. Never paste live API tokens, passwords, or SSH private keys into Claude, Cursor, ChatGPT, Antigravity, or any AI tool. AI coding assistants do not need real secrets to fix response envelopes — always use sanitized dummy placeholders like your_token_here.

Testing Status

Modules Looking for Testers

If your agency operates sites on any of these platforms, we would love your feedback.

WP Engine Module

Enterprise Managed Hosting

API v1 auth, per-site SSH runners, Companion deployment, and automated site/environment discovery.

What needs testing:

Live verification of install list envelope, backup history endpoints, and SSH gateway handshake.

modules/WPEngineTest Module→

Kinsta Module

Managed Container Hosting

MyKinsta API v2 auth, Company → Site → Environment hierarchy mapping, and SSH command runner.

What needs testing:

Live verification of dynamic SSH password generation and environment-specific SSH port routing.

modules/KinstaTest Module→

Cloudways Module

Managed Cloud VPS

Dual CloudProvider & HostingProvider implementation via Cloudways REST API v1.

What needs testing:

Real server hardware CPU/RAM telemetry polling and app-isolated SSH command execution.

modules/CloudwaysTest Module→

Azure Monitor Module

Enterprise IaaS

Azure Resource Manager & Entra ID Service Principal integration.

What needs testing:

Enterprise metrics polling for Percentage CPU and Available Memory Bytes on production VMs.

modules/AzureTest Module→

Linode Module

IaaS Hypervisor

Linode API v4 telemetry and instance reconciliation.

What needs testing:

Hardware specs mapping, multi-core vCPU normalized stats, and plan size tier resolution.

modules/LinodeTest Module→
Open Ecosystem & Extensibility

Extend Your Control Panel for Your Stack.
Get Listed as an Official 3rd-Party Module.

Run on a hosting platform or cloud hypervisor we haven't built yet? You don't have to wait for us. Clockwork Control was engineered with decoupled contracts so anyone can create a custom module for their agency's needs—and share it with the community.

1. Zero Core Code Edits

Extend ModuleServiceProvider. Your module owns its routes, settings, and manifests without modifying a single core file.

2. Auto-Encrypted UI

Declare required API keys in ModuleManifest. Form fields auto-render on /settings/integrations and store securely encrypted.

3. Implement & Test Quickly

Implement your provider's API endpoints against our clean contracts. Write or generate unit tests matching our reference Pest test suites.

4. Get Officially Listed

Submit a PR to our directory. We list your module in our ecosystem index with verified status, crediting your agency and linking back to your repo.

Contract Architecture

Pick the contract for your use case

  • HostingProvider: For WordPress management (RunCloud, GridPane, Enhance, Plesk, cPanel, Flywheel).
  • CloudProvider: For IaaS CPU/RAM metrics and server reconciliation (AWS Lightsail, Scaleway, OVHcloud, GCP).
  • SmsNotifier / Alerts: For custom alerts (PagerDuty, Telegram, Discord, MessageBird, AWS SNS).
  • DiagnosticCheck: Custom automated health checks integrated directly into /diagnostics.
Directory Submission/api/modules.json →

How to list your 3rd-party module

1. Tag your GitHub repository with topic clockworkcp-module.
2. Open an issue or PR titled [3rd-Party Module] Your Module Name to be indexed in /api/modules.json.
3. We audit and list your package in the official directory feed, giving full credit to your agency.

AI Module Generation Prompt (Claude / Cursor / Antigravity)Copy & Prompt

"I am building an open-source 3rd-party module for Clockwork Control to integrate with [Provider Name].

Clockwork Control uses a modular Laravel architecture. Please read:
- `modules/Core/src/Contracts/HostingProvider.php` (or CloudProvider.php)
- `modules/Core/src/ModuleServiceProvider.php`
- `modules/Core/src/ModuleManifest.php`

Here is the REST API documentation for [Provider Name] endpoints: [Paste API endpoints or docs].

Please generate the `{Provider}ServiceProvider`, `{Provider}Client`, and `{Provider}HostingProvider` classes with encrypted credentials declared in the manifest, Pest test fixtures, and strict type safety."

Read the full technical specification:Docs → Building 3rd-Party Modules
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→