Skip to content
Faultline

The live app · Nebius Global AI Hackathon

The bisect that refuses to blame the innocent.

An unattended git bisect run in one reused environment can blame the wrong commit when dependencies drift across the range. Faultline tests every suspect in a fresh Nebius container built from that commit’s own dependencies, proves both ends first, refuses to guess when the verdicts disagree — and has NVIDIA Nemotron explain the culprit.

Run a live hunt Watch the recorded run

live hunts today: …

01

Each commit, its own environment
One terminating Nebius Serverless AI Job per probe, installing that commit's own declared dependencies.

02

Both ends tested, not assumed
Round 1 runs your known-good ref and your failing ref in clean containers. If the failing ref passes there, the bug is in your environment — and Faultline says so.

03

Or no answer at all
If the verdicts contradict each other, no single commit explains them and Faultline refuses to name one. Commits that will not build are skipped, never blamed.

Trace 01 · the product, running

A real hunt, replayed

Real Nebius job IDs, real timestamps, real verdicts. It costs nothing to view and it is never presented as live.

Loading the recorded run…

Trace 02 · start a hunt

Three fields. No YAML.

Point Faultline at a public repository, a failing test, and the last ref where it passed. It resolves the install command from the repository — check it, edit it, start.

A public GitHub repository. Faultline reads the commit range before it spends anything.

The exact command each probe container runs, unchanged, on its own commit.

A tag, branch or SHA where the test still passed. The failing end defaults to HEAD.

Runs in every probe before the test, against that commit's own files. Leave empty to detect per commit.

Round 1 tests both ends in fresh containers. Each probe bills only while it runs.

Trace 03 · sponsor integration

Nebius is the engine, not a badge

Every probe is a container on Nebius Serverless AI Jobs; every verdict comes back through a presigned Object Storage URL, so no credential ever enters a probe; every explanation is one Token Factory call to NVIDIA Nemotron.

What Nebius actually runs

loading…

  • Reading the integration report…