Skip to main content
Guardian
Docs
ChangelogFAQContact
Download
Guardian

AI-generated code governance for small engineering teams. Enforce team policies and approve releases with confidence.

Product

  • Changelog
  • Docs
  • FAQ
  • Contact

Resources

  • Getting Started
  • Security
  • Configuration
  • Guru AI
  • Monitoring

Legal

  • Privacy Policy

© 2026 Guardian Project. All rights reserved.

Designed & Developed bySenol Dogan

Getting Started | Guardian

Sections

Features

Guru: Release Decision AssistantProject MonitoringReviews & Fix Proposals

General

Getting Started

Operations

InstallationAuthenticationUpdatesConfigurationMigration Guide

Security

Security

Support

Troubleshooting
Documentation

Getting Started

Control AI-generated code before release with policy enforcement and human approval.

What is Guardian?

Guardian helps small engineering teams control AI-generated code before it ships. It is a desktop + CLI governance layer focused on risky AI-assisted changes and release decisions.

Guardian is not:

  • A generic AI coding assistant
  • A generic code review tool
  • A generic security scanner

Guardian is the release control layer for AI-heavy code change workflows.

Core Product Workflow

  • AI-Generated Code Intake: Detect and isolate AI-assisted or unusually large/refactor changes for stricter handling.
  • Policy Enforcement: Apply team architecture, security, and quality policies automatically.
  • Human Approval Workflow: Require accountable approval, override owner, and reason when risk is high.
  • Release Decision Surface: Answer the final release question with evidence: can this code ship now, and why?

Who is it for?

Guardian is designed for teams that need release confidence on AI-assisted code:

RoleUse Case
Engineering LeadersStandardize release decisions across AI-heavy PRs
Platform/DevOps TeamsEnforce guardrails in local + CI release gates
Security/Architecture TeamsApply non-negotiable policies before merge/release
Release ManagersTrack approvals, overrides, and decision evidence

How it works

Guardian follows a four-step release governance cycle:

┌─────────────┐     ┌──────────────┐     ┌──────────────┐     ┌─────────────┐
│   INTAKE    │────▶│   ENFORCE    │────▶│   APPROVE    │────▶│   DECIDE    │
│ AI-heavy PR │     │ Team Policy  │     │ Human Gate   │     │ Ship/Block  │
└─────────────┘     └──────────────┘     └──────────────┘     └─────────────┘
  1. Intake: Guardian identifies risky AI-assisted or unusually large changes.
  2. Enforce: Team policies are evaluated across architecture, security, and quality rules.
  3. Approve: Human reviewers validate fixes and document approval or override reasons.
  4. Decide: A release readiness signal is generated with explainable evidence.

First 10 Minutes

Here's what you should do in your first session:

1. Install the Application

Download the installer from the Download page. macOS builds are available now; Windows and Linux appear when published.

2. Configure Provider Settings

Navigate to Settings > Provider and configure your AI provider credentials. Guardian supports both cloud and local models.

3. Start Monitoring Your Workspace

Click the Scope field (or drag and drop a folder onto the app) to select your workspace, then choose Launch Guardian to start monitoring.

4. Review Findings as a Release Decision

Once the scan completes:

  • Focus first on AI-heavy and architecture-sensitive changes
  • Use Guru to understand why each risky change matters
  • Apply policy-aligned fixes and record decision context for your release flow

Application Layout

The Guardian interface consists of four main areas:

AreaPurpose
SidebarNavigate monitoring, reviews, settings, and history
Main PanelInspect findings, policy evidence, and fix proposals
Guru ChatExplain risky changes and propose policy-aligned fixes
Status BarTrack provider status, version, and workflow state

Next Steps

  • Installation Guide - Detailed setup instructions
  • Guru - Explain risky findings and generate fix proposals
  • Reviews & Fix Proposals - Manage approvals and controlled apply flow
  • Configuration - Configure policies, scan scope, and guardian.lock
  • Security - Understand the local-first security model

On This Page

What is Guardian?Core Product WorkflowWho is it for?How it worksFirst 10 Minutes1. Install the Application2. Configure Provider Settings3. Start Monitoring Your Workspace4. Review Findings as a Release DecisionApplication LayoutNext Steps

Latest release notes

What's New in v1.2.6

Published: Apr 04, 2026

  • Release approval policy documented with role boundaries for release managers, incident commanders, and reviewers.
  • Legacy `.guardian/release_decisions.jsonl` rows now remain readable during upgrades, so manual approval state is preserved.
  • Audit precision hardened for local/dev-only findings and recent-fix context reuse to reduce stale duplicate reports.
View full changelog