Get in touch ↗
We build commercial software and Gray, our programming language and runtime.
Commercial software, the Gray runtime,
and published engineering research.
Commercial applications built around specific workflows and the people who use them.
Explore services
↗An integrated programming language and runtime for networking, database access, and native execution.
Inside the platformTechnical reports that document implementation, measured performance, and the limits of each result.
Read the publicationsGrayworth builds commercial applications, works on production infrastructure, and develops the Gray language and runtime. Here’s where those capabilities fit.
When work crosses spreadsheets, inboxes, and disconnected tools, the application needs to reflect how people actually get things done.
Start with the users, the decisions, and the handoffs. Define what belongs in the application and what needs to connect to an existing system.
Work, connected.●Work on deployment and the systems behind the application. Identify how failures are noticed, how access is managed, and how service is restored.
Explore infrastructure ↗Evaluate Gray against the actual workload, integrations, and operational requirements. Make the migration scope and tradeoffs explicit before moving a service.
Explore migration to Gray ↗Gray connects application code with HTTP, PostgreSQL access, and native execution in one development model.
The compiler and server runtime are developed together. The overview below separates the compilation path from the services an application uses while running.
Explore Gray engineering ↗Compilation produces the native application. The runtime handles the connections around application execution.
A project needs more than a sequence of meetings. Use each stage to clarify the decisions, the software, and the responsibilities that follow.
Map the users, the current systems, and the problem the application needs to solve.
Choose the first useful scope and the conditions that tell you it works.
Review working software, test its connections, and resolve the remaining decisions.
Establish deployment, access, monitoring, recovery, and maintenance responsibilities.
The report compares four runtime fixtures on the same host, with one CPU, equivalent handlers, and seven requested rates. All 56 runtime–route–rate points are retained.
Gray’s highest qualifying plaintext test point was 60,000 requested requests per second. The report also documents its queueing knee and a database wait bottleneck.
Read the methods & results ↗Qualification: ≥95% rate delivery and corrected p99 <100 ms. These are requested test rates, not delivered throughput. Results apply to the report’s specific host, fixtures, and conditions.
Source: GW–2026–0002, version 1.0 ↗Compiler-hidden continuations and the implementation behind direct-style database calls.
Read GW–2026–0003 ↗Native compilationThe design and implementation described in Gray’s native loop lowering report.
Read GW–2026–0004 ↗Based in California, working across commercial software, the Gray language and runtime, and production infrastructure.
About the company ↗Logan leads company strategy and commercial operations, connecting product direction and customer engagements to the development of Gray.
View profileAnnabella leads Gray’s language and runtime development. Her work spans native execution, networking, database systems, and published technical research.
Profile and publicationsPractical guides to planning, building, and owning software.
Explore the library ↗
Connect the problem, the context, and the decisions a delivery team needs to make.
Read the guide 5 min read
Handle an interrupted response without creating duplicate orders, inquiries, or jobs.
Read the guide 5 min read
Check that you can restore the data and use the application afterward.
Read the guide 4 min read
Work with Grayworth