Upload or connect your logs. See what would have been blocked, caught, or flagged.
Understand how Anvil. prevents costly mistakes before they happen.
Redacted before analysis. Nothing leaves our servers. No copy of your logs is kept.
What happens to what you paste
What we take: the log or config text you upload or paste — or, in connector mode, the read-scoped credentials you enter, used only to pull a bounded window of recent activity.
Before analysis we run a pattern-based redaction pass over the content (keys, bearer tokens, cookies, emails, card- and SSN-shaped numbers). It is best-effort, not DLP — it will miss novel secret formats, so treat it as a safety net, not a guarantee.
Analysis runs entirely on Anvil's servers. This deployment does not send your content to any external model provider, and nothing here is used to train models.
How long it lives: we do not keep your log text — it is parsed in memory and never written to a file or a database row. The report we derive from it is held briefly so this page can render it and you can download or email the PDF: up to 30 minutes in our job store, and up to 12 hours in memory (the report plus its rendered PDF), keyed to your session, then dropped — and neither survives a restart. An intake session also holds request counters for that same 12 hours; a connector token is held in memory for the same window and is never sent back to the browser. Credentials you type are used for the pull and not stored.
Paste this in your terminal, from your project folder. Not sure where that is? Paste it anyway, Anvil finds it. Works in any JavaScript or TypeScript project.
Couldn't reach the server, so this command runs without your scan context. That's fine: anvil protect re-scans when you run it.