Pricing
ProPR is self-hosted in both editions, so you hold the AI account and pay your provider directly. Community covers reviewing on every supported platform and provider. Enterprise adds what larger installations need.
Community
Free
Self-hosted, and the default for a fresh installation
Everything needed to review pull requests in production. This is the default edition, so a fresh installation starts here and stays there until you change it.
Read the quickstartIncludes
- AI review on every pull request, across as many repositories as you run
- Azure DevOps, GitHub, GitLab and Forgejo, cloud or self-hosted
- Every AI provider, including Anthropic, Bedrock, Vertex and models you host
- Thread memory, security passes and evidence-backed verification
- ProCursor repository knowledge and the full review record
- Per-review cost reporting
One review runs at a time, and reviews are triggered by webhook or an API call.
Enterprise
Talk to us
Tell us about your installation and we will quote it
For installations serving several teams, or where sign-on, spend control and isolation have to be answered before anyone will approve a rollout.
Contact usEverything in Community, plus
- Single sign-on through your identity provider
- Several pull requests reviewed at once, as many as you size for
- More than one source-control connection per team
- Scheduled repository sweeps, and replies to @-mentions in a pull request
- Spend limits ProPR enforces, with forecasting and roll-ups
- Multiple isolated teams, each with its own credentials, budget and policy
- A per-team policy naming the only AI destinations your code may reach
- Your negotiated model prices, so cost figures match your invoice
- Quality metrics collected per finding, so review value can be measured over time
The admin console and the technical documentation call this the Commercial edition.
What each edition includes
The split is enforced at runtime, and the admin console marks anything Enterprise covers as disabled, so you can see what a licence would change before you buy one.
| Capability | Community | Enterprise |
|---|---|---|
| Reviewing | ||
| AI review on pull requests | Included in Community | Included in Enterprise |
| Repositories and reviewers covered | As many as you run | As many as you run |
| Reviews running at once | One at a time | As many as you size for |
| How a review starts | Webhook or API call | Webhook, API call or scheduled sweep |
| Replies to @-mentions in a pull request Mentions are found by the same scheduled scan | Not included in Community | Included in Enterprise |
| Security and second-opinion review passes | Included in Community | Included in Enterprise |
| Thread memory, so settled discussions stay closed | Included in Community | Included in Enterprise |
| Findings verified against your code before posting | Included in Community | Included in Enterprise |
| Full review record and diagnostics | Included in Community | Included in Enterprise |
| Prompt overrides and repository conventions | Included in Community | Included in Enterprise |
| Quality metrics tracked per finding over time Off until a team opts in, because classification spends tokens | Not included in Community | Included in Enterprise |
| Source control | ||
| Azure DevOps, GitHub, GitLab and Forgejo | Included in Community | Included in Enterprise |
| Self-hosted hosts and enterprise editions | Included in Community | Included in Enterprise |
| Source-control connections per team | One | As many as you need |
| AI providers and models | ||
| Every provider, including models you host yourself | Included in Community | Included in Enterprise |
| Named logical models, so switching provider is one setting | Included in Community | Included in Enterprise |
| Bundled model catalog with context windows and list prices | Included in Community | Included in Enterprise |
| Your negotiated model prices | Not included in Community | Included in Enterprise |
| Hand-define a model the catalog does not list | Not included in Community | Included in Enterprise |
| Restrict which AI hosts a team may reach | Not included in Community | Included in Enterprise |
| Cost control | ||
| What each review cost, and which model produced it | Included in Community | Included in Enterprise |
| Monthly, per-pull-request and per-review spend limits | Not included in Community | Included in Enterprise |
| Spend forecasting for the period | Not included in Community | Included in Enterprise |
| Spend rolled up across every team | Not included in Community | Included in Enterprise |
| Access and teams | ||
| Local accounts | Included in Community | Included in Enterprise |
| Single sign-on | Not included in Community | Included in Enterprise |
| Isolated teams | One | As many as you need |
| Encrypted credentials, never shown again after saving | Included in Community | Included in Enterprise |
| Configuration changes recorded with who made them | Included in Community | Included in Enterprise |
| Running it | ||
| Self-hosted on your own infrastructure | Included in Community | Included in Enterprise |
| Runs on an isolated network with no internet access | Included in Community | Included in Enterprise |
| Your existing metrics, tracing and logging | Included in Community | Included in Enterprise |
Questions about the editions
Is Community a production edition?
Yes. It is what a fresh installation runs, and it covers reviewing across as many repositories and reviewers as you have.
Which AI providers does Community cover?
All of the ones ProPR supports, including Anthropic, Bedrock, Vertex and models you host yourself. You hold the AI account and bring your own key in either edition.
What happens to our configuration if a licence lapses?
It stays in the database exactly as you left it. Crawl configurations, budgets and extra connections are all retained, and they resume being exercised once the capability is available again.
How does ProPR behave when a feature needs a licence?
The API answers with a message naming the capability, and the admin console shows the feature as disabled, so you can see what a licence would change.
What do we pay besides the licence?
Your AI provider bills you for model usage, and you supply the infrastructure ProPR runs on. Both editions are self-hosted, so your code and your credentials stay inside your environment.
Can we move from Community to Enterprise later?
Yes, and it takes no migration. A platform administrator sets the edition in the admin console, and the licensed capabilities become available on the configuration you already have.
Ready to innovate with Meister Dev?
Join us in building the next generation of AI-driven tools. Let's create something extraordinary together.
Get in Touch