# Licensing

repowise is AGPL-3.0. What that allows, why internal use creates no obligation to publish your code, and when a company needs a commercial licence.

Repowise is released under
**[AGPL-3.0](https://github.com/repowise-dev/repowise/blob/main/LICENSE)**. You can run it, modify it and
build on it at no cost, including inside a company. Every language and
every intelligence layer ships in the AGPL distribution. Nothing about
the analysis is reserved for paying customers.

## What AGPL asks of you

| What you do | What AGPL requires |
|---|---|
| Run Repowise unmodified, on your own machines or in CI | Nothing |
| Modify it for your own use, without offering it to anyone else | Nothing |
| Modify it and let other people use it over a network | Offer those users the source of your modified version, under AGPL |
| Distribute it, modified or not, for example inside a product you ship | Provide the source under AGPL, including your modifications |

The full terms are in the
[LICENSE](https://github.com/repowise-dev/repowise/blob/main/LICENSE)
file in the repository. Where this table and the licence text differ,
the licence text decides.

## Do we have to open-source our code?

No. Using Repowise inside your company, including on internal servers
and in CI, creates no obligation to publish your code. The AGPL
obligations apply if you modify Repowise and offer it to other people
over a network, or ship it inside your own product. A commercial
licence removes them.

## The hosted service

The hosted service at [repowise.dev](https://repowise.dev) is operated by
Repowise. AGPL obligations fall on whoever runs a modified copy for other
people, so using the hosted service places none on you.

## When a company needs a commercial licence

You need one if the AGPL terms conflict with what you want to do. The
common cases:

- Modifying Repowise and shipping it inside a closed-source product
- Building it into a developer platform you offer to others over a
  network, without publishing your changes
- Redistributing it as part of something you sell

## What the commercial licence covers

The [Enterprise](https://docs.repowise.dev/enterprise#what-the-licence-grants) page has the
full list. In short:

1. The right to modify Repowise without releasing your changes under AGPL
2. The right to embed Repowise in your internal tooling and developer
   platforms
3. A defensive patent grant and IP indemnification
4. Support with SLA-backed response times, and updates during the term
5. The right to audit Repowise's security and compliance practices

An Enterprise deployment runs entirely inside your perimeter: Repowise never
handles your code or data, and your own controls and certifications cover it.
It is also the route to the security, compliance and administration
features listed in the
[Enterprise status table](https://docs.repowise.dev/enterprise#what-the-commercial-licence-adds),
and to [Foresight](https://docs.repowise.dev/hosted/foresight) as it opens.

## Pricing models

Commercial licences come in three models. Every model includes the full
commercial feature set; only the scaling dimension changes. Figures come
in a proposal.

| Model | How it scales | Fits |
|---|---|---|
| **Per seat** | Priced per engineer with dashboard, API or MCP access. Inactive seats are reclaimable, and the seat lifecycle can follow your directory through SCIM, set up with your deployment | Spend that tracks headcount, alongside existing developer-tool billing |
| **Per indexed repository** | Priced per indexed repository, cross-repo workspace intelligence included, with unlimited seats inside the licensed set | Teams where agents and CI do most of the reading, since seat counts stop tracking the value there |
| **Enterprise-wide** | Unlimited seats and repositories, every commercial feature, on-prem or air-gapped, named support | Org-wide standardisation under one contract |

Hybrid arrangements work too, for example enterprise-wide in one
business unit and per repository elsewhere.

## Talk to us

[Book a demo](https://cal.com/repowise-demo/30min?overlayCalendar=true)

Or email [hello@repowise.dev](mailto:hello@repowise.dev).