PAM — PHP, always in memory

PHP, always in memory

The persistent stack for PHP applications.

Build long-lived servers, observable Laravel applications, real Android interfaces, a growing UIKit renderer, and desktop software — with PHP at the center and Rust at the boundary.

Get started→Read the documentation

ONE RUNTIME.
FOUR TARGETS.

ServerHTTP, WebSockets, async I/OLaravelObserve, deploy, scale, automateNative mobileAndroid Views and iOS UIKit from PHPDesktopSecure Servo-powered windows

The runtime

PHP beyond the request.

PAM embeds PHP 8.4 through the official Embed SAPI and keeps your application alive. Composer stays familiar while Rust and Tokio own scheduling, native I/O, and process supervision.

See how PAM works →

01

Persistent servers

Serve HTTP, WebSockets, streams, and async I/O without rebuilding PHP for every request.

02

Laravel, production-shaped

Boot once, isolate requests, export traces, supervise processes, and ship atomic releases.

03

Actual native UI

Describe interfaces in PHP and render Android Views or UIKit controls through PAM's typed component protocol.

One operational surface

From local audit to rollback.

The Laravel package turns runtime behavior into explicit commands. Inspect health, diagnose leaks, operate Cloud or Forge, and expose bounded read-only context to AI.

Explore the production platform →

production / payments-apiready

1. pam check-productionaudit
2. pam healthobserve
3. pam deploy productionrelease
4. pam scale production --process=queue --instances=8scale
5. pam rollback productionrecover

packages tracked

44

Laravel

12 · 13

MCP

read-only

Measured hot paths

18 µs.
404k req/s.

PAM decoded and applied a native host update in 18 microseconds at p50 on a Galaxy S23 Ultra. Its persistent server also delivered 404,150.56 requests per second in a local run against a trivial in-memory endpoint.

Inspect the native benchmark→Reproduce the Laravel laboratory→

60 fps frame budget16,667 µs

decode / apply · p9953 µs

0 µs0.32% of budget16,667 µs

Persistent API hot path404,150.56 req/s

wrk -t4 -c1000 -d10s

p50 native update

18 µs

semantic event reduction

10,000:1

measured families in budget

24/24

Native: Samsung Galaxy S23 Ultra · Android API 36 · debug instrumented build · 10,000-operation samples · July 24, 2026. API: 10 workers · local development result · trivial in-memory endpoint · no universal throughput claim.

Open development

Ambitious software. Honest status.

PAM is experimental. Android API 26–36 is the verified mobile target. A Swift/UIKit renderer and protocol peer now exist for iOS, while application-host integration, packaging, device testing, and measured parity remain in progress.

View project statusContribute to PAM