Designed to operate inside a controlled environment.
AuditIQ is local-first by design.
The current product runs on a single machine and is intended to be operated by the auditor or internal team responsible for the audit.
Audit records stay on the machine that produces them.
AuditIQ does not require a vendor-hosted SaaS account or cloud audit database.
Client records, runs, decisions and reports are stored locally within the product environment.
External access is explicit, not hidden.
AuditIQ may contact:
01
The audited website
To retrieve the pages and resources required for the audit.
02
Linked external documents
Where inspection requires them.
03
Google PageSpeed Insights
Only where performance measurement is enabled.
PageSpeed can be disabled for an engagement.
The audit itself should be governed.
AuditIQ records:
Relevant collection information can also appear in the report.
who authorised the audit,
how the website is collected,
crawl delay,
rendering settings,
and the reason for browser User-Agent overrides where used.
authorised_by: head-of-digital@example-insurer.in
collection: rendered · local browser
crawl_delay: 2000 ms · page_limit: 200
user_agent_override: none
pagespeed: enabled
AuditIQ is intentionally not presented as a multi-user enterprise platform today.
Clear architecture boundaries are part of the assurance story.
Current boundaries include:
single-machine operation,
no SSO,
no user roles,
no shared cloud workspace,
no authenticated portal crawling.