Multi-repo scanning
Pull every repository across GitHub, GitLab, Bitbucket, and Azure DevOps into one catalog. Auto-rescan on check-in — no public webhook required.
4 VCS providersQorVertex maps how code, APIs, events, and databases connect across every repository in your organization — the couplings single-repo scanners and IDEs never see.
A change to one users table can break five services in three repositories — and nothing in your IDE will warn you, because the producer and consumer never reference each other in code. They only share a name.
QorVertex scans every repo into one catalog and treats shared tables, stored procedures, and message queues as first-class dependencies. So the coupling becomes something you can see, search, and measure.
Every repository, resolved into a single dependency graph — code, data, APIs, and events — that you can traverse across boundaries. Explore the product →
Pull every repository across GitHub, GitLab, Bitbucket, and Azure DevOps into one catalog. Auto-rescan on check-in — no public webhook required.
4 VCS providersCalls, imports, inheritance, and type bindings resolved across project and repository boundaries — with durable edges that survive partial rescans.
The coreShared tables, stored procedures, and physical databases as first-class nodes — with per-column blast radius and cross-language coupling.
Shared DataWho exposes and who consumes each endpoint — REST, gRPC, GraphQL, MCP, and SOAP — with "Called by N" across every repo.
5 protocolsPublishers and subscribers linked through channel names across 10 broker families — Kafka, RabbitMQ, SNS/SQS, Pub/Sub, Sidekiq, JMS, and more.
10 broker familiesWalk dependents transitively from any symbol, table, column, endpoint, or event. Answer "what breaks if I change this?" before you commit.
Change safetyDependency graphs, class and component diagrams, and shared-table data-flow views — with full version history, diff, and restore.
DiagramsFind any class, function, table, endpoint, or package — and every place it's used across all repos, ranked by real usage.
Find anythingAn MCP server that lets Claude Code, Cursor, and Copilot answer about repositories they have never opened — with file:line. No model provider needed; your assistant brings its own.
9 read-only toolsWhich integration and end-to-end suites must run for this change — across repositories. Always a minimum, never an allow-list: what can't be analysed says run everything.
Run less, safelyAn industry XSD, WSDL, or proto compiled into many products couples them by name alone. Trace a schema type through the generated class to every line of code that touches it.
XSD · WSDL · ProtobufWhat a component is deployed into, and what it talks to at run time — Docker Compose, Kubernetes and Helm, JBoss, WebLogic, IIS — wired into the same blast radius.
Compose · K8s · app serversTwo ways to put the catalog in front of a model, and neither sends anything to us. Both are off until you switch them on. See how it works →
An MCP server puts the cross-repo graph inside Claude Code, Cursor, and GitHub Copilot — so they can answer about repositories they have never opened, citing file and line. No model provider needed: your assistant brings its own.
9 read-only toolsAsk inside QorVertex, starting from whatever is on your screen. Inference runs in your cloud account on AWS Bedrock or Google Vertex AI, authenticated by the host's instance role — no long-lived key stored. Every answer shows the queries behind it.
Your cloud, your governanceThe blast radius of a single column change, walked across services and back to the code that calls it.
From source and APIs to databases, message brokers, and how it all deploys — coverage is what makes an org-wide graph possible. See the full list →
Search any symbol, table, endpoint, or package and see every consumer, grouped by repository — not just the ones in the file you're looking at.
→ Org-wide search & dependentsWalk the blast radius transitively — through shared columns, procedures, and message channels — before the change ships.
→ Impact analysisEvery producer and consumer of a shared node, across repositories and languages, on one page with read/write breakdown.
→ Shared DataAdd your source connections. QorVertex clones and parses every repository — TypeScript, JavaScript, Python, Java, C#, Go, PHP, and Ruby, tree-sitter accurate — into a central PostgreSQL catalog.
Symbols, APIs, events, and database access are resolved into shared nodes, so a table or endpoint many services touch becomes one thing they all point at.
Search, traverse the graph, and measure the blast radius of any change. Auto-rescans keep the map current as code lands.
One downloadable bundle, one install.sh. It provisions the whole stack behind an nginx ingress on a single Linux box — your source and your catalog never leave your network.
Self-hosted at every tier. Start free, grow by lines of code analyzed.
Prices are placeholders — tiers are being finalized. Metering is by lines of code scanned.
Request access to the private beta and get the self-hosted bundle. See your organization's real dependency graph — database included.