MEASURED STATUS

Numbers, not promises.

Coverage: · stable performance pin:

2,655

passing Zend corpus tests

82%

of the core standard library

30,472

WordPress single-site tests at effective oracle parity

1.747×

latest clean full WordPress-suite CPU ratio vs PHP

Coverage was fully re-measured on 16 September 2026. Performance pin s183 was promoted on 16 October 2026; repository activity is tracked through 22 October 2026 at f89ae08 ↗. See measured coverage ↗

THE CONTRACT

Compatible in behavior. Free in implementation.

The reference is not Zend's design, but the output PHP code produces. Official .phpt tests and real application suites become executable oracles for closing each difference.

Faithful

Type juggling, errors, warnings, stack traces, destructor timing and edge cases are compared against PHP 8.5.7.

Safer foundations

Rust ownership, types and data structures replace much of the manual memory management found in the C core.

Performance to parity

Compatibility is proven on WordPress. The active front now targets 1× oracle CPU through measured changes to hot VM handler bodies.

ARCHITECTURE

One production VM.

Source moves through an explicit pipeline: parser, intermediate representations, bytecode compilation and VM dispatch. A compatible CLI and HTTP server exercise the same semantics.

Pipeline: PHP source, mago parser, AST and HIR, bytecode, VM.

“Correct or absent.”

A function returning plausible but wrong results is worse than a missing function. A builtin is registered only after its behavior has been verified.

CURRENT FRONT

From compatibility parity to performance parity.

The stable s183 micro benchmark is at 2.1× arithmetic, 2.3× properties, 2.9× arrays and 2.5× regex; calls and strings remain the largest measured gaps.

Read the latest update GitHub issues ↗