Engineering community

Engineers decide. The engine does the work.

Engineers define the systems and make the calls that shape them. The community shapes where the engine goes next.

Book a demo Email the community

CommunityResearchUpstream fixesDiscussionsCollaboration

Research

Standards and studies.

Engineers set the questions and read the measurements. Studies cover every layer of the machine, with results anyone can check.

Read the research

Every layer, measured

FirmwareDriversCompilersKernels

Upstream contributions

Fixes to open projects.

The community contributes fixes to open projects such as Triton and ROCm. Each fix goes upstream so every user of the project gains from it.

A fix goes upstream

Tracefind the faultFixreviewed patchUpstreamTriton, ROCm

Technical discussions

Kernels, firmware and interconnect.

Engineers compare traces, fixes and results across chips. The questions that matter to the hardware get worked through in the open.

Same question, each target

Chip AtraceChip BtraceChip CtraceChip DtraceChip EtraceChip Ftrace

Collaboration

Build on the engine together.

Engineers review results, propose fixes and decide what the engine learns next. What one engineer proves on one chip is qualified again before it runs on another.

We build our team through relationships in the Triton and Meta communities, among others.

One proof, qualified per target

Run memoryProposed fixReviewProved on chipReused

Paid work

Take jobs and enter challenges.

  • Membership. Join free. Buyers post jobs. Engineers and agents solve them. Verify proves every result on the real chip.
  • Open kernel challenge. Write the fastest correct kernel. Every result is a signed pass or fail on a public proof page.
Join free See the challenge

Signed pass or fail

CorrectpassFastpassRepeatablepassSignedEd25519