Trust & safety
Governed autonomy, by design.
The native path isn't just more capable — it's safer by construction. Jarvis works on screen, where you can see it, so mistakes are visible and you can step in mid-task. The promise isn't blind autonomy; it's visible, governed autonomy.
Controls
It can't run off without you.
VisibleOn screen, not in the darkEvery action happens where you can watch it. No hidden background calls — you see the work, not just the result.
Asks firstAmber before anything irreversibleTen authority levels. Anything that spends, sends, or deletes waits for your approval — via the dashboard, Telegram, or Discord.
Stops coldPause or kill, any surfaceOne click pauses or kills any agent on any machine. The emergency stop is everywhere, and every tool execution lands in the audit trail.
Your data
Your machine, your models.
- Source-available. Jarvis runs under the Jarvis Source Available License — you can read exactly what the runtime does, with the full source on GitHub.
- Local-first. Run local models, or bring your own LLM keys. Compute goes straight to your provider — we're infrastructure, not a token reseller.
- On your hardware. The pebble, your apps, and your screen stay on your machine, whether you self-host the brain or use managed hosting.
- Audited. Every tool execution is logged, so there's always a record of what ran and when.
Telemetry
What leaves your machine.
Because Jarvis is source-available, you can read precisely what the runtime sends. We keep operational telemetry to the minimum needed to improve reliability, it never includes your content, and it can be turned off. For the current, authoritative details — and how to disable it — see the configuration docs and the repository.