Company

The company behind the Compute Optimization Engine

Computelab.co builds one product. The Engine runs the entire compute environment, from firmware to kernels, on any chip. Neutral on every chip. Building this engine for DARPA and other highly regulated partners.

Why it exists

Enterprises want the whole environment

The problem

Every layer feels a chip move

Teams move to a second chip, a new cloud or FP8, and every layer feels it. Firmware, drivers, networks, compilers and kernels all have to work together.

The product

One Engine, start to finish

The Engine connects to your repo, CI, cloud and machines. It returns a merged pull request, a signed proof pack and an installable artifact. Then it keeps watching.

Inside the Engine

Verify, Trace, Search, Green Computing

Trace finds the costly kernel. Search finds the fix. Verify proves it on the real chip. Green Computing counts the energy.

Research

Research feeds the product

Public studies with real implementations and measurements stand behind the Engine. Read them on the research page.

Partners

Meta ResearchLinux FoundationAWSMicrosoftGoogle Cloud

Leadership

The team behind the engine

Industry veterans in high-performance computing and low-latency engineering.

Founder and CTO

Laela Zorana

Laela built her career in high-frequency trading, tuning bare metal systems for nanoseconds of speed. Today she supports frontier AI labs, works with chip makers and has run large GPU clusters. That low-latency discipline is built into how the engine measures, tunes and proves every layer.

Co-founder

Dr. Vish

Dr. Vish brings decades of industry experience in green construction, geothermal energy and power. He shapes how the engine measures energy, power and thermal behavior from the facility down to the chip.

COO

Bradley Hamcock

Bradley is a performance engineer who has worked across several firms, including top quantitative trading firms and hardware manufacturers. He runs operations, delivery and partner programs, so every pilot moves from first check to proved results on schedule.

Vice President

Johann Miller

Johann is a scientific computing engineer with a long career in the medical field, where accuracy and reliability come first. That rigor goes into every customer and partner the engine serves.

Engineering network

Low-latency engineers in the US and worldwide

Contract engineers in the US and abroad who have worked with Laela on many low-latency engineering projects. The engine runs with a human in the loop in this phase. These engineers step in on every hard case, so nothing breaks while the engine learns.

The pipeline

Experts built into every run

computelab job cl_7a12
$ computelab fix kernels/attn_fwd.cu --chip MI300X
agents      plan, port, test, profile
verify      PASS on MI300X, 64 of 64 shapes
expert      reviewer sign off, HPC bench
senior      release approved, two-person rule
proof       signed ed25519  attn_fwd.pack
PR #214     ready to merge
Expert reviewers

HPC and trading engineers

A global network of HPC, scientific computing and high-frequency trading engineers reviews Engine output. Hard cases escalate to them inside the pipeline.

Coverage

US jobs, US reviewers

Jobs from US customers are reviewed by engineers in the United States, from first check to watch.

Reasons to trust it

Four differentiators

HPC

Laela and a global network of contract engineers with accumulated HPC experience review every escalated run.

HFT

High-frequency trading roots. Bare metal tuned for nanoseconds of speed, latency and reliability.

Neutral

Every vendor gets the same test.

Regulated

Building this engine for DARPA and other highly regulated partners, and working with regulators.

Product principles

What the Engine always does

01

Proves on real hardware

Every result runs on the real chip and comes with an Ed25519 signed proof pack you can check offline.

02

Returns one pull request

Every job runs the same intake, kernel check, hardware verification and expert review. You get one pull request and you click merge.

03

Keeps it working

The Engine rechecks your kernels on each new driver, firmware and framework release, with a named regression owner.

04

Keeps your code yours

Each job runs in its own sealed container. You keep full IP on delivered code.

05

Compares any chip fairly

NVIDIA, AMD, Intel, Google TPU, AWS Trainium, Qualcomm, Apple and Arm. Each one faces the same test.

06

Remembers every fix

When an expert fixes a case, the fix goes into run memory. It is paid for once and reused.

Kernel engineers, join the bench

Join free, take jobs the agents could not finish and get paid per passed kernel. US first.