alize verify

Your AI says it's finished.
Prove it.

Verify AI generated code before you ship.

  • Build
  • Routes
  • Browser Journey
  • Console Errors
  • Network Errors
  • Evidence Report
View on GitHub See example report

Try it

git clone https://github.com/yankeealpha444-arch/alize
cd alize
npm install
node scripts/alize-cli.mjs verify

v0.1 developer preview runs from the repo. Standalone package coming next.

← 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: node scripts/alize-cli.mjs verify

Example: READY

Verification ID: 4845c50b-5c48-494f-99b1-9deef853f6c7 · Timestamp: 2026-07-01T19:17:44.504Z

Result: READY
Gate 1 — Build: PASS
Gate 2 — Routes (/signup, /login, /pricing): PASS
Gate 3 — Journey (/alize-proof): PASS
Success text: Login successful
Console errors: 0 · Network errors: 0
Evidence: reports/alize-proof-evidence/journey-result.json, journey-result.png

Example: NOT READY

Verification ID: a13e2f0c-8e11-4d2a-9c3e-6b5f2d4a7e91 · Timestamp: 2026-06-28T14:02:11.118Z

Result: NOT READY
Gate 1 — Build: PASS
Gate 2 — Routes: PASS
Gate 3 — Journey (/alize-proof): FAIL
Failure reason: Login button did not produce success message — 'Login successful' element not found.
Evidence: reports/alize-proof-evidence/journey-result.json, journey-result.png

← Back