Plain questions, direct answers
Is anything monitoring me? Is anything hiding from the process list? What starts on its own? Each audit answers one question.
Is my machine still mine?
JARVIS
A guardian for machines that run AI agents.
Agents run code with your credentials. JARVIS watches the machine they run on: what is running, what could take or keep control, and what has quietly changed. It works locally, keeps evidence, and tells you what it cannot see.
The Lattice. A sweep passes over the machine, an intruder is flagged and held, then released on undo. One panel is left open on purpose: the blind spot it admits to.
How it works
01
Observe
Processes, autostarts, network activity, sensors and firewall state across Windows and Linux views.
02
Correlate
Events are joined into a timeline so a change has a before and an after.
03
Explain
Findings come with the evidence behind them and with what could not be seen.
04
Respond
Reversible containment only when you have switched it on. Anything more waits for you.
What it does
Local security guardian
The developer's trust surface
It shows what runs because you opened an editor, a repository or a shell, which is exactly where an agent works.
Evidence first
What is observed is recorded before anything responds to it. Something that is merely absent from a later scan is logged as not observed, never as fixed.
A response ladder
Watch, ask, propose, act. Automatic actions are limited to reversible containment, every action is in a ledger, and there is an undo.
Threat intelligence that can only add suspicion
Public threat feeds are vetted by a deliberately simple checker. Nothing fetched is ever executed, and intelligence can never clear a finding.
It names its own blind spots
JARVIS compares current attacker techniques with what its own sensors cover and reports the gaps as a work list.
Local by construction
The dashboard only listens on your own machine. There is no telemetry by default, and the core depends on almost nothing but the language it is written in.
Illustration
In practice
Ask it a question
jarvis spy- Is anything monitoring me? Who used the microphone or camera?
jarvis hidden- Is anything hiding from the normal process list?
jarvis toolchain- What runs because I opened an editor, a repo or a shell?
jarvis secrets- Which credentials are sitting in plain text on this disk?
jarvis evasion- Is anything in a position to lie to these checks?
jarvis gaps- What attacker tradecraft do I not cover yet?
What it is not
- Not a replacement for enterprise endpoint security.
- Windows and WSL2 today.
- Someone with full administrator or kernel control can falsify what any local tool sees. JARVIS says so instead of hiding it.