#001Learning2 min

Hackaiz: what it is and what it is for

What Hackaiz actually examines, what it never claims to do, and who it was built for.

Hackaiz team · updated 20/11/2026

Illustration: a developer reviews an app on a laptop.
Illustration: a developer reviews an app on a laptop. Illustrative photo, not a screenshot.

01Hackaiz at a glance

Hackaiz is a security tool for web apps, AI-built apps, code repositories, APIs, databases, and the MCP servers and Skills that agents rely on. It looks for exploitable flaws and shows, for each one, what was observed, why it is a risk and what to do next.

It only works on what you are allowed to examine. No website or API is read or analyzed without domain control proof and explicit authorization. A repository requires an authorized GitHub App installation on that repository.

02What Hackaiz actually does

Depending on what you connect, Hackaiz reads code and configuration, observes the public surface of a site with read-only requests, checks the access rules of a database linked read-only, and examines external components such as an MCP server or a Skill without running them outside a sandbox.

  1. 1It produces a report with a verdict, findings labeled Danger, To fix or To watch, and the coverage that was really checked.
  2. 2It can prepare a fix for a connected repository; you review and approve it yourself.
  3. 3If you wish, it can monitor a verified asset and alert you when it changes.

03What Hackaiz does not claim

Hackaiz is not an antivirus, not a firewall and not a certification body. A report with no finding does not guarantee an app is safe: it describes what was checked with the access you provided. Hackaiz never merges a fix automatically and does not run destructive tests against your data.

04Who is it for?

Hackaiz was first designed for people who ship fast with AI and have no security expert at hand: indie makers, small teams, startups and agencies. Developers also get a CLI, a GitHub Actions integration and MCP access.

Tip: Start with a single app you know well: you will understand faster what the report teaches you.

05Proof and authorization before analysis

No website or API is read or analyzed without control proof and recorded explicit authorization for the exact domain. The former passive audit without proof has been permanently removed. For a client website, a signed mandate reviewed by Hackaiz is also required and never replaces technical proof.

Frequently asked questions

Was this article helpful?

Related articles