A custom fork that keeps evolving
Your patch set changes as products develop. You want a plan for supported differences, eligible backports, regression coverage and contributions that could reduce divergence.
In development · Register interest
OpenCV Enterprise Partnership
Build what comes next. Together.
For organizations that need continuing OpenCV co-engineering across custom forks, hardware platforms and product generations, with scheduled work and clear acceptance criteria.
Indicative annual pricing
From US$400,000 / yearThree-year agreement, billed annually. Qualification and taxes extra. Planned offering; final scope and pricing at launch.OpenCV stays free and open source.
Enterprise support is entirely optional.
Enterprise support is entirely optional.
- Your details
- Your needs
Register your interest
✓ Your registration is saved
What does your team need?
Help shape OpenCV Enterprise. This step is optional, and you’re already on the launch list.
You’re on the list.
Your registration is saved. We’ll keep you informed about the OpenCV Enterprise launch.
Who this tier is for
Is Partnership the right fit?
Partnership is for a platform team with continuing development work to plan, not just incidents to escalate. It extends the Premier foundation with reserved engineering capacity, a maintained integration strategy and a regular working cadence. The aim is to support differentiated products while reducing avoidable maintenance of a separate implementation.
Hardware-specific OpenCV work
An accelerator or embedded platform needs agreed integration, optimization and comparisons across its supported paths. Qualification must name the actual boards, software stacks and tests.
Several product generations
Multiple independent source lines can serve a portfolio. Their dependencies and release schedules need explicit ownership rather than an assumption that one successful build covers the rest.
Your planned package
What Partnership includes.
| Included scope | Planned allowance |
|---|---|
| Indicative annual fee | From $400,000 |
| Product families | 3 |
| Maintained baselines | 4 |
| Qualified build profiles | 8 total |
| Reserved engineering | 60 days / year |
| S1 initial response | 1 business hour |
| Standard support window | 8x5 |
| Working cadence | Weekly active-work reviews; quarterly roadmap planning |
Indicative annual fee for a three-year commitment, billed annually. Taxes and initial qualification are separate. Allowances are totals across the agreement, not per family or baseline.
The Premier foundation.
Priority support, covered maintenance, certified binaries and product-specific qualification for the supported portfolio.
60 reserved engineering days.
A scheduled backlog with acceptance criteria for fork evolution, optimization, test integration or bounded migration and porting work.
A maintained integration strategy.
Patch-set review, reduction of avoidable divergence and upstream contribution preparation, subject to the project's normal review process.
An ongoing engineering relationship.
A named lead, weekly active-work reviews, quarterly roadmap planning and 1-business-hour S1 response within 8x5 coverage.
Illustrative deployment
Three product families, four source lines, eight profiles.
Imagine a platform organization supporting an inspection device family, a mobile-robot platform and an edge-vision SDK. The SDK maintains two independent source lines for different product generations. Each accepted line has two agreed deployment configurations. This is an illustrative portfolio, not a list of platforms or versions already approved for support.
| Coverage item | Illustrative scope | Count / profiles |
|---|---|---|
| Inspection devices | Baseline A | 2 |
| Mobile-robot platform | Baseline B | 2 |
| Edge-vision SDK | Baseline C | 2 |
| Same edge-vision SDK family | Baseline D | 2 |
| Total | 3 families / 4 maintained baselines | 8 profiles |
A bounded workstream might review one accelerated image-processing path, agree CPU/backend output tolerances, integrate representative regression cases and prepare a qualified release. The backlog would specify deliverables and acceptance criteria before work is scheduled. No performance gain, completion date or upstream acceptance is assumed. Routine updates stay within their baseline; an independently maintained new line or configuration changes the agreed scope.
Examples explain scope, not supported-version or hardware availability. Each exact source line, configuration and acceptance criterion is agreed after assessment.
Certified by OpenCV
A release record your team can use.
All binaries delivered under OpenCV Enterprise Partnership will be certified by OpenCV, including builds from a custom fork after its acceptance and qualification. Upstream CI results do not automatically qualify downstream changes.
- An exact source and patch record, build recipes, dependency manifests, signed artifacts and a release certificate.
- A named hardware/software test matrix, recorded results, exclusions and exceptions, with build checks, emulation and hardware runtime testing distinguished.
- An SBOM, relevant vulnerability status, known anomalies and change-impact information, plus agreed output and performance comparisons.
Your existing CI may already be extensive. We review the actual coverage and agree what additional qualification the product needs. Certification applies to that agreed matrix, not all hardware, and it does not confer regulatory or functional-safety approval on your complete product. Final product validation and deployment remain with your team.
Service and engineering
Reserved capacity, tied to an agreed backlog.
Sixty engineering days provide scheduled capacity for fork evolution, optimization, test integration and bounded migration or porting work. Each day is eight hours. This is not a dedicated full-time engineer or a promise that a major port will fit into the allowance. Large ports, additional hardware and formal safety programs require separate scope and pricing.
A named lead, weekly active-work reviews and quarterly roadmap planning keep the work and acceptance criteria visible. Patch-set review can identify avoidable divergence and prepare contributions for upstream consideration. The project’s normal review process governs acceptance; the subscription does not give a customer control of the public roadmap.
Priority support remains part of the Premier foundation: a one-business-hour S1 initial response within the agreed 8x5 window. S1 means a critical supported production failure or material active exploitation with no acceptable workaround. Response starts triage and ownership; it is not a guaranteed repair deadline. Coverage uses an agreed time zone and holiday calendar.
Questions for your team
Start with the engineering work you need to plan.
Which differences need to remain yours?
Describe the private patches, hardware integrations and product behavior that create value. Separate essential differences from changes that could potentially be maintained upstream.
What would count as a completed workstream?
Bring a prioritized backlog with representative workloads, output tolerances and acceptance criteria. A specific integration or test deliverable is easier to schedule than an open-ended request to make the platform faster.
Who owns the dependencies and release decision?
Identify the OpenCV, accelerator, BSP, driver and application owners. Tell us which baselines and hardware generations remain commercially relevant, and where customer data or test access is constrained.
Partnership questions
A few details before you register.
Does every company with a fork need Partnership?
No. A small, stable fork may fit LTS after assessment, while production diagnosis may point to Premier. Partnership is most useful when the fork or platform needs an ongoing engineering plan and scheduled development capacity.
Do engineering days replace maintenance?
No. Covered support, severe-defect remediation, security backports, certification and service reviews continue when the engineering allocation is used. Days fund approved customer-specific work. Unused days expire annually unless agreed otherwise; additional work requires agreed scope.
How do the eight build profiles work?
Eight is the total across the agreement, not eight per baseline or family. Four baselines on two specified stacks each use eight profiles. Each profile identifies its hardware, architecture, OS, toolchain, enabled modules/backends and dependencies. Exact support is confirmed at onboarding.
What are the commercial and lifecycle terms?
The starting fee is from $400,000 annually for a three-year commitment billed annually, excluding taxes. Standard initial qualification is separately scoped, indicatively $25,000-$40,000; complex integrations may need different scope. The agreement defines maintenance end dates and the fix policy. Five-year extensions require assessment.
Does Partnership include 24x7 coverage or complete product approval?
The starting support window is 8x5. 24x7 critical-incident coverage may be scoped separately, with availability and pricing confirmed in the agreement. Component support does not guarantee product uptime or replace your regulatory and functional-safety obligations.
What happens to the open-source code when the agreement ends?
OpenCV remains free and open source. Your rights to received open-source code continue under its license. Future services, release-record access and continuing obligations follow the agreement. Enterprise buys engineering and maintenance commitments, not permission to use OpenCV.
Register your interest
Bring your platform roadmap into the conversation.
Share the product families, source lines, hardware generations and engineering work you want to plan. The offering is in development. Register interest to discuss requirements and request launch information, without a purchase commitment.
Register interest in PartnershipPlanned offering. Final scope, availability and pricing will be confirmed at launch. Indicative fees are in US dollars and assume a three-year commitment, billed annually. Taxes and initial qualification are separate.
OpenCV remains free and open source. Read the OpenCV license information. Compare all three Enterprise tiers.