One server. One framework. A million requests per second.
Bootgly is the native, zero-dependency PHP framework with one async core for Web and CLI. No Nginx, no PHP-FPM, no C extensions — and no third-party packages for your security team to audit.
You pay it in servers, in audits, and in onboarding time.
Infrastructure sprawl
The classic stack puts Nginx in front, PHP-FPM behind it and supervisors around it. The modern one — Swoole, FrankenPHP, event-loop frameworks — trades that for C extensions, custom binaries and new APIs to learn. Either way, every piece is one more config to tune, one more thing to monitor — and one more bill.
Dependency roulette
A typical application pulls in hundreds of vendor packages. Every one of them is supply-chain surface your team ships to production — and has to audit, patch and upgrade.
A dozen ways to do everything
Competing servers, config schemas and test stacks mean every project is a new set of decisions. Teams slow down arguing about plumbing instead of shipping.
Everything a modern backend needs, built into one coherent core.
Do more with less infra
A native event-loop HTTP server in pure PHP — Fibers for non-blocking I/O, HTTP/2, WebSockets, TCP and UDP. A drop-in alternative to Swoole and FrankenPHP with nothing extra to install.
Zero third-party packages in the core. The server, router, ORM, sessions, cache and test framework are first-party code — a smaller vendor/ and a smaller attack surface.
Web infrastructure: HTTP server, HTTP client, TCP server, TCP client — high-performance networking from the ground up.
Foundation layers
API Application Programming InterfaceApplication orchestration: components, endpoints, environments, projects, and server management. Forks into CLI and WPI.
ADI Abstract Data InterfaceData layer abstractions: database connections, table operations, and ORM foundations.
ACI Abstract Common InterfaceShared utilities for observability: benchmarking, event system, logging, and the built-in test framework.
ABI Abstract Bootable InterfaceCore bootstrap infrastructure: configs, data handling, IO, resources, and the template engine. The foundation everything else builds upon.
Dependencies flow one way — down. No skipping, no cycles.
The PostgreSQL driver speaks the wire protocol natively and pools connections per worker — queries suspend Fibers instead of blocking workers. That is where the +74% over Swoole on /db comes from.