惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

人人都是产品经理
人人都是产品经理
量子位
月光博客
月光博客
罗磊的独立博客
宝玉的分享
宝玉的分享
博客园_首页
酷 壳 – CoolShell
酷 壳 – CoolShell
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
WordPress大学
WordPress大学
博客园 - 叶小钗
博客园 - 聂微东
阮一峰的网络日志
阮一峰的网络日志
V
V2EX
雷峰网
雷峰网
博客园 - 三生石上(FineUI控件)
Jina AI
Jina AI
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园 - Franky
美团技术团队
爱范儿
爱范儿
V
Visual Studio Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Y
Y Combinator Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
I Wanted AI Code Review I Could Actually Own. So I Built ...
Devarshi Shimpi · 2026-06-24 · via DEV Community

I wanted AI code review I could actually own.

Not access through a subscription or a black-box service with its own limits. The deployment, credentials, providers, and usage under my control.

I kept hitting usage limits mid-week during deep building sessions. The models were capable. The workflow was useful. But access still depended on somebody else's weekly allowance, and centralized platforms can change whenever the company behind them decides to. Pricing, quotas, models, plan boundaries.

A workflow that fits this month may sit behind another subscription next month. I could not find a reliable open-source option that gave me the ownership model I wanted. So I built one.

codra-ai-code-review-dashboard

That became Codra: A self-hosted AI review engine built around bring-your-own models, your own data boundary, and no Codra-imposed usage ceiling.

What Codra Is

Codra is an open-source, self-hosted AI code review engine for GitHub pull requests.

It listens to pull request events, reviews changed files, posts inline findings, and provides a dashboard for jobs, repositories, model routing, history, usage, and failures.

codra-github-inline-pr-comment

It runs on Cloudflare Workers and uses:

  • Cloudflare Queues for review jobs
  • PostgreSQL through Hyperdrive for storage
  • KV for sessions and cache
  • A React dashboard for operations

The GitHub App, model credentials, database, and review history are yours. Provider keys are encrypted with AES-GCM using your deployment secret.

Bring Your Own Model, Bring Your Own Limits

Changing providers does not require replacing your review history, configuration, or workflow.

You configure the provider and model. Supported:

  • OpenAI-compatible APIs
  • OpenRouter
  • Anthropic
  • Google / Gemini
  • Cloudflare Workers AI

Why Self-Hosted Matters Here

A large frontend repo and a tiny backend repo should not need the same review strategy.

Each repository gets its own review settings. You tune triggers, skip generated files, ignore drafts, use mention-triggered reviews, configure labels, set file limits, and define custom rules.

What Codra Actually Does

Codra is not just a prompt wrapped around a diff.

It includes the pieces needed to operate AI review as a system:

  • Automatic and mention-triggered reviews
  • Inline comments, summaries, and check runs
  • Per-repository rules and skipped paths
  • Provider fallbacks and size-based model routing
  • Queue-backed, chunked processing with retries
  • Dead letter queue recovery
  • Job history, usage, repository, and model dashboards

The boring pieces are the point.

codra-dashboard-job-issues

Production software is mostly unhappy paths: provider outages, malformed output, large diffs, stale jobs, superseded reviews, and failed queue runs.

Codra exists because those details matter.

Open Source Is Part of the Product

Codra is AGPL-licensed because "own your AI review loop" only means something when the system is inspectable.

Developers can inspect how jobs, diffs, prompts, fallbacks, comments, failures, and repository settings work. AI code review is still early, and those questions are better answered in the open:

AI code review is still early. There are open questions everywhere:

  • Which models work best for different kinds of PRs?
  • How strict should automated review be?
  • How should local models and repository context fit in?
  • How do we reduce noise without missing real bugs?

Those questions are better answered in the open.

Codra should improve through real codebases and community contributions to prompts, providers, docs, tests, and defaults.

What Comes Next

Still in beta, but the foundation is there. The next phase has three tracks.

The next phase has three main tracks.

Deployment Targets

Cloudflare Workers stays the primary target. These paths are for teams and
individuals who want to run Codra on infrastructure they already control.

discord-other-hosting-support-cloudflare-issue

  • Vercel Functions adapter and other serverless runtime support
  • Conventional server deployment via Node.js and PM2 for EC2 or any VM
  • A Docker-first deployment path for platforms like Hetzner, DigitalOcean, and Coolify

Stability and Developer Experience

The review pipeline works. The focus now is making it hold up under real-world load
and easier to get running without friction.

  • A more robust pipeline that handles large PRs reliably
  • Cleaner installation, configuration, and debugging flows for first-time deployers
  • Community-driven defaults and real-world review config examples

Provider and Model Support

Inference should not be locked to hosted APIs. Local and self-hosted models will
become a first-class option alongside the existing provider list.

  • Improved support across existing providers
  • Routes for local and self-hosted models, Ollama, LM Studio, and similar
  • More language-aware review behavior per file type

Own the Review Loop

Providers, pricing, and quotas will keep changing. Your review engine should not have to change with them.

codra-cta-banner

Codra is open source on GitHub. Try it, star it, break it, file issues, and help shape where it goes next.

Docs: https://codra.run/docs

Read more