You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bitemporal supply-chain forensics on HydraDB: reconstruct exactly which repos resolved a compromised package version during an incident window - and prove which ones did not. Hack Hydra 2026, Track 2A.
Agent triage, measured: does this edit need a human, or can the AI handle it? We measure whether the graph under the agent can reach the tests that guard a change (0.42 pooled, 7 repos) and ship the fail-closed gate that routes unproven maps to human verification. CLI · MCP · SARIF · in-engine on HydraDB.
Supply-chain incident response on a HydraDB graph: which of your services resolved a compromised version, which installed it while it was still live on npm, and the Cypher that proves each answer.
HydraClaim turns agent memory into a temporal claim graph: every fact is a claim with provenance and a validity window, contradictions and overwrites are first-class graph structure, and a graph-probe router answers cheaply, escalates conflicted questions, and, crucially, abstains when the graph can't back an answer.
Supply-chain blast radius for npm, built on HydraDB. Answers what is exposed when a package is compromised — including the packages reachable through shared publish rights that dependency scanning misses. Hack Hydra 2026, Track 2A.
Graph-native supply-chain blast-radius scanner: which compromised npm/PyPI packages can actually reach your project, and through which path. Powered by HydraDB.
CrewBrain: meet Juno and Rex, AI helpers your homeowners and crew can text or talk to. They only see what you allow, nothing goes out without your OK. HydraDB + Claude + OpenAI realtime.
Autonomous engineering memory for coding agents. Captures diagnostics, git diffs, terminal evidence, and project context to provide persistent memory and continuity across development sessions using HydraDB.
Supply-chain blast radius over a HydraDB dependency graph. Ask which of your services a compromised npm package actually exposed, with the dependency path as evidence. Hack Hydra Track 2A.