< BACK TO DIRECTORY

SYSTEM: LOCALHOST // PATH: ~/projects/gitrabbit

GITRABBIT.CO

AI-POWERED CODE INTELLIGENCE FOR MODERN ENGINEERING TEAMS

GitRabbit.co aims to go beyond conventional AI code-review tools. Instead of reviewing code line-by-line in isolation, it is being built to understand the entire codebase, architecture, framework behavior, and potential production impact of every code change.

ONGOING DEVELOPMENTSAAS PRODUCTAI DEVELOPER INFRASTRUCTURE
NEXT.JSTYPESCRIPTOPENAIGITHUB APISFASTAPIREDISPOSTGRESQLAI ORCHESTRATION✦NEXT.JSTYPESCRIPTOPENAIGITHUB APISFASTAPIREDISPOSTGRESQLAI ORCHESTRATION✦NEXT.JSTYPESCRIPTOPENAIGITHUB APISFASTAPIREDISPOSTGRESQLAI ORCHESTRATION✦NEXT.JSTYPESCRIPTOPENAIGITHUB APISFASTAPIREDISPOSTGRESQLAI ORCHESTRATION✦NEXT.JSTYPESCRIPTOPENAIGITHUB APISFASTAPIREDISPOSTGRESQLAI ORCHESTRATION✦NEXT.JSTYPESCRIPTOPENAIGITHUB APISFASTAPIREDISPOSTGRESQLAI ORCHESTRATION✦NEXT.JSTYPESCRIPTOPENAIGITHUB APISFASTAPIREDISPOSTGRESQLAI ORCHESTRATION✦NEXT.JSTYPESCRIPTOPENAIGITHUB APISFASTAPIREDISPOSTGRESQLAI ORCHESTRATION✦
// MARKET OPPORTUNITY

The AI code review market is projected to reach approximately $420M by 2026.

While generalist incumbents currently dominate, significant market share is available for specialized platforms offering deep framework integration, in-browser collaboration, and precise architectural analysis.

// PRODUCT INTRODUCTION
DEMO VIDEO

An introduction to the GitRabbit.co product vision — what we're building and why it matters.

🐇

GITRABBIT.CO

AI-POWERED CODE INTELLIGENCE

WATCH ON YOUTUBE
// THE PROBLEM

Existing code review evaluates the change.
GitRabbit.co is being built to understand the system around it.

Modern software teams work with large, interconnected codebases, complex pull requests, framework-specific architecture constraints, hidden service dependencies, and an increasing volume of AI-generated code — code that may compile and pass CI but introduce deeper architectural, performance, or security problems.

TRADITIONAL REVIEW

—Diff → Review
—Review → Comments
—Comments → (Maybe) Fixed
—Context: the changed lines only

PROBLEM SCOPE

Evaluates the change. Misses the system.

GITRABBIT.CO APPROACH

▸Repository Context
▸Architecture Map
▸Dependency Graph
▸Multi-Model AI Analysis
▸Zero-Noise Validation
▸Actionable Engineering Insights

GOAL SCOPE

Understands the system. Surfaces what matters.

AI-Generated CodeHidden DependenciesN+1 QueriesArchitectural Anti-PatternsAsync/Sync ViolationsFramework MisusePerformance BottlenecksSecurity RisksContext Switching
// COMPETITIVE LANDSCAPE

AI Code Review, Reimagined

Where GitRabbit.co goes beyond traditional AI review tools.

🐰

CodeRabbit

AI-powered PR review

🐇

GitRabbit+

AI code review that teams experience together.

Review→Collaborate→Resolve
🐙

GitHub Copilot

AI-assisted development & review

🔍

Traditional tools

Review-focused

VS
🐇

GitRabbit.co

Review + Real-Time Team Collaboration

→
👥
💬

Traditional tools

Feedback across separate workflows

VS
🐇

GitRabbit.co

AI review + live team discussion in one workspace

→
🗨️
🔎

Traditional tools

Find issues

VS
🐇

GitRabbit.co

Understand → Discuss → Resolve

→
✅
// HOW IT WORKS

The AI Pipeline

