Introduction
Guardix is an AI-powered security audit platform for Solidity smart contracts on EVM chains. It connects to your Git repository, runs a deep analysis pipeline, and returns validated findings you can prioritize, share, and export as professional reports.
Who Guardix is for
Section titled “Who Guardix is for”- Protocol and product teams shipping contracts to mainnet or testnets
- Security-minded developers who want architecture context, not just a list of linter hits
- Teams that need a shared workspace, invite links, and stakeholder-friendly share pages
What you get
Section titled “What you get”| Capability | What it means for you |
|---|---|
| Architecture understanding | Guardix maps how your system fits together before diving into issues. |
| Broad static analysis | Many parallel checks across common vulnerability classes and project-specific context. |
| Multi-engine validation | Findings are cross-checked by independent AI engines to reduce noise. |
| Exploit verification (when available) | For selected issues, Guardix can attempt to demonstrate impact in a controlled environment — so you see real exploitability, not only theoretical risk. |
| Reports and sharing | Downloadable reports and read-only share links for people outside your org. |
| Release Audits (when available) | Upload third-party audit reports and reconcile them against your source and deployment context before release. |
| CLI and agent skills | Terminal access and coding-agent skills to read findings, start audits, and triage across providers. |
What Guardix is not
Section titled “What Guardix is not”- A replacement for a full manual audit by a specialized firm when your threat model requires it
- A guarantee that every bug will be found — AI and automation still have limits
- Real-time monitoring of deployed contracts (Guardix focuses on repository snapshots you choose to audit)
Typical timeline
Section titled “Typical timeline”Full pipeline runs are asynchronous and often take on the order of hours, depending on repository size and scope — not minutes. Plan reviews around that cadence.
Next steps
Section titled “Next steps”- Quick start — connect a repo and run your first audit
- CLI and agent skills — terminal and coding-agent workflows
- API keys — authenticate scripts and the HTTP API with Bearer tokens
- How it works — conceptual view of the pipeline