Follows every commit
A signature-verified webhook notifies Repotrix on each push, and it reads exactly what changed. Nothing waits on a manual trigger or a scheduled job.
NEWVS Code Extension · Re-syncs on every merge
Your codebase changes daily.Your docs & answers never fall behind.
Most tools that chat with your repository answer from a snapshot taken at setup. The moment your team merges, that snapshot is out of date. Repotrix works differently: it follows every commit, understands what changed, and keeps your documentation, diagrams, and answers in step with the code. Available on the web and as a native VS Code extension.
Every mergeauto re-sync
Zerostale answers
VS Codenative extension
<2 minto first ingest
BUILT ONFastAPIPineconeGeminiPostgresRedis / ARQGitHub WebhooksSlackTeams
Why Repotrix is different
Other tools answer from a snapshot.
Repotrix answers from today.
When documentation falls out of sync, people quietly stop trusting it. Repotrix is built so that does not happen. Here is what makes it work.
Re-syncs in one pass
Documentation, diagrams, security findings, and the search index update against the new commit together, so they never disagree with each other or with the code.
Surfaces what drifted
Each change is reconciled against the dependency graph, so you can see precisely where the system has moved away from its documentation.
Sharpens over time
The longer Repotrix follows a repository, the better it understands your patterns, so its reviews and answers grow more precise the longer you use it.
Snapshot tools vs. Repotrix
Most tools answer from setup. Repotrix answers from today.
The difference isn't the feature list — it's freshness. Here is the same job, side by side.
Snapshot tools
Repotrix
Knowledge source
A snapshot taken at setup
The latest commit, every merge
When you merge
Answers quietly go stale
Re-syncs automatically in one pass
Documentation
Drifts until someone rewrites it
Regenerated on every push
Diagrams
Hand-drawn, soon outdated
Redrawn from the live graph
Answers
Vague, few or no citations
Cited to exact files in today's code
Upkeep
You babysit it
Maintains itself
Take the tour
See it stay current, live.
A guided walkthrough of the real product, from the first ingestion to a merge that brings everything back in sync. Select any chapter to begin.
Repositories
WorkspaceRepositories
Connect any GitHub repo. Ingested in minutes.
payments-svc
Ready8e2a31d⚡ Drift on⎇ productiongithub.com/acme/payments-svc
🔑 PR-Companion
📁 1,247 files📄 84,392 lines🌐 3,184 chunks indexed
🛡 12 secrets redacted⚡ 42s ingested🌍 3 languages
HEALTH0/100
WHAT THIS REPO DOES
Settles card and UPI payments end to end. Owns webhook dispatch, idempotency keys, and the reconciliation cron…
Read full documentation →01/10Repositories
The Suite
Every surface. Always in sync.
One source of context, kept current for you.
Documentation, diagrams, security, chat, and reviews all draw on the same dependency graph and search index, and they refresh together as the code changes. Nothing contradicts anything else, on the web or in VS Code.
Re-syncs on every merge
The Freshness Engine
The engine behind everything else. A signature-verified webhook reports each push, the worker reads precisely what changed, and your documentation, diagrams, security posture, and search index update on their own. Nothing waits on a manual step or a scheduled job.
- Notified on every push by a signature-verified GitHub webhook
- Re-embeds only the files that changed, then reconciles them against the dependency graph
- Documentation, diagrams, and security scans regenerate automatically
- Shows where the architecture has moved away from its documentation
- Answers are grounded in the latest commit, so they stay accurate
RE-SYNCOn merge
MANUAL STEPSNone
GROUNDED INLive commit
Always current
Documentation
Technical documentation generated from your code and rewritten whenever a merge changes what it describes, so it reflects what actually shipped.
Live diagrams
Architecture
Architecture, dependency, and sequence diagrams in Mermaid that regenerate on each push, so the picture always matches the current system.
Grounded in your code
AI Chat
Graph-aware retrieval that searches the latest commit and cites the exact files behind every answer, so you can verify what it tells you.
Automated reviews
PR Companion
Every pull request is reviewed against your current documentation, and the findings are posted back to GitHub for the team to act on.
Continuous scanning
Health & Security
Exposed secrets, PII, and licensing issues are re-evaluated as the code changes, with a health score that tracks each repository over time.
Guided ramp-up
Onboarding
Role-aware onboarding paths built from the live codebase, so new engineers learn the system as it stands today.
Quietly kept informed
Drift Alerts
When a change pulls the code away from its documentation, Repotrix posts a short summary to Slack or Teams so the team stays aware.
Built-in audit trail
Compliance
Redaction events, webhook rotations, and token changes are recorded in a tamper-evident log you can export when it is needed.
Native VS Code Extension
Your fresh codebase, where you already work.
The same up-to-date documentation, diagrams, security, and chat, without leaving the editor. Install once, and Repotrix lives in your sidebar, answering from the latest commit while you work.
REPOTRIX AI: REPOSITORIES
▾ BEmain · ✓ current
- Chat
- Documentation
- Architecture
- Security Report
- Onboarding
- PR Reviews
- Drift Events
▸ FEmain · ↻ 1 behind
▸ repotrix_vscodemain · ✓ current
Docs — BESecurity — BE ×
◆ BERegenerate
83
3 MEDIUM1 LOW
HEALTH SCORE · 25 files analyzedStrong security practices overall — robust password hashing, comprehensive log redaction and signature-verified webhooks. Watch the default CORS config and JWTs passed in WebSocket URLs.
MEDIUM (3)
app/api/routes/websocket.py:40 SECURITYThe WebSocket auth token (JWT) is passed as a query parameter, exposing it in server logs and browser history.
app/core/config.py:9 SECURITYDefault
CORS_ORIGINS allows any origin (*); restrict it in production.PROBLEMSOUTPUTTERMINALPORTS
worker-1 17:55:02 cron:reap_stuck_jobs_task() delayed=2.69s
worker-1 17:55:02 ✓ {'status':'ok','drift_event':0,'documentation':…}
◆ synced to main@a1b2c3 fresh
- 1
Context-aware chat
Ask about the file you are in and get answers grounded in the current commit, without leaving the editor.
- 2
Docs & diagrams inline
Open up-to-date documentation and architecture diagrams beside your code, drawn from the same context as the web app.
- 3
Security & PR reviews
Read health scores, security findings and pull-request feedback in the place where you write code.
- 4
Guided onboarding
Walk a new engineer through the codebase from a native sidebar, from their first clone to their first commit.
New · MCP Server
Your codebase, inside Claude, Cursor, ChatGPT & Gemini.
Connect your AI assistant to Repotrix over the Model Context Protocol - Claude Code, Cursor, Copilot, Gemini, ChatGPT and other MCP-compatible tools. Whatever tool you code in can ask grounded, always-fresh questions about your repositories - no copy-pasting, no stale context. Available on paid plans.
ClaudeCursorCopilotWindsurfGeminiChatGPT
exposes
list_reposask_codebasesearch_codeget_architecturewhats_changedyour repositoriesgraph-aware · always fresh
Production-Grade
Not a demo. Hardened from day one.
Secrets are encrypted, requests are rate-limited, responses are cached against the live commit, and every token is metered. It is ready for a real team from the first day.
Encrypted at rest
Webhook secrets and GitHub PATs are encrypted with Fernet — keys live in the environment, never in the database.
Commit-pinned cache
Gemini responses are cached against the latest commit hash, so a new push invalidates them naturally — fresh answers, small bill.
Per-workspace rate limiting
Fixed-window rate limiting with dedicated budgets per feature. Noisy workspaces can't starve the rest.
Token metering
Per-model counters track tokens-in and tokens-out for every RAG turn, with full usage visibility in your dashboard.
Workflow
Set it up once. It keeps itself current.
01
Connect GitHub
Add a fine-grained token and a single webhook. Credentials are encrypted at rest and never shown back to you.
02
Ingest and graph
A background worker clones the repository, embeds it into Pinecone, and builds the dependency graph that grounds every answer.
03
It maintains itself
From the next push onward, your documentation, diagrams, security, and answers update on their own. There is nothing to regenerate by hand.
Voices from the field
Teams trust their
own docs again.
Six perspectives on what changes when your codebase knowledge stays current.
Half of my code-review work just disappeared. The PR companion catches the obvious bugs and lint issues so I can focus on logic and design.
Manoj PradeepDoctor & Tech Geek
Our architecture diagram used to be out of date within a month. Now it redraws itself on every merge, and I trust it enough to present in a stand-up without screenshots and arrows.
Sathyan GTeam Lead (Java) · 11 yrs experience
I onboarded onto a five-year-old codebase in two days instead of two weeks. The chat answered everything I would have spent an afternoon grepping for — and it was actually current.
Shiksha ChauhanPython Django Developer
Once the docs stopped going stale, people started trusting them again. That alone changed how the team works, and ramp time dropped from weeks to days.
Shajim KhanEngineering Head
The RAG is genuinely sharp, and the answers track the code as it changes. It answers faster than I can switch tabs, and the citations land on real files I can verify.
SingaravelTech Architect
Setup took ten minutes. Three months later it's running on every service we own and we haven't touched the configuration once — it just stays current.
Arun BangaruFull-Stack Developer
Free while in Beta
Your docs will never be
out of date again.
Connect a repository in a few minutes. From then on, every merge keeps your documentation, diagrams, and answers current, on the web and in VS Code, with nothing left for you to maintain.