Your Assistant
What does this PreventScripts AI do for me? Six answers.
Answers, with you
Ask, and PreventScripts answers from your own data through its tools — grounded lookups, never guesses. What it can't reach, it says so.
Tends itself
Every service is supervised: if one stops, it is relaunched within the minute. Updates are health-gated with automatic rollback, and the database is backed up nightly and restore-drilled weekly — not just saved, proven restorable.
Remembers, on your land
Its memory is a vault of readable notes plus your own records — all of it on your box. Nothing it learns leaves your hardware.
Reaches inside, for people you trust
Signed in, the assistant queries your live records — not a copy, not a summary. Every read is gated by your identity and logged. There is no public door to your data: the machine surface stays inside the fence, offered to an outside agent only when you name one.
Lives behind its own fence
The whole composition runs as its own account with its own keys. The fence is the boundary your data never crosses.
Grows with implements
Domain packs — data plus tools — hitch on as your needs grow. The assistant you have is the one that learns the next job.
The live inventory — which services are running, at what versions, with how fresh a backup — appears here behind a sign-in, read from your assistant's own service register. It isn't wired yet, so this page doesn't pretend: no status you see here is invented.