Skip to content
PAM

PAM — PHP, always in memory

PHP, always in memory

PHP was never the limit.

PAM is the ambitious, persistent application platform that takes PHP from supervised servers and production Laravel to real native interfaces and secure desktop software — with PHP at the center and Rust at the boundary.

orbit / pamready

$ pam init orbit --template native

Project created

Native runtime ready

$ cd orbit && pam dev

Android connected

iOS connected

Hot reload armed

native eventPHP stateRust diffUI commit
The PAM application stackComposer and PHP run through PAM into server, native mobile, and desktop targets.COMPOSERPHP 8.5PAMRUST · TOKIO · ZENDHTTP + SOCKETSMOBILEDESKTOP

ONE FOUNDATION.
NO SMALL AMBITION.

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

Choose what ships

One command. Four ceilings removed.

Pick the product surface. PAM keeps the workflow, runtime discipline, and PHP application model coherent.

The capability shelf

Add the hard parts.
Keep building the product.

Every official and community capability uses the same Composer contract and the same package-command extension model.

Explore all 27 capabilities

The runtime

We built the runtime PHP deserved.

PAM embeds PHP 8.5 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. It is not a workaround for PHP's past — it is a platform for what PHP can build next.

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 runtimeReproduce the Laravel laboratory
60 fps frame 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 1.0 stabilizes the CLI and public runtime contracts. Android API 26–36 is certified end to end. The generated Swift/UIKit host is compiled and launched in real simulators with PHP 8.4 and 8.5; signing and physical-device qualification remain explicit responsibilities of each application team.