# REEZN

> REEZN is a SPeeDD (Structured Prompt Driven Development) platform: a web app
> for taking software features through a structured, AI-assisted review and
> approval workflow. Teams define a feature, generate an analysis document,
> review and approve it, generate per-service REASONS canvases, and (on the
> Business plan) have an AI agent implement the feature and open pull requests,
> with human review gates at every stage.

REEZN is a private, authentication-gated SaaS application. The public site at
https://reezn.io exposes marketing pages, full documentation, and legal pages;
all product functionality lives behind authentication and is
organization-scoped.

## How it works

- Features move through a fixed lifecycle: draft, analysis (AI-generated),
  analysis review, canvas (per-service REASONS canvases, AI-generated), canvas
  review, approved. On the Business plan the lifecycle continues: implementing
  (an AI agent writes code and opens a pull request per service), verification
  review (human approval of AI verification reports), delivered. Features can
  also be rejected at a review gate or archived.
- AI generation is bring-your-own-key: organizations configure their own
  provider and API key (Anthropic, OpenAI, or Google).
- Governance is built in: norms (team conventions) and safeguards (hard
  limits) are injected into every AI generation, and safeguard violations
  block approval unless an admin overrides with a justification. Norms can be
  hand-authored or extracted by AI from a service's connected repository and
  approved into the library.
- Business orgs get an organization knowledge base (an AI-maintained knowledge
  graph built from approved documents, governance entries, uploaded documents,
  and repositories) that feeds context into generation, plus an optional
  adversarial AI Red Team pass that critiques generated documents.
- Access is governed by roles (admin, reviewer, author, observer) and by teams
  that grant access to specific projects.

## Docs

- [Documentation index](https://reezn.io/docs): all product documentation
- [Overview](https://reezn.io/docs/getting-started/overview): what REEZN is and the core workflow
- [Feature lifecycle](https://reezn.io/docs/workflow/lifecycle): every stage from draft to delivered
- [Norms](https://reezn.io/docs/concepts/norms): team conventions, including AI extraction from repositories
- [Safeguards](https://reezn.io/docs/concepts/safeguards): hard limits every plan must respect
- [Knowledge base](https://reezn.io/docs/concepts/knowledge): the organization knowledge graph
- [Implementation](https://reezn.io/docs/workflow/implementation): AI implementation and pull requests
- [Roles and teams](https://reezn.io/docs/concepts/roles-teams): permissions and project access

## Methodology

- [Spec-driven development: the complete guide](https://reezn.io/spec-driven-development):
  what SDD is, why it emerged, how the specify-review-implement-verify loop
  works, and the landscape of tools and approaches
- [SPDD: Structured Prompt Driven Development](https://reezn.io/spdd): the open,
  opinionated, governed flavor of spec-driven development REEZN is built to
  run, including the REASONS blueprint and where the review gates go and why

## Guides

- [AI code governance](https://reezn.io/solutions/ai-code-governance): how
  teams keep quality in the loop when AI writes the code
- [How to review AI-generated code as a team](https://reezn.io/solutions/review-ai-generated-code):
  review the plan, not just the diff
- [Spec-driven development for teams](https://reezn.io/solutions/spec-driven-development-for-teams):
  SDD with product and engineering agreeing together, standards enforced
- [AI slop](https://reezn.io/solutions/ai-slop): what it is, why it ships, and
  the process that stops it before production

## Comparisons

- [REEZN vs GitHub Spec Kit](https://reezn.io/compare/github-spec-kit)
- [REEZN vs Kiro](https://reezn.io/compare/kiro)
- [REEZN vs Notion + AI](https://reezn.io/compare/notion-ai)

Comparisons are honest and table-based: each concedes what the other tool does
better and explains where a governed team platform differs.

## Optional

- [Features](https://reezn.io/features): marketing overview of capabilities
- [Pricing](https://reezn.io/pricing): plans (Free, Team, Business)
- [Security](https://reezn.io/security), [Privacy](https://reezn.io/privacy), [Terms](https://reezn.io/terms), [GDPR](https://reezn.io/gdpr)

## Notes for AI agents and crawlers

- The marketing site, documentation, and legal pages are real,
  server-addressable URL paths; see /sitemap.xml for the full list.
- Authenticated application routes are client-rendered hash fragments
  (`/#/app/...`, `/#/backoffice/...`) and are not server-addressable, so they
  cannot and should not be crawled or indexed.
- For inquiries, use the contact options on the landing page.