# Entelligence Pricing

> Startup, Scale, and custom Enterprise plans based on team size and review volume. Additional reviews are $1 each.

Source: https://entelligence.ai/pricing

## Choose the plan that fits your team.

Plans are based on team size and monthly review volume.

- **Startup** (Up to 15 engineers): $750 / month. AI code review for smaller teams. Includes: Self-healing code review; 300 reviews / month ($1 per review after).
- **Scale** (16–50 engineers): $2,500 / month. More review capacity as the team grows. Includes: Self-healing code review; 1,000 reviews / month ($1 per review after).
- **Enterprise** (Custom): Custom pricing. For larger teams and advanced requirements. Includes: Self-healing code review; Agent Insights; Model Router; Knowledge Base; Self-hosting.

## Start with the engineering problem you can measure.

Each product tackles a different part of quality, cost, and delivery. Start with the workflow you need now, establish a baseline, and expand from there.

- [Entelligence Model Router](https://entelligence.ai/model-router.md): Route eligible coding-agent requests by quality and cost, keeping stronger models available for harder work instead of paying frontier-model prices on every turn. Scope: Balanced / Eco policies; Request-level routing; Session cost & savings; Proxy or BYOK.
- [Code Review](https://entelligence.ai/code-review.md): Catch production-impacting issues with repository-wide context and prioritized first-pass review, then measure whether the feedback is actually addressed. Scope: Repository-wide context; Guidelines & Learnings; Prioritized findings; Review analytics.
- [Agent Insights](https://entelligence.ai/agent-insights.md): See where coding-agent spend goes, how workflows behave, and what that activity produces across projects, repositories, and outcome categories. Scope: Spend & budgets; Retries / context health; Outcome breakdown; Project & member drill-down.
- [Ask Ellie](https://entelligence.ai/ask-ellie.md): Ask engineering questions across connected code, pull requests, incidents, delivery, and agent activity, then continue into permitted actions where supported. Scope: Web & Slack; Multi-source questions; Permission-aware context; Permitted actions.

**Not sure which product to start with?** If more than one looks relevant, we can help you pick the smallest useful starting point for your team.

## Results engineering teams can actually measure.

- **Allocore** (Jun 2025): 45+ hours saved every month. Engineering review time returned to the team. [Case study](https://entelligence.ai/case-study/allocore)
- **Bespoke Labs** (Jul 2026): 99% review success. Reviews completed in ~4 minutes on average. [Case study](https://entelligence.ai/case-study/bespoke-grades-the-world-s-ai.-entelligence-grades-bespoke-s-code)
- **Docket** (Jul 2026): 37 rules learned from past fixes. Docket's own engineering lessons carried into future reviews. [Case study](https://entelligence.ai/case-study/how-docket-uses-entelligence-to-make-sure-the-same-bug-never-ships-twice)

## Security and data

- **SOC 2 Type II**: Request the current report, scope, and bridge letter.
- **Workspace controls**: Review roles, repository access, and connected destinations.
- **Confirm your data boundary**: Review architecture, storage, and deployment commitments for your setup.
- **Use metrics with context**: Signals are diagnostic, not a score for individuals.

## What teams usually want to know before a pilot.

- **Why isn't there one fixed price on this page?** Commercial terms can vary by plan, billed seats, usage, product access, and deployment. The values in your current workspace and signed order form are the source of truth.
- **Can we start with a small pilot?** Yes. Start with one measurable workflow, a small set of repositories or users, and a baseline you can compare against. Expand after you verify the result and operational fit.
- **What can appear in Billing?** Depending on your workspace, Billing can include subscription state, billed seats, LLM usage and overage, invoices, and Model Router credits or balance where routing is enabled.
- **Do we need every product?** No. Product access and rollout can vary by plan, connectors, deployment, role, repository, and rollout state. Start with the workflow you need now.
- **Is Agent Insights included in Startup, Scale, or Enterprise?** Agent Insights is included in Enterprise. It is not included in Startup or Scale.
- **How should we choose the first product?** Choose the problem with the clearest baseline: review quality, AI spend, delivery friction, or recurring production risk. A good pilot should give you something concrete to compare before and after.
- **Can security review happen before purchase?** Yes. Review the product's visible controls, then request the current security and contractual documents for deployment boundaries, retention, model-provider terms, compliance scope, and other commitments.
- **Is Agent Insights an employee-monitoring tool?** Agent Insights is designed for workflow and cost diagnosis, not standalone employee scoring. Its metrics should be interpreted with repository, task, coverage, and team context, not used alone as individual performance measures.
- **What happens on the call?** We will review the workflow you are trying to improve, the systems it depends on, any security or deployment requirements, and the smallest pilot that can give your team a useful answer.

## Start with one workflow. Expand when it proves value.

Book a demo or talk to sales: https://calendly.com/aiswarya-qlnt/1-1-aiswarya-1