← Alizé

Security

Last updated: July 2026

Our Commitment

Alizé Verify is open source — the code that checks your build, routes, and browser journey is public on GitHub and reviewable by anyone. The account layer runs on Supabase, which provides encrypted connections and row-level security. All data is encrypted in transit (TLS 1.2+) and at rest.

What stays local

Verification runs your build and drives a real browser against your own running app. Your source code is never uploaded anywhere by the CLI — it runs on your machine, against your machine's dev server.

Verification Data

Evidence reports contain only pass/fail gate results, error counts, and file paths — never your source code, secrets, or credentials.

Responsible Disclosure

If you discover a security vulnerability in Alizé Verify, report it to security@alize.one before public disclosure. We respond within 72 hours.

Privacy · Terms

Terms of Service

Alizé Verify checks whether AI-generated code actually builds, deploys, and works before you ship it. By using Alizé Verify, you agree to the following terms.

What Alizé Verify provides: automated checks against your application — build success, route availability, browser journey completion, console and network errors — and an evidence report. A passing report means the automated checks passed; it does not guarantee your code is bug-free, secure, or production-ready.

Your responsibilities: review evidence reports before shipping code; actions that are paid, risky, or irreversible require your explicit approval.

Privacy Policy · Security

Privacy Policy

Alizé Verify takes data privacy seriously.

What we collect: your email, name, and the code, verification runs, and evidence reports associated with your account. We collect only what is needed to run verification checks.

Data isolation: your verification runs and account data are isolated to your account using row-level security.

AI processing: code and context may be sent to AI model providers (Anthropic Claude) to help run verification checks. We do not sell your data.

Terms of Service · Security

Example verification report

Run: npx https://alize.one/alize-verify.tgz https://github.com/login

Both runs below are real and recorded. There is no READY example: READY needs credentials for an account on the target, we hold none, and inventing a green run on a verification product's own example page is the one thing this page must never do.

Example: INCONCLUSIVE (a healthy target, no account)

Evidence: 2026-07-21T20-44-33-861Z__github.com__blocked.json · Timestamp: 2026-07-21T20:44:33.861Z

alize verify  https://github.com/login

  PASS     Site reachable
           HTTP 200 in 322ms.

  PASS     App renders
           Rendered 282 characters of visible text.

  PASS     Login form found
           Found at https://github.com/login

  PASS     Auth rejects a bad password
           App rejected a deliberately wrong password in 464ms.

  BLOCKED  Real sign-in works
           No credentials given, so signing in as a real user was not tested.
           This is not a verdict about your app — it is a gap in what we
           checked.

  INCONCLUSIVE — 4 passed, 1 could not be tested
  4.2s · https://github.com/login

  BLOCKED means we could not test it. It is not a pass.

  Exit code 2.

Example: NOT READY (an auth outage)

Evidence: 2026-07-21T20-44-14-185Z__localhost-4010__fail.json · Timestamp: 2026-07-21T20:44:14.185Z

alize verify  http://localhost:4010

  PASS     Site reachable
           HTTP 200 in 55ms.

  PASS     App renders
           Rendered 23 characters of visible text.

  PASS     Login form found
           Found at http://localhost:4010/

  FAIL     Auth rejects a bad password
           Auth request never came back — still hanging after 15080ms. This is
           the shape of an auth outage: the browser asked, nothing answered. A
           user sees a spinner that never stops.

  BLOCKED  Real sign-in works
           No credentials given, so signing in as a real user was not tested.

  NOT READY — 1 check failed
  17.0s · http://localhost:4010

  Exit code 1.

← Back