Host Edition

“Why is my site slow?”
Answer it in ten seconds, for any account.

PHPRay records every PHP request on your servers — wall time, SQL as fingerprints, outbound HTTP, errors, N+1 patterns — and puts the answer in two places: a console for your support team, and a page inside DirectAdmin for the customer, so many of them stop opening the ticket at all.

Talk to us See the console

What it costs you to run

No daemon per account, no agent process. The extension writes one record per request into a shared-memory ring — one 0600 ring per uid, so accounts cannot read each other's traces — and a single Go binary reads it into SQLite.

We measured the overhead on our own hardware and published the numbers, including the inconvenient one: the request-level layer is indistinguishable from not having the extension loaded, and the per-plugin breakdown costs about 4 % — the same at any sampling rate, because registering a zend_observer handler flips the whole process onto the observed call path. Method and raw rounds: the measurement.

We run it on our own production. One shared server: 205 accounts, 719 domains, 223 sites reporting, PHP 8.0 through 8.5 side by side under CloudLinux and CageFS. We are a hosting provider first — the constraints this is built for are ours.

Nothing leaves your machines

The console is self-hosted. Traces stay on your servers; no request bodies, no cookies, no sessions are recorded at all, and SQL is stored with the literals stripped before it reaches disk. You are not sending customer data to a third party, which is the first question your own compliance people will ask.

Read the code before you install it

The DirectAdmin plugin and the extension are open source. Before you put anything on a production node you can read exactly what runs as root and what runs as the customer:

• phpray-directadmin — the panel plugin, Apache-2.0. One privileged script, guarded by a single sudoers rule validated with visudo at install time.
• phpray — the C extension and the Go collector, Apache-2.0, with a PHP_INI_SYSTEM master switch that makes the extension inert without uninstalling it.

How an evaluation usually goes

1. We put it on one node with the extension enabled for a handful of accounts you pick. Nothing is enabled fleet-wide on day one — we learned that the expensive way and wrote it down in the changelog.
2. You watch the overhead and the support queue for a week.
3. If it earns its place, you widen it; the per-account switch means you never have to choose between all and nothing.