From deployment to evidence
mipo maps to how Security and GRC teams actually work: deploy scanners, model scope, run and schedule scans, detect changes, investigate results, export evidence, and monitor health.
Deploy scanners
A single Go static binary (stdlib only) runs on customer networks with no runtime dependencies and no auto-update.
Read the docs →Model scope
Compose subnets, subnet groups, FQDNs, and port lists into scan templates you can reuse and version.
Read the docs →Run / schedule scans
Launch a template immediately or schedule recurring runs; the dispatcher fans jobs out to the right scanners.
Read the docs →Detect changes
Every scan is diffed against history so newly-open, still-open, and closed ports are explicit.
Read the docs →Investigate results
Filterable, paginated results with per-host port state and a full historical view.
Read the docs →Export evidence
An append-only, tamper-evident audit log and encrypted backups preserve audit-ready evidence.
Read the docs →Monitor health
A five-layer resilience model plus a stateful alarm system keep operators ahead of failures.
Read the docs →Ready to go deeper?
The docs cover every page, field, and API call — generated from the same source as the in-app help.