For teams and enterprise
One index for the whole engineering org.
Review every pull request the same way, see where risk sits across repositories, and govern the code your agents write. Hosted on Teams, or inside your own network with nothing leaving it.
What the org gets
Every repository, read the same way by everyone.
A shared index per repository
Indexed once, read by every member, reviewer and agent from the same snapshot.
PR review and gates
One comment per pull request, an optional merge gate, and CI gates for coverage, doc drift, secrets and change risk.
Portfolio health
One ranked list of what to fix this week across every repository, with hotspots and trends.
Contracts and blast radius
HTTP, gRPC and topic contracts between repositories, and how far a change reaches beyond its own repo.
Ownership and bus factor
Who knows each file, rolled up across repositories, with bus-factor risk flagged early.
AI provenance
Which commits coding agents wrote, from git history alone, next to their health and owners.
Team MCP
Every member's agent reads the same index, one URL per repository or per workspace.
Integrations
One org GitHub App install, alerts to Slack or a signed webhook, Jira and Confluence in beta.
One platform
One index in place of five point tools.
Docs, code health, PR review, ownership and agent context usually arrive as separate tools, each reading the code its own way. repowise reads it once, and every team draws from that one index.
- Documentation generatorsDocs and an architecture map, built from the code graph
- Code-health scannersHealth per file, checked against real bug fixes, with a fix-first list
- PR risk and review botsOne comment per pull request, gates in CI
- Dependency and ownership dashboardsContracts, blast radius, owners and bus factor across repositories
- Agent context toolsTen MCP tools, hooks and a generated CLAUDE.md for every agent
One vendor
One contract and one support line for the whole surface.
One bill
Licensed per seat, per repository or enterprise-wide, under one contract.
One security review
One data flow to assess, and it can run inside your network.
One answer
Reviewers, dashboards and agents agree, because they read the same snapshot.
Review
Every pull request reviewed the same way.
One comment per pull request: what the change can break, files that usually change together, owners and the health change. Signals mode makes no model call; AI review draws from the team credit pool.
- Optional merge gate: a check run, advisory or blocking
- CI gates for patch coverage, doc drift, new secrets and unusual change risk, on GitHub Actions or GitLab
Across repositories
See how your repositories depend on each other.
A workspace finds the HTTP, gRPC and topic contracts between repositories, the files that change together across them, and how far a change reaches beyond its own repo.
- Workspace chat and a workspace MCP endpoint
- Team-owned workspaces on Teams
Portfolio
Know where risk sits before it ships.
One list of what to fix this week across every repository, ranked by health, churn and bug-fix history. Nightly signals send hotspot drift, bus-factor risk and health decline to Slack or a signed webhook.
Governance
Govern the code your agents write.
See which commits coding agents wrote, from git history alone, next to health and ownership. Security triage ranks CVEs by whether your code imports the vulnerable package, and scans secrets across the whole history.
- CycloneDX SBOM and VEX export
- PCI-DSS and SOC 2 control-coverage reports on Teams: evidence maps, not audits
- Insert-only audit trail for security data, including agent reads over MCP
Team MCP
One context for every agent on the team.
Every member's agent connects to the same index with a personal key: one URL per repository, one per workspace. Reviewers, developers and agents read the same snapshot, indexed once.
# one repository
https://api.repowise.dev/mcp/{owner}/{repo}
# one workspace, across its member repositories
https://api.repowise.dev/mcp/w/{workspace_id}
Authorization: Bearer YOUR_API_KEYIntegrations
It fits the tools you already run.
One org install of the GitHub App covers every member. GitLab, Bitbucket and any other CI run the same gates from the CLI. Alerts go to Slack or your own endpoint.
- Claude Code
- Codex
- Cursor
- GitHub Copilot CLI
- Any MCP client
- VS Code
- GitHub PR bot
- GitHub Actions
- GitLab CI
- Bitbucket and any CI
- Slack
- Jira
- Confluence
Deployment
Run it where your code lives.
Graph, git history, health, change risk, tests, dead code and PR review make no model call. Raw source is parsed in memory and never stored.
- Self-hosted, commercialYour VPC or an air-gapped networkOnly the integrations you configure. Nothing at all in air-gapped mode.
- Self-hosted, open sourceYour machines, with the index next to the repoOpt-out anonymous CLI telemetry, and your own model provider if you turn prose on.
- Hosted TeamsShort-lived containers; each clone is deleted after its runYour code is read by the hosted platform, under the data handling terms.
Licensed the way you buy
A commercial licence per seat, per indexed repository with unlimited seats, or enterprise-wide.
Support with an SLA
A named contact, a response-time SLA and a quarterly architecture review.
IP indemnification
IP indemnification and a patent grant, and no AGPL obligations on your code.
Built for your stack
Custom language and framework extensions, unlimited repositories and configurable index concurrency.
SAML or OIDC single sign-on and SCIM provisioning are scoped into an enterprise rollout. Compliance reports are control-coverage evidence from your own findings, not certifications.
FREQUENTLY ASKED
Questions, answered
How is Teams priced?
Per seat with a 3-seat minimum: $20 per seat per month, or $16 billed yearly. Each seat adds $5 a month to one shared credit pool, and the team shares 25 repositories.
How is the enterprise licence priced?
Per indexed repository, with unlimited seats inside the licensed set. More of the code in a repository is now written and read by agents and CI, so seat counts stop tracking the value.
What is the difference between Pro and Teams?
Pro is one person with 5 repositories and a personal balance. Teams indexes each repository once for every member and adds owner, admin and member roles, one org GitHub App install, portfolio views, team workspaces and alert webhooks.
Do we have to open-source our code because of the AGPL?
No. Using repowise inside your company, including on internal servers, creates no obligation to publish your code. A commercial licence removes the obligations that apply to modifying repowise and offering it to others.
Does the analysis send code to a model?
No. The graph, git history, code health, dead code and security scanning make no model call. Written documentation and chat use a model: on hosted repowise through our provider accounts, self-hosted through the provider and key you configure, or fully offline.
Do you support SSO and SCIM?
As part of an enterprise agreement. Tell us your identity provider and directory, and we scope SAML or OIDC single sign-on and SCIM provisioning into your rollout.
Get started
Put the whole org on one index.
Book a call to plan a rollout in your network, or start a hosted team from 3 seats today.