Nebius x NVIDIA hackathon · Coding and agentic engineering
A living case file for your codebase.
HUBRIS maps your codebase, replays failures in a sandbox, and verifies fixes before you merge. It proves before it patches.
EVALUATING HUBRIS?
Run the guided demo: HUBRIS investigates a real duplicate-payment bug, reproduces it in a sandbox, forges a fix and verifies it with the test suite. No sign-in or keys needed.
TRY DEMO →TWIN SYNCED · WORKSPACE READY
Understand
Twin
maps the repo into a dependency graph
Trace
Call chain
built from the analyzed CodeTwin
Verify
Evidence
reproductions and checks, persisted
Forge
Patch
minimal and grounded in the repo
The CodeTwin maps your repository into a dependency graph. → Investigation grounds a suspected bug in that graph. → Reproduction stages the analyzed revision in a sandbox. → Forge generates a minimal patch. → Verify re-runs everything against the same revision.
Every stage derives its context from the analyzed job — the same repository, the same source revision — so evidence never drifts between screens.
Repository-aware by design
Source revision pinned per job
Sandbox-isolated reproduction
Evidence, not confidence.
Twin
Deterministic parsing: files, functions, APIs, tests, queues, infrastructure. The model reasons over facts and never invents the architecture.
Forge
Hypothesize, reproduce, falsify. It rejects its own wrong theories before proposing a minimal patch. You approve every persistent change.
Verify
Reproduction, regression test, full suite, typecheck, lint. Reported as one evidence record you can hand to a reviewer.