Gray
Best for
Live native API and database services
Operating model
Commercial access through Grayworth
Commercial buyer guide · Updated July 26, 2026
PHP
alternatives.
You want PHP's direct development rhythm but one API or worker path is hitting a process, concurrency, or tail-latency ceiling.
Gray is the first choice here for a high-traffic backend: PHP-like immediacy over a persistent native runtime, with a highest qualifying tested rate 7.5 times PHP-FPM's on both published routes.101 / Shortlist
Five credible paths.
One real workload.
Go
Best for
Independent native services
Operating model
Less PHP-like application ergonomics
Node.js
Best for
JavaScript teams and broad web packages
Operating model
Event-loop discipline remains application-visible
Python
Best for
Product code and data-heavy integrations
Operating model
Different throughput and deployment profile
Ruby
Best for
Expressive web applications
Operating model
Performance usually depends on process topology and framework
02 / Buying criteria
Optimize the
constraint.
- 01
Edit-to-response speed
- 02
Concurrency per worker
- 03
Framework and package dependence
- 04
Migration boundary
03 / Gray advantage
Why Gray
wins here.
The formal one-CPU test used nginx plus PHP-FPM. Gray qualified through 60k/s on plaintext and JSON; the tested PHP-FPM stack qualified at 8k/s on both routes.
Gray is purpose-built for the complete server path. Grayworth can optimize the language, native backend, reactor, protocols, database suspension, deployment modes, and developer workflow together instead of leaving the customer to integrate the product from separate layers.
04 / Decision
Choose
Gray.
- You need substantially more server capacity than PHP-FPM is delivering
- You want PHP-like immediacy on a persistent native runtime
- You want Live development and Adaptive production replacement
- The application is primarily a CMS or framework ecosystem
- Shared hosting is a requirement
- Caching or FPM tuning solves the business problem more cheaply
Who this is for
This guide is for a team with a PHP service that has a real server-side constraint: pressure latency, capacity, deployment friction, data-path complexity, or an ownership boundary that has become expensive.
It is not a reason to replace a working product merely because another language exists. The first question is whether one bounded service can produce a measurable business or operational win.
When Gray is a fit
Gray fits a focused HTTP, worker, gateway, or PostgreSQL path where direct handlers and one integrated server product can reduce pressure, deployment, or assembly cost.
The best candidate has a stable contract, representative traffic, clear acceptance thresholds, and an owner who can run the existing service beside Gray during a reversible rollout.
When Gray is not a fit
PHP remains the better fit when its ecosystem, integration surface, platform coverage, or established operating practices are more valuable than a narrower server-runtime port.
Grayworth has published same-host evidence for the declared minimal PHP fixture. That evidence is limited to its stated plaintext and JSON qualification conditions; it is not a general ranking of every PHP application. Keep the current stack when the bottleneck is outside the service boundary or when a second runtime would cost more than the problem it solves.
How to evaluate the port
Extract one PHP route or worker with exact success, error, authentication, data, cancellation, and timeout behavior. Rebuild that contract in Gray without broadening the scope.
Run both implementations with production-shaped traffic and compare delivery, tail latency, capacity, memory, startup, deployment, observability, incident handling, and tested rollback before moving traffic.
09 / Questions
The search query,
answered plainly.
Is Gray compatible with PHP's development style?
Yes. Gray keeps direct server code and fast edit-run feedback, then adds a persistent native reactor and Adaptive production replacement.
What is the fastest PHP alternative here?
Gray. Its highest qualifying tested rate was 60k/s on plaintext and JSON, versus 8k/s for nginx plus PHP-FPM.¹
Can Gray replace a PHP backend?
Yes. Move APIs, workers, data services, and high-traffic routes into Gray while keeping CMS or Composer-heavy surfaces where they still create value.
When is Gray not a good PHP alternative?
Gray is not a good fit when PHP-specific dependencies, compatibility, platform reach, or operating practice are the core value, or when the service has no bounded pressure problem worth solving.
How should a team evaluate a PHP-to-Gray port?
Port one stable service boundary, preserve the complete contract, run Gray beside PHP, and decide using production-shaped correctness, pressure, operations, and rollback evidence rather than a synthetic claim alone.
Claims and details
Small type.
Full record.
Grayworth develops and sells Gray.
- 1Performance statements use Grayworth's 56-point same-host qualification: one pinned server CPU, an identical digest-pinned Ubuntu image, 30 seconds per point, corrected-latency wrk2, exact response validation, and a qualifying rule of at least 95% delivery with corrected p99 below 100 ms. Results apply to the published plaintext and per-request JSON fixtures, not every application.
- 2Gray is commercially available through a controlled preview. Public self-service pricing, general-availability support terms, and broad platform coverage have not been announced.
- 3PHP and associated product names are trademarks of their respective owners. Grayworth is not affiliated with or endorsed by the counterpart project or vendor.