Reflex for Agencies — White-label server management for client fleets

TL;DR

Reflex replaces per-client Forge accounts and fragmented monitoring with a single white-label dashboard that manages your entire client fleet. Assign team members per client, run repair playbooks across dozens of servers simultaneously, and stop waking up at midnight for someone else's PHP-FPM crash.

The problem

• Sprawling Forge accounts — every new client means another Forge team, another set of credentials, and another login to juggle. At 20+ clients, the overhead becomes a job in itself.
• Midnight alerts for other people's servers — when a client's queue worker dies at 3 AM, you are the one who gets paged. Manual SSH, manual restart, manual invoice for the emergency hours.
• No fleet-wide visibility — each client's monitoring lives in a separate tool (or no tool at all). You cannot answer "are all my servers healthy?" without checking each one individually.
• Inconsistent server configuration — without a central ops standard, every client server drifts. One runs PHP 8.1, another 8.3, swap is missing on half of them, and OPcache settings vary wildly.
• Team handover is painful — when a developer leaves, their SSH keys, Forge access, and tribal knowledge about Client X's server leave with them. There is no audit trail.

How Reflex helps

• One dashboard, every client — the Reflex white-label dashboard groups servers by client. Your team sees only what they need. No more credential juggling or forgotten logins.
• Team-scoped access control — assign team members to specific clients. Junior developers can view logs without root access. Seniors can run deploys. Nobody touches servers they should not.
• White-label client experience — optional white-label branding lets your clients see your logo and colours on the dashboard they are allowed to access. You keep operational detail internal; they see health, incidents, and resolution status without Reflex marketing chrome.
• Client-facing narrative — share incident timelines and repair outcomes without exposing your internal playbook library. Billing stays between you and your client; Reflex bills your agency workspace, not theirs.
• Repair playbooks across the fleet — when PHP-FPM crashes, a playbook detects it and restarts the service automatically. That playbook works across every client server without you writing custom scripts per project.
• Reflex Brain auto-repair — Brain monitors CPU, memory, disk, and process health 24/7. It triggers playbooks autonomously so the 3 AM alert is handled before your phone even buzzes.
• Audit trail for every action — every deploy, restart, and playbook execution is logged with who triggered it and what changed. Client billing disputes and team handovers become straightforward.

Recommended plan

Per-server pricing fits agency workflows: pay £29 per monitored client server with fleet-wide playbooks and team seats included. Contact sales for white-label add-ons, SSO, and custom SLAs on larger programmes.

Getting started

1. Connect your first three client servers — install reflexd on a mix of clients to see the dashboard grouping and health metrics in action.
2. Enable the PHP-FPM and queue worker repair playbooks — these cover the two most common midnight incidents across client fleets.
3. Invite your team and scope access — assign developers to their clients, set permission levels, and start building the audit trail from day one.