“I want to know what this is”
First success: You see a real governed result on your own machine.
Typically ~12 min
Start here
Pick the route that matches your role.
Twelve routes. Each states the concrete first success you will reach and a realistic time. None needs an account, a key, a cloud service or a conversation with us.
VerifAIer is not published to PyPI, npm or any marketplace, and no packaged installer exists. Every route starts from a source checkout. This website has no signup and no sign-in, so no route below leads to one.
Routes
If two routes fit, take the shorter one first, nothing later depends on it.
“I want to audit my own AI conversations”
First success: An AI conversation you already had, audited and sealed into a receipt you can verify offline.
Typically ~16 min
“I want to govern the code I write”
First success: A governed scan of your own repository, plus a pre-commit hook that runs it.
Typically ~14 min
“I want to run this for a team”
First success: VerifAIer in CI, gating a pull request with a real governance verdict.
Typically ~50 min
“I want to govern the agents and sessions I build”
First success: An AI session governed end to end, with a receipt.
Typically ~38 min
“I want to know what this protects and what it does not”
First success: A completed AppSec pilot with real findings and a documented trust boundary.
Typically ~1 day
“I want to know how this maps to a framework”
First success: A policy-pack alignment result you can put in front of an auditor, with its limits stated.
Typically ~34 min
“I want to verify a claim independently”
First success: You verify a receipt someone else produced - offline, without trusting the machine that made it.
Typically ~29 min
“I want the risk posture and my accountability”
First success: You can state the trust boundary, data handling and failure modes without asking anyone.
Typically ~49 min
“I want to know how this composes with what we run”
First success: You can draw the architecture and name its integration points and boundaries.
Typically ~64 min
“I want to know whether there is a real product”
First success: You have run the product yourself and seen a verifiable artifact, not a demo of one.
Typically ~68 min
“I must reach a defensible verdict without contacting anyone”
First success: A complete 8-stage evaluation: platform, architecture, evidence, governance, hands-on run, roadmap separation, deployment, verdict.
Typically ~3 h
Evaluating for your organisation?
The enterprise evaluation route is deliberately ordered so you can stop after any stage with a defensible partial verdict: understand the platform, then the architecture and trust boundaries, then evidence and receipts, then governance and policy packs, then run it yourself, separate what ships from what is roadmap, review deployment expectations, and reach a verdict.
It also names what should make you say no. A guide that cannot disqualify itself is marketing, not evaluation.