Self-hosted, air-gapped, commercially licensed.
Everything in repowise, deployed inside your firewall, on a license that is not AGPL, with the identity, indemnification, and compliance controls security and procurement ask for. Open at the core, inspectable, and priced for teams.
You need codebase intelligence that runs where your code lives, on a license that is not AGPL, with the controls your security and procurement teams require.
Most enterprise code intelligence is a closed-source black box behind a six-figure contract, or it is AGPL-licensed in a way your legal team cannot accept, or it ships your source to someone else's cloud. repowise is open at the core, self-hostable inside your firewall, and available on a commercial license with IP indemnification when you need it.
Deployed where your code lives, licensed how procurement needs.
The same five intelligence layers and nine MCP tools, run inside your network, on commercial terms, with the identity and support controls a large org requires.
On-prem and air-gapped
Run the whole platform inside your network. Zero telemetry, no phone-home, and your source code is processed transiently and never persisted. Bring your own LLM key for wiki generation, or run fully offline with a local model via Ollama for zero external API calls.
- Self-hosted: code never leaves your infrastructure
- Bring your own key, or fully offline via Ollama
- Reference HA topology on your own infrastructure (generally available)
- Packaged air-gapped install bundle on the roadmap
A commercial license, not just AGPL
repowise is dual-licensed under AGPL-3.0 and a commercial license. The commercial track removes the AGPL obligation and grants proprietary modification and embedding rights, so you can deploy on-prem, fork internally, or embed repowise in an internal developer platform without the copyleft requirements.
- Removes the AGPL obligation for enterprise use
- Proprietary modification and embedding rights
- IP indemnification (generally available)
- Defensive patent grant (generally available)
SSO and provisioning for the whole org
SAML and OIDC single sign-on across Okta, Entra ID, Auth0, Google Workspace, and generic SAML 2.0, with SCIM provisioning so inactive seats are reclaimed automatically. These identity capabilities are rolling out; role-based access control and multi-tenant deployment are on the roadmap, and we will not present them as already shipped.
- SAML and OIDC SSO (rolling out)
- SCIM user provisioning (rolling out)
- Role-based access control (on the roadmap)
- Multi-tenant deployment (on the roadmap)
Built to run org-wide
A reference high-availability topology, Postgres-backed metadata with S3-compatible artifacts and horizontally scalable MCP servers, plus custom language and framework extensions when your stack needs coverage beyond the standard tiers. Priority support with an SLA backs it all.
- Reference HA topology on customer infra (generally available)
- Custom language and framework extensions (generally available)
- Priority support with an SLA (generally available)
- Multi-repo workspaces with federated MCP queries
From evaluation to org-wide rollout in four steps.
Evaluate
Start with the open-source core under AGPL-3.0, self-hosted, and inspect every heuristic before you commit.
Deploy in your environment
Stand up repowise inside your firewall, on-prem or air-gapped, with BYO key or fully offline via Ollama.
Integrate identity and workflows
Wire up SSO and SCIM (rolling out) and connect the MCP endpoint to Claude Code, Cursor, Cline, and Codex across teams.
Roll out org-wide
Move to a commercial license with IP indemnification, the reference HA topology, and priority support with an SLA.
Open core, enterprise controls.
Self-hosted deployment
Run the whole platform inside your network with zero telemetry. Reference HA topology is generally available; a packaged air-gapped bundle is on the roadmap.
Commercial licensing
Dual-licensed AGPL-3.0 plus a commercial track that removes the AGPL obligation and grants proprietary modification and embedding rights.
SSO and SCIM
SAML and OIDC single sign-on with SCIM provisioning, rolling out now. RBAC and multi-tenant deployment are on the roadmap.
.NET-first depth
C# is a full-tier language with framework-aware edges for ASP.NET MVC and Minimal API, EF Core, and gRPC-dotnet, alongside 14 other languages.
Security and compliance
Deterministic scoring with zero LLM in the loop, so EU AI Act high-risk obligations do not apply. Usage-aware CVE triage and SBOM are generally available on hosted.
Priority support and SLA
Priority support with an SLA, IP indemnification, a defensive patent grant, and custom language and framework extensions, all generally available.
Enterprise code intelligence has meant six-figure annual contracts and closed-source black boxes. repowise is open at the core, self-hostable inside your firewall, and priced for teams, with a commercial track, IP indemnification, and priority support when you need it.
Questions, answered
Can we self-host or run air-gapped?
Yes. The entire platform runs inside your network with zero telemetry and no phone-home, so your code never leaves your infrastructure. You can bring your own LLM key for wiki generation or run fully offline with a local model via Ollama, which means zero external API calls. A reference high-availability topology on your own infrastructure is generally available. A packaged air-gapped install bundle is on the roadmap; today air-gapped deployments are configured with our support team.
Do you offer a commercial license that removes the AGPL obligation?
Yes. repowise is dual-licensed under AGPL-3.0 and a commercial license. The commercial license removes the AGPL obligation and grants proprietary modification and embedding rights, so you can deploy on-prem, modify the source, or embed repowise inside an internal developer platform without the copyleft requirements. It also includes IP indemnification and a defensive patent grant, both generally available.
Do you support SSO and SCIM?
SAML and OIDC single sign-on (Okta, Entra ID, Auth0, Google Workspace, and generic SAML 2.0) plus SCIM user provisioning are rolling out. Role-based access control and multi-tenant deployment are on the roadmap. We will share current status and timelines for your identity stack on a demo call, and we do not present rolling-out capabilities as already shipped.
Is there IP indemnification?
Yes. The commercial license includes IP indemnification and a defensive patent grant, both generally available today. These are exactly the protections procurement and legal teams ask for when adopting an open-core tool, and they sit alongside proprietary modification and embedding rights.
What about data residency? Does our code leave our infrastructure?
No. repowise is self-hosted, so your source code is processed transiently and never persisted, and it never leaves your infrastructure. What gets stored is the dependency graph, non-reversible embedding vectors, generated wiki pages, and git metadata, all on hardware you control. With a bring-your-own-key setup you rely on your LLM provider's data policy, and with a fully offline Ollama setup there are no external API calls at all.
Do you support C# and .NET?
Yes, with full-tier depth. C# is one of the nine full-pipeline languages alongside Python, TypeScript, JavaScript, Java, Kotlin, Go, Rust, and C++. That includes AST parsing, import and call resolution, and framework-aware route-to-handler edges for ASP.NET MVC and Minimal API, EF Core, and gRPC-dotnet. repowise covers 15 languages in total across the headline tiers.
What support and SLA is available?
Priority support with an SLA is generally available on commercial agreements, along with custom language and framework extensions if your stack needs coverage beyond the standard tiers. Quantified response-time targets are set per contract, so we will scope them with you during procurement rather than quoting a single number here.
How is repowise licensed and priced for a large organization?
repowise is dual-licensed: AGPL-3.0 for open-source use, and a commercial license for enterprises, embedding, and on-prem deployment. Commercial agreements come in three shapes: per-seat (priced per engineer, with reclaimable inactive seats and SCIM-managed provisioning), per-repo (priced per indexed repository with unlimited seats inside the licensed set), and enterprise-wide (unlimited seats and repos, all features, on-prem or air-gapped, with named support). Book a demo or email sales to scope the right model.