Grayworth

Engineering / Gray

What Gray
includes.

Gray is not a framework around somebody else’s engine. Grayworth owns the language, bytecode, native backend, network reactor, database continuation model, and browser delivery path.

Live Gray runtime Connecting

Execution path

01Gray sourceTyped or immediate
02CompilerVerified bytecode
03Native backendW^X x86-64
04ReactorHTTP, TLS, DB
05ResponseBinary-safe

Implemented surface

Built below the
application line.

LanguageClasses, modules, collections, BigInt, regex, typed errorsImplemented
ExecutionLive, Adaptive, Static, JIT and bounded AOTImplemented
NetworkHTTP/1.1, HTTP/2, TLS, WebSockets, epoll and kqueueImplemented
DataPostgreSQL continuations, SQLite, Redis, cache and sessionsImplemented
ToolingFormatter, linter, LSP, tests, docs, trace and profilerFoundation
PortabilityNative IOCP operation backend and release qualificationOpen

Performance work

Every bottleneck
leaves a shape.

Database architecture

802.82 ms
became 4.60 ms.

Synchronous PostgreSQL exposed the blocked-reactor queue. Readiness-driven libpq removed the architectural bottleneck. Compiler-hidden continuations then restored ordinary-looking handler code.

p99 at qualification load

Database path evolution

ms

174× lower p99from the original synchronous path to compiler-hidden continuation

Database p99 latency by architecture
Architecturep99 latency
Synchronous802.82 ms
Readiness-driven32.80 ms
Compiler continuation4.60 ms

Separate qualification runs documenting the architectural progression. Not a controlled causal A/B.