Run the same PHP app the same way from dev to prod, as one Rust binary. ePHPm embeds real PHP (Zend via FFI) and bundles a web server with auto-TLS, an embedded SQLite-compatible database, a KV cache, a pooling SQL proxy, and gossip clustering, so your code and config run on a single process with no other services to operate.

Ephemeral GitHub Actions runners. Single binary, every platform. Containers on Linux, Hyper-V on Windows, VMs on macOS. Secure by default — every job gets an isolated, disposable environment.

Speak MySQL, PostgreSQL, or SQL Server to SQLite. Wire-protocol translation in Rust: point pdo_mysql at :3306 and your unmodified app runs on embedded SQLite - no database server, no code changes.

PHP session save handler storing $_SESSION in ePHPm's embedded KV via the ephpm_kv_* SAPI functions

Predis Connection that routes commands to ePHPm's in-process KV store via the ephpm_kv_* SAPI functions - drop-in for Predis\Client with zero socket round-trips.

Userland mysqli compatibility shim over ePHPm's in-process DB bridge (ephpm_db_* SAPI functions) - the mysqli API your code already speaks, straight onto the embedded SQLite session; activates only when ext-mysqli is absent.

WordPress database drop-in (wp-content/db.php) backed by ePHPm's in-process DB bridge via the ephpm_db_query/ephpm_db_execute SAPI functions - wpdb without mysqli, no socket, SQLite underneath.

Laravel database driver ('driver' => 'ephpm') over ePHPm's in-process DB bridge — MySQL-dialect SQL through the ephpm_db_* SAPI functions, no PDO, no socket.

Doctrine DBAL driver for ePHPm's in-process database bridge - SQL through the ephpm_db_* SAPI functions, zero socket round-trips

CodeIgniter 4 database driver over ePHPm's in-process ephpm_db_* bridge