Repository
▼
Codebase Indexing
▼
Repository / Dependency Graph
▼
Multi-Model AI Orchestration
▼
Validation & Zero-Noise Filtering
▼
Architectural + Performance Analysis
▼
Actionable Engineering Insights
▼
Optional AI Resolution

REASONING MODELS

▸Multi-file bug detection
▸Logical refactoring
▸Architectural analysis
▸Complex dependency reasoning

HIGH-CONTEXT MODELS

▸Large repository compression
▸PR diff analysis
▸Verbose log processing
▸Context summarization & briefs

FILTERING LAYER — ZERO-NOISE POLICY

Suppresses stylistic preferences, nitpicks & low-value suggestions. Surfaces only high-severity, actionable, technically justified issues.

ZERO NOISE
// FRAMEWORK INTELLIGENCE

Deep Framework Understanding

Instead of treating every project as generic source code, GitRabbit.co is designed to develop deep, framework-specific intelligence — understanding how modern frameworks actually behave.

▲

Next.js

SUPPORTED
▸App Router behavior
▸Server vs Client boundaries
▸Hydration-related problems
▸Data-fetching architecture
▸Server Component misuse
⚡

FastAPI

SUPPORTED
▸Async architecture validation
▸Dependency injection patterns
▸Pydantic validation review
▸Blocking synchronous operations
▸API-layer design analysis
🐈

NestJS

SUPPORTED
▸Module boundary enforcement
▸Dependency injection cycles
▸Decorator validation
▸Middleware execution tracking
▸Exception filter analysis
+ More frameworks planned: Django REST · Laravel · Ruby on Rails · Spring Boot
// FULL-CODEBASE CONTEXT

Beyond the Diff

GitRabbit.co is being designed to move beyond analyzing only the changed PR diff. The system aims to understand the full repository — how a seemingly small change in one module could affect another service or component elsewhere.

REPOSITORY CONTEXT MODEL

Repository

Root context

Files

Source units

Modules

Feature groups

Services

Domain layers

Dependencies

Import graph

Data Flow

State & I/O

Architecture

System design

PR Change

The actual diff

Result: AI reasoning that understands where the change lives within the broader system — not just what changed.

// ZERO-NOISE REVIEW

Review Less. Catch More.

GitRabbit.co is built around a strict Zero-Noise Policy — the goal is not to overwhelm developers with hundreds of suggestions, but to surface only what genuinely matters in production.

FILTERED OUT — NOISE

✗Stylistic preferences
✗Minor nitpicks
✗Low-value suggestions
✗Subjective opinions
✗Formatting inconsistencies
✗Comment conventions

SURFACED — ENGINEERING INTELLIGENCE

▸Production-impacting bugs
▸Security-relevant problems
▸Architectural violations
▸Performance bottlenecks
▸Scalability risks
▸Dangerous data-access patterns
// ARCHITECTURAL AUDITING

A Virtual Staff Engineer

PRODUCT VISION

The goal is not to replace engineers — it is to give every team the architectural oversight of a senior engineer, available on every pull request. GitRabbit.co is designed to reason about long-term system quality, not just whether code passes CI.

[ARC_01]

Blocking sync operation in async FastAPI route

Detected synchronous database call inside async endpoint — causes thread starvation under load.

[ARC_02]

Incorrect state pattern in Next.js Server Component

useState hook used inside a Server Component boundary — invalid and causes hydration failures.

[ARC_03]

Poor separation of responsibilities

Business logic and data access mixed inside a single route handler — reduces testability and reuse.

[ARC_04]

Architectural coupling between services

Service A directly imports and calls Service B internals — breaks modular boundaries and increases risk.

// PERFORMANCE INTELLIGENCE

Algorithmic & Infrastructure Analysis

Better algorithms mean lower compute requirements, better scalability, and lower infrastructure cost. GitRabbit.co aims to identify computational and data-access inefficiencies before they reach production.

DETECTED

O(N²)

Brute-force nested-loop approach — performance degrades quadratically as input grows.

→
SUGGESTION

O(N)

Hash-map based approach — linear time, scales efficiently regardless of input size.

N+1 QueriesUnpaginated Data FetchingUnnecessary DB CallsMemory-Heavy LoopsRepeated ComputationsResource LeaksBlocking I/OScalability Bottlenecks
// ENGINEERING WORKSPACE

Next-Generation Workspace

ROADMAP VISION

GitRabbit.co's long-term vision extends beyond code review into a collaborative AI-native engineering environment. These capabilities represent the product roadmap — not currently implemented.

⬛PLANNED

Cloud IDE

Inspect and modify AI-flagged issues directly inside the browser — no context switching.

⟳PLANNED

Live Pair Programming

Teams collaborate around AI-detected problems inside a shared real-time environment.

◈PLANNED

One-Click AI Resolution

Detect → Explain → Generate Fix → Run Tests → Review → Commit to Branch.

⚡PLANNED

Enterprise Governance

Organization-wide architectural consistency rules, custom policies, and large-repository analysis.

// WHY IT COULD MATTER
⚡

Developer Productivity

Reduce the amount of manual investigation required during code review.

◈

Engineering Quality

Catch deeper problems before they reach production.

▲

Framework Intelligence

Analysis tailored to how modern frameworks actually behave.

⬛

Enterprise Engineering

Help teams maintain architectural consistency across large repositories.

◬

Infrastructure Efficiency

Identify inefficient algorithms and data-access patterns earlier.

🐇

AI-Native Development

Part of the workflow where AI writes code and specialized AI validates it.

// ROADMAP

Product Phases

PHASE

01

Foundation

IN PROGRESS
Repository ingestionCodebase indexingPR analysisMulti-model orchestrationInitial framework intelligenceZero-noise filtering

PHASE

02

Code Intelligence

PLANNED
Full-codebase contextDependency graphArchitectural analysisBig-O detectionPerformance analysisAdvanced framework rules

PHASE

03

Engineering Workspace

VISION
Cloud IDEAI-assisted fixesTest executionBranch integrationCollaborative reviewLive pair programming

PHASE

04

Enterprise Intelligence

VISION
Org-wide code intelligenceArchitectural governanceLarge-repo analysisEngineering analyticsCustom rulesEnterprise integrations
// THE MISSION

AI can generate code.
GitRabbit.co aims to help engineers understand whether that code belongs in the system.

GitRabbit.co is not just an AI code reviewer. It is an ongoing attempt to build a code intelligence and engineering workspace that understands software at multiple levels.

CodeContextArchitecturePerformanceCollaborationResolution

THE LONG-TERM GOAL

Help engineering teams move from "Does this code work?" to "Does this code belong in the system?"

ONGOING · LARGE-SCALE SAAS PROJECT

GitRabbit.co is an ongoing product initiative focused on building an AI-native engineering intelligence platform. The current implementation and roadmap will continue evolving as the product architecture, AI capabilities, and developer experience mature.

↗ VIEW LIVE DEMO⌥ BACKEND REPO
// TECHNICAL DEEP DIVE

How I Built the System

GitRabbit Backend v2 is a production-grade microservices architecture built for scalability, database isolation, and independent deployability — each service owns its own domain, schema, and runtime.

MICROSERVICES ARCHITECTURE

🔐

Auth + Realtime

NestJS v11 · :3000

auth_db · PostgreSQL · Prisma v5
▸JWT Auth
▸Refresh Tokens
▸RBAC Guards
▸Socket.IO WebSocket
▸User Management
🤖

AI / LLM Service

FastAPI · :8000

ai_db · PostgreSQL · SQLAlchemy + Alembic
▸OpenAI API
▸Anthropic API
▸Conversation Models
▸Token Usage Tracking
▸Async Processing
📝

Blog Service

Fastify v4 · :4000

blog_db · PostgreSQL · Prisma v5
▸Post / Category / Tag
▸Comment System
▸JWT Verification
▸Auth Decorator
▸Slug-based Routing
🌐

API Gateway

Nginx · :80

— · —
▸/api/auth/* routing
▸/api/ai/* routing
▸/api/blog/* routing
▸WebSocket Upgrade
▸Internal Proxy

NGINX ROUTING TABLE

ANY/api/auth/*→auth-service:3000REST
WS/socket.io/*→auth-service:3000WebSocket
ANY/api/ai/*→ai-service:8000REST
ANY/api/blog/*→blog-service:4000REST

MULTI-AGENT AI WORKFLOW

Rather than sending a PR diff to a single model, GitRabbit.co orchestrates multiple specialized AI agents that analyze code from different perspectives simultaneously — then synthesize results through a validation layer before surfacing insights.

01

Repo Ingestion Agent

Clones & indexes the full repository. Builds dependency graph and module map.

Custom Parser
02

Architecture Agent

Detects framework patterns, architectural violations, and anti-patterns across the codebase.

OpenAI GPT-4o
03

Security & Perf Agent

Scans for N+1 queries, async/sync violations, injection risks, and auth gaps.

Anthropic Claude
04

Context Retrieval (RAG)

Queries Vector DB to find semantically similar code patterns across the full codebase.

Embeddings + pgvector
05

Synthesis & Filter Agent

Merges agent outputs. Applies Zero-Noise Policy — surfaces only high-signal findings.

OpenAI GPT-4o
06

Response Formatter

Generates line-by-line review comments, severity labels, and actionable fix suggestions.

Output Layer

VECTOR DATABASE & RAG PIPELINE

Codebase Embedding Flow

▸Repository cloned & chunked by file/function
▸Each chunk embedded via OpenAI text-embedding-3
▸Vectors stored in PostgreSQL + pgvector extension
▸Indexed by file path, language, and module type
▸Re-indexed on each new commit to stay current

RAG Query Flow

▸PR diff extracted and embedded at review time
▸Similarity search against codebase vector store
▸Top-K relevant code chunks retrieved (k=10)
▸Injected as context into AI agent prompt
▸Agent reasons about change in full codebase context
VECTOR STORE:PostgreSQL + pgvectorOpenAI EmbeddingsCosine SimilarityTop-K RetrievalChunk-level Indexing

DATABASE ISOLATION STRATEGY

Key principle:Each service exclusively owns its own PostgreSQL instance. No service ever directly queries another service's database. Cross-service identity is passed via JWT payload only.

auth_db

Serviceauth-service
Port5433
ORMPrisma v5
Migrationprisma migrate deploy
Volumeauth-db-data

ai_db

Serviceai-service
Port5434
ORMSQLAlchemy + Alembic
Migrationalembic upgrade head
Volumeai-db-data

blog_db

Serviceblog-service
Port5435
ORMPrisma v5
Migrationprisma migrate deploy
Volumeblog-db-data

FULL TECHNOLOGY STACK

LayerTechnologyVersionStatus
Auth / RealtimeNestJSv11✅
AI / LLMFastAPI0.110✅
BlogFastifyv4✅
Language (Auth/Blog)TypeScriptv5✅
Language (AI)Python3.11✅
DatabasePostgreSQL15✅
ORM (Auth/Blog)Prismav5✅
ORM (AI)SQLAlchemy + Alembic2.x✅
Vector DBpgvector (PostgreSQL)0.5+🚧
EmbeddingsOpenAI text-embedding-3Latest🚧
LLM ProvidersOpenAI + AnthropicLatest🚧
RealtimeSocket.IOv4✅
API GatewayNginxlatest✅
Cache / BrokerRedisv7⏳
ContainerizationDocker + Composev3✅
✅ Active🚧 In Progress⏳ Provisioned, not integrated

ARCHITECTURE PRINCIPLES

Database per Service

Each service has its own PostgreSQL instance — zero cross-DB queries permitted.

Loose Coupling

Services communicate via HTTP/WebSocket, never through shared databases.

Independent Deployment

Each service has its own Dockerfile and can be rebuilt and deployed independently.

Stateless Services

No in-memory session state. JWT is self-contained and verifiable by any downstream service.

Reproducible Migrations

Prisma and Alembic migrations run automatically on every container start.

Security by Default

bcrypt-hashed passwords, secrets in env vars, databases fully isolated per service.