How Hackaiz Works — Method, Scope and Safety

How Hackaiz works: connect, prove, fix, verify

Short answer

Hackaiz connects to what you own (a site address, a GitHub repository, a database in read-only mode), runs authorized non-destructive checks, keeps evidence for every finding, prepares a fix you approve and rechecks it. Anything it could not test is listed as not verified — never as safe.

By the Hackaiz team · HACKTUALIZ Inc. · Updated 2026-10-21

Start my first scan

1. Connect

For a site or API, you prove control of the exact domain (DNS record or HTTPS file) and confirm your authorization; both are timestamped. GitHub repositories require a GitHub App installation on the repositories you select.

2. Prove

Checks are read-only by default (GET, HEAD, OPTIONS), paced, and limited in volume. Every outbound request batch is written to a hash-chained log that helps detect alterations. Findings keep the exact request, response or code location as proof.

3. Fix

For each finding, Hackaiz prepares a fix. You approve it; it is delivered as a GitHub pull request that you review and merge yourself.

4. Verify

A recheck confirms the fix worked. The score history shows progress, and recurrence alerts warn you if a fixed issue comes back.

What Hackaiz does not do

No denial-of-service, no data deletion or modification, no account takeover attempts.
No live database test without owner approval.
No finding invented to push a purchase — a clean, fully checked result is reported as clean.

Pricing

You pay in credits only for work actually done. New accounts receive welcome credits. If credits run out, the analysis pauses and shows what was checked and what remains, and the amount actually used is shown afterwards.