Gray
Live native API and database services
Commercial access through Grayworth
Commercial buyer guide · Updated July 26, 2026
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
Live native API and database services
Commercial access through Grayworth
Independent native services
Less PHP-like application ergonomics
JavaScript teams and broad web packages
Event-loop discipline remains application-visible
Product code and data-heavy integrations
Different throughput and deployment profile
Expressive web applications
Performance usually depends on process topology and framework
02 / Buying criteria
Edit-to-response speed
Concurrency per worker
Framework and package dependence
Migration boundary
03 / Gray advantage
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
05 / Questions
Yes. Gray keeps direct server code and fast edit-run feedback, then adds a persistent native reactor and Adaptive production replacement.
Gray. Its highest qualifying tested rate was 60k/s on plaintext and JSON, versus 8k/s for nginx plus PHP-FPM.¹
Yes. Move APIs, workers, data services, and high-traffic routes into Gray while keeping CMS or Composer-heavy surfaces where they still create value.
Claims and details
Grayworth develops and sells Gray.