Case study

Fast-Name: dogfooding Reflex on our own production

Fast-Name is the team behind Reflex. We run customer-facing Laravel and PHP workloads on our own infrastructure — Reflex has monitored and repaired that fleet since before public launch. This is our first named story: real stack, real incidents, no synthetic composite.

The setup

• Multi-site Laravel production on Linux VPS
• PHP-FPM, Nginx, MySQL, Redis, queue workers
• Reflex agent + Brain in graduated auto-repair on validated playbooks

The problem

Like every small platform team, we had the usual patchwork: panel deploys, uptime checks, Slack alerts, and restart scripts that only worked when the author was awake. Revenue-impact incidents — 502s during checkout, queue backlog on mailers — were the ones that hurt.

Results (internal metrics, last 90 days)

Production servers on Reflex

4

Brain-assisted repairs (90 days)

47

Incidents auto-resolved without human

38 (81%)

Typical MTTR (infra class)

< 2 min

Figures from internal Reflex workspace analytics — updated quarterly. Not a guarantee for your fleet.

What Reflex caught

• PHP-FPM worker exhaustion / 502 recovery
• Queue worker stalls (Horizon)
• Disk trajectory alerts before full
• Post-deploy health regression (Pipeline gating)

“We built Reflex because we were tired of paging ourselves for the same PHP-FPM crash. Now most of those never reach a human.”