Why MarsCompute

One team, from silicon to applications.

Most companies in AI own one layer: a model, an API, or a tool. We build the layers in between, and that is why each of them gets better.

The stack

Five layers. Select one.

The top two layers are what you call. The layers below are what we bring to the models we run on our own GPUs.

Layer 03

A planner that keeps optimizing, instead of tuning once.

It discovers optimization opportunities from how workloads really execute, models how kernels, memory and runtime interact, and plans changes that do not conflict with each other.

Architecture discovery Optimization graph Conflict-aware scheduling Continuous adaptation

Proof

Measured, and published.

3.9×

Sooner to the target

An agent reached its target at iteration 14 with our trace, against 54 with the best existing tracer.

G-Watch, September 2026

+13.3%

FlashAttention-4 on B300

Over the open-source kernel, from traces of a closed-source one. 5.2 to 13.3% across shapes.

G-Watch, September 2026

94–98%

Of the kernel left as it was

Original instructions still in a kernel traced by Xtrace. Existing tracers keep 8 to 48%.

G-Watch, September 2026

+50.8%

FlashAttention-2 on A100

Best case from an automated run; 25 to 51% at sequence length 1,024 and up with batch size 4 and up.

Report, March 2026

Working with teams at Meta 4Paradigm AI Singapore
Customer story

Meta

A customized G-Watch for internal AI workloads

Under a commercial collaboration, MarsCompute provided Meta with a customized G-Watch to help its engineers optimize internal AI workloads.

Read the story
Product
G-Watch, customized
Goal
Optimize internal AI workloads
Why it matters
At hyperscale, small kernel gains are large amounts of compute

A model to call, or a fleet to tune?

Sign up for the API, or talk to the optimization team about your own kernels and hardware.