Decision library · Evidence before rankings
Compare
Gray.
Start here
Gray is the commercial server product Grayworth recommends for fast, focused backends. These guides show why, attach the measured record where it exists, and keep full claim qualifications in numbered notes rather than interrupting the product story.
01 / Gray versus the stack
Gray first.
Evidence attached.
Gray is one commercial product across code, runtime, native execution, networking, data, deployment, and tooling.
Go, Node.js, and PHP-FPM were tested in Grayworth's exact same-host fixture. Every guide leads with Gray's product advantage; methodology, availability, and trademark qualifications live in compact numbered claim notes.
Read the complete methodology →02 / Languages and runtimes
Choose the system
you actually have.
Gray vs Go
Choose Gray for a new high-throughput API when direct synchronous-looking handlers, Adaptive replacement, integrated PostgreSQL, and measured pressure behavior belong in one product. Gray qualified at twice Go's highest tested request rate for both published routes in Grayworth's same-host qualification.
Read comparison → 02 Same-host evidenceGray vs Node.js
Choose Gray when a backend needs the immediacy developers like in Node.js without making the application carry the event loop's continuation discipline. Gray's tested qualifying ceiling reached 60k/s on both published routes, versus 12k/s plaintext and 20k/s JSON for Node.js in the same fixture.
Read comparison → 03 Same-host evidenceGray vs PHP
Choose Gray when you want PHP-like directness on a persistent native server platform. Live and Adaptive execution preserve the fast development loop while Gray's reactor and cooperative PostgreSQL path replace the request-process ceiling. In the published fixture, Gray's highest qualifying rate was 7.5 times PHP-FPM's on both routes.
Read comparison → 04 Architecture guideGray vs Rust
Choose Gray for product-facing server software that should feel direct, deploy live, and own its HTTP, TLS, database, tooling, and selective native execution as one platform. Gray delivers the server product above the systems layer instead of asking every application team to assemble it.
Read comparison → 05 Architecture guideGray vs Java
Choose Gray for a focused backend that wants readable synchronous code without carrying a conventional JVM service stack. Compiler-hidden continuations, native networking, Adaptive replacement, and a compact Static artifact make the runtime part of the product instead of another platform to assemble.
Read comparison → 06 Architecture guideGray vs Python
Choose Gray for the performance-critical API boundary while keeping Python where its data, AI, and automation ecosystem creates value. Gray turns that hot path into a compact, typed server product with native HTTP, cooperative PostgreSQL, and bounded native execution.
Read comparison → 07 Architecture guideGray vs C#
Choose Gray when a service benefits from a smaller integrated runtime, synchronous-looking cooperative handlers, Adaptive replacement, and a deployment artifact Grayworth can optimize as one system. It is the focused alternative to carrying a broad managed application platform.
Read comparison → 08 Architecture guideGray vs Ruby
Choose Gray for a server path that should keep Ruby's belief in expressive application code while gaining an integrated reactor, cooperative database I/O, Adaptive replacement, and selective native execution. Port the pressure boundary and leave the product surface intact.
Read comparison → 09 Architecture guideGray vs C++
Choose Gray when the product needs native server performance without turning application development into manual systems engineering. Gray selectively lowers eligible code, preserves VM fallback, and owns HTTP, TLS, PostgreSQL, cancellation, deployment, and developer tooling as one commercial platform.
Read comparison → 10 Architecture guideGray vs Kotlin
Choose Gray for a backend that wants expressive typed code, classes, and synchronous-looking suspension in a smaller vertically integrated runtime. Adaptive replacement and runtime-owned I/O give the deployment model the same attention as the language.
Read comparison → 11 Architecture guideGray vs Elixir
Choose Gray when the service priority is compact native execution, low tail latency, direct handlers, and readiness-driven HTTP and PostgreSQL. Gray turns those capabilities into one commercial server platform with Live, Adaptive, and Static operating modes.
Read comparison →03 / Measured set
One fixture.
Four runtimes.
Orientation heuristic: at least 95% delivery and corrected p99 below 100 ms. One pinned server CPU, 30 seconds per point. This is not a general language ranking.
Gray is built to replace the pressure path.