
Kozo is the "Senior AI Architect" that lives in your project. It enforces the laws of clean code, security, and context—automatically—across Cursor, Lovable, Emergent, and every other agent you use.

"I asked Emergent to add a function to a 1,200-line file. Because of the Vibe Constitution, it refused. It calculated the violation, explained why it was bad for my project, and offered 3 modular alternatives instead. This is governance in action."
Most beginners don't see these traps coming. We didn't either — until we did.
That's why Kozo exists: Simple rules that teach your AI (and you) how to build clean, safe, scalable apps from the start.

"Once the rules are in place, the agent literally refuses to make things worse."
Super simple 4-step flow for beginners
What are you building? What tools do you use? What's annoying you most? Takes ~60 seconds.
We create simple, clear rules tailored to you: keep files small, no secret keys in code, basic security, memory helper, and "rescue mode" if your project is already a mess.
One zip file. Copy-paste into Cursor, Lovable, Emergent, Bolt.new — done in under 2 minutes.
Agents start refusing bad ideas. They suggest proper splits instead of bloating files. They remind you about security.
Before — agent nagging about refactor

After — agent suggests modular approach

Rules are only useful if they're followed. Sentinel connects to your GitHub repo to ensure your AI (and your team) never drifts from the Constitution.
ARCHITECTURAL ALERT: This PR introduces a 650-line file in /services. This violates the 500-Line Law. Please refactor before merging.
Sentinel acts as a "Quality Gate" in your CI/CD pipeline. It automatically flags (or blocks) Pull Requests that violate your core laws.
AI agents can be "pushy." Sentinel detects when an agent tries to ignore your .mdc files and alerts you before the technical debt becomes permanent.
Continuous scanning for API keys and PII that might have been "hallucinated" into your codebase by an AI during a late-night session.
A high-level view of your "Project Health Score." Watch your technical debt shrink in real-time as your Constitution takes hold.
Beta testers get lifetime Pro — so you'll see the full power first.
We know trust matters when uploading code.
That's why we built it this way from day one:
Our scanner runs 100% in your browser. We never see your source code; we only analyze the "Vitals" (file size, secrets, tech stack). No storage, no sharing, no training our models on your code. Guaranteed.
Your constitution, your rules, your project. We just help you organize it.
We're opening 20 beta spots for coders who:
Spots are limited — apply today.
No. We use a "Local-First" architecture. When you select a project, your browser performs a local scan using our open-source scanner. The raw source code is read into temporary memory, analyzed for architectural patterns, and then immediately discarded. Only the "Vitals" (metadata like file sizes and line counts) are ever sent to our server.
Vitals are a high-level summary of your project's health. They include: Structural Metadata (file names, folder depths, language breakdown), Complexity Metrics (line counts and "Spaghetti" hotspots), and Security Alerts (notifications that a secret was found, but never the secret itself).
The scanner looks for patterns (Regex) in your browser. If it finds something that looks like an API key or a password, it records the type and the location. Before that information is sent to us, we run a redaction script that scrubs the value entirely. Example: Instead of seeing your actual key, our server sees: sk-[REDACTED].
Yes. Because we never ingest your source code, Kozo is compatible with most corporate security policies that forbid "Code-Leaking" into third-party AI tools.