See the relationship between your application, database and HTTP services. Start with a specific request and narrow down the investigation.
Connect PHP execution time, database queries and external APIs in a single investigation. No jumping between logs and plugin lists.
Duration, CPU, memory, SQL, outbound HTTP, files, Redis and PHP errors. The always-on layer records every request, including the one that is hard to reproduce.
Sampled profiling attributes execution time to components. Start with the most expensive component instead of disabling plugins one by one.
Example from the WooCommerce test store: Storefront and 22 plugins. Values describe the profiled sample.
Find slow fingerprints, query counts and N+1 patterns. Customer-specific parameter values do not need to appear in the report.
Separate time spent executing your code from time spent waiting on payment, shipping and other HTTP services.
The extension runs inside PHP. A local collector stores request records in SQLite. Choose Cloud when you need to manage multiple sites.
Open source. A local dashboard. No account required for local use. Data leaves the server only when you enable Cloud.
of requests in the always-on layer
default profiling sample
local collector and dashboard
PHP, SQL, HTTP and components
Use the PHP extension on your server, or the WordPress collector when loading a custom .so module is not an option.
Requests reach the collector through shared memory or JSONL. SQLite storage, an API and the diagnostics dashboard are available locally.
Follow a slow URL to its SQL queries and components. After a change, compare the results with Studio or a higher plan.
phpray.so captures request, SQL, HTTP, file and error events. Observer API powers a separate, sampled profiling layer.
Reads the stream, stores SQLite data, applies retention and local alerts. Defaults: 30 days of history and a 4 GB database cap.
Persistent local history. Retention windows and size limits are independent; the oldest records are pruned when either limit is reached.
Local collector interface for the dashboard and CLI. It is distinct from the Cloud /v1/aggregates and /v1/traces protocol.
Sites, traces and component views. Loopback by default, with JWT access control. The local core needs no Cloud account.
Disconnected by default. Data stays local until you configure the connection.
Architecture diagram — the switch does not change server configuration.Expand any node to inspect its scope. Full data protocol →
Explore the example. Inspect the details. Make a decision based on data.