How it works

How Folt tests WordPress plugin compatibility

From plugin archive to environment-level evidence across the PHP, WordPress, theme, and plugin combinations you select.

how it works

From zip to verdict.

Four steps. No config file. Real WordPress, real signals.

Drop the zip.

Drag in your plugin .zip. No config file, no YAML, no Dockerfile. If it activates in wp-admin, it scans.

avg upload → queue: 4s

One environment per selected combination.

Folt expands your scan into environment runs. Baseline runs cover PHP × WordPress × themes; conflict runs cover PHP × WordPress × selected plugins. The current full matrix uses 216 runs.

provision: ~900ms per env · parallel by default

Then we poke it.

Each environment activates your plugin via WP-CLI, crawls wp-admin and the frontend with headless Chromium, records PHP fatals, JS console errors, and full-page screenshots. WooCommerce combos run a scripted checkout.

signals: debug.log · console · screenshots · wp-cli status

Read the verdict.

Pass/fail per combination. The exact stack trace. The exact environment. Plus a popularity-weighted blast radius, so you fix what actually matters first.

delivered: web report · json · email

Run calculation

The matrix expands before execution.

A scan is the request. Environment runs are the quota unit, and Folt shows the total before you start.

Baseline

4 × 2 × 7

PHP × WordPress × themes

56 runs

Conflicts

4 × 2 × 20

PHP × WordPress × selected plugins

160 runs

Full current matrix

216

environment runs

What you can verify

A report built from executed environments, not estimates.

Folt provisions the selected combinations, runs the same probes in each one, and keeps the evidence attached to the result.

Review the methodology

Coverage

216 environment runs at full coverage

4 PHP versions, current and previous WordPress releases, 7 themes, and 20 conflict plugins. Run cost is shown before execution.

Evidence

Failures include the environment and cause

Inspect activation, PHP, HTTP, browser-console, checkout, log, and screenshot evidence without reproducing the stack locally first.

Isolation

Ephemeral containers with no internet egress

Each run uses a constrained sandbox. Plugin archives are deleted after execution; retained reports follow the plan retention period.

$ folt scan ./your-plugin.zip

Test the combinations that matter before you ship.

100 environment runs per month on Free. No credit card required.

Start free

4 PHP versions · current and previous WordPress releases · 7 themes · 20 conflict plugins