#016Tutorial1 min

Run your first analysis

The full path: choose a target, prove authorization, keep the checks ticked and launch.

Hackaiz team · updated 20/11/2026

Illustration: a person sets up an account on a laptop.
Illustration: a person sets up an account on a laptop. Illustrative photo, not a screenshot.

011. Choose the right path

From Analyze, two doors are available. “Analyze my infrastructure and projects” is for what you own: site, repository, database. “Check an external component” is for an MCP server, a Skill or a dependency you do not own; no ownership proof is needed because nothing is attacked.

022. Authorize the target

For a site, prove your domain. For a repository, install the GitHub App. Optional connections such as Supabase make the report more complete: Hackaiz explains why they matter without forcing them.

033. Keep the checks ticked

Every applicable check is ticked by default, and core security always runs.

  1. 1Untick only what you really do not want: an unticked check is neither run nor billed.
  2. 2Confirm the live site address when analyzing a repository: it must be entered, never guessed.
  3. 3Click the launch button: nothing starts without that click.

044. During and after

Progress shows real stages written by the server. When done, the report opens automatically with the verdict, findings and coverage. If the analysis is partial, the report says exactly what is missing.

Tip: For a first try, pick an app you published yourself: domain proof will be quicker.

Frequently asked questions

Take the next step

Was this article helpful?

Related articles