Software,
at speed.

Grayworth builds software products and Gray, the server platform now carrying RC3 native execution evidence.

01 / First platform: Gray

The handler pauses.
The reactor does not.

pg_query reads like a normal call. Gray suspends the handler on socket readiness, then resumes it with its locals, errors, and request ownership intact.

General task workers
0
Measured continuation p99
4.60 ms
world.gycooperative continuation
function handleDatabase($request, $database) {
    $rows = pg_query(
        $database,
        "SELECT id, "randomNumber"
         FROM world WHERE id = $1",
        [random_int(1, 10000)]
    );

    http_respond(
        $request,
        200,
        "application/json",
        json_encode($rows[0])
    );
    return 0;
}

The compiler preserves this frame while PostgreSQL becomes ready.

02 / The Grayworth model

One engineering core.
More than one product.

Gray is Grayworth’s flagship commercial platform, not the edge of the company. The same systems work supports software products, developer tools, and infrastructure developed under one roof.

A

Build real products

Start with a focused user problem, not a platform demo. Product work decides what the shared systems must become.

B

Own the core

Language, runtime, data, delivery, and tooling can improve together instead of being negotiated across unrelated layers.

C

Prove it in use

Every product becomes a demanding test environment for performance, security, deployment, and developer experience.

03 / One system

The application path is
the product.

Gray is the commercial expression of that model: one language, runtime, server, data path, native backend, and release contract.

SourceGray languageTypes · classes · modules
ExecutionAdaptive runtimeStatic · native · SIMD
I/OReactor and dataHTTP · TLS · PostgreSQL
ReleaseStatic artifactNative mode · signing · SBOM
Inspect the engineering

04 / Qualification

Measured under load,
including where it fails.

Grayworth publishes corrected tail latency, saturation, memory growth, resource limits, exact build identity, and RC3 native-execution packets. The comparison is supporting evidence, not the product pitch.

Read the benchmark record
1-hour plaintext50k req/s49,997.81/s achieved · p99 7.00 ms · RSS growth 0 KiB
Database continuation4.60 msp99 at 8k requested/s · 99.52% delivered
RC3 native executable101 roundsDarwin arm64 program-specific sum and launch-floor fixtures below matching Go controls
RC3 SIMD sum40–49%less time than Go controls on Linux EPYC and macOS Apple Silicon integer-sum fixtures
Known saturation60–75k req/sthe measured transition, not a service promise

05 / Evidence

The claim stays
attached to proof.

RC3 adds native executable and SIMD evidence without turning fixture results into universal language rankings. Grayworth keeps the host, artifact, control, and failure boundary visible.

06 / Commercial preview

Bring one real
service.

Bring a production service to Grayworth. We will move it to Gray, establish the baseline, and turn the performance gain into a real migration.

Start a Gray migration

Gray language

Gray has its own technical home.

Grayworth develops Gray. The language reference, installation guides, and release documentation live at graylanguage.com.

Gray language reference