A stable integration
Your team wants eligible fixes on an accepted source line, with clear records of what changed and how it was tested.
In development · Register interest
OpenCV Enterprise LTS
Keep proven products supported.
For established products that need controlled maintenance of a stable OpenCV integration, with qualified releases and a written support horizon.
Indicative annual pricing
US$150,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 LTS the right fit?
LTS is for a product that already works and needs an accountable maintenance path. Its main value is keeping component work aligned with your product plan, especially when a broad upgrade would introduce testing and integration work that the product does not otherwise need.
A long product life
Medical imaging software, industrial inspection systems and embedded devices can have support horizons that extend beyond their original development cycle.
A controlled change process
Your engineering and quality teams need source, build and test evidence to make their own release decisions. Component qualification supports that work; it does not replace product validation.
Your planned package
What LTS includes.
| Included scope | Planned allowance |
|---|---|
| Indicative annual fee | $150,000 |
| Product families | 1 |
| Maintained baselines | 1 |
| Qualified build profiles | 2 total |
| Customer engineering | 10 days / year |
| S1 initial response | 4 business hours |
| Standard support window | 8x5 |
| Technical reviews | Quarterly lifecycle review |
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.
Maintenance that stays with your baseline.
Applicable security backports and covered severe-defect remediation, with a quarterly qualification review and releases when needed.
Every binary certified by OpenCV.
Signed builds, source and patches, a software bill of materials (SBOM), test results, change notes and a release certificate for supported configurations.
A practical regression suite.
Agreed functional checks and numerical tolerances established at onboarding and rerun for each delivered update.
Continuity and access.
A named service owner, quarterly lifecycle review, 4-business-hour S1 response within 8x5 coverage, and 10 engineering days per year.
Illustrative deployment
Two appliance models, one maintained integration.
Imagine standard and compact models of an inspection appliance that share substantially the same OpenCV integration and regression tests. The team needs one accepted source line, built for two agreed Linux configurations. This is an illustrative counting example, not a statement that a particular release or device is already supported.
| Coverage item | Illustrative scope | Count / profiles |
|---|---|---|
| Product family | Inspection appliances: standard and compact models | 1 |
| Maintained baseline | One accepted source line and patch set | 1 |
| Build profiles | That baseline on agreed Linux x86-64 and Linux Arm64 stacks | 2 |
A covered parser defect would be assessed against that baseline. An eligible fix would be backported and qualified against the agreed tests and numerical tolerances before a certified update is delivered. The customer would still validate the appliance and decide when to deploy it. Routine maintenance releases do not automatically consume another baseline or profile.
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 LTS will be certified by OpenCV. Each delivered binary will be tied to its exact source, build environment, supported configurations and qualification results.
- Signed binaries and hashes, source revision and patches, build recipes and pinned dependency manifests.
- A release certificate and test record identifying the tested matrix, acceptance criteria, results, exclusions, known anomalies and approved exceptions.
- A software bill of materials (SBOM), relevant vulnerability assessments, change notes and installation or rollback instructions.
OpenCV certification is first-party qualification of the supplied binary. It is not testing on all hardware, regulatory approval or a functional-safety certificate for your product. Your team retains final integration testing and release approval. A quiet quarter still brings a maintenance and exposure report, even if no code change is needed.
Service and engineering
Maintenance continues between releases.
LTS includes applicable security backports and covered severe-defect remediation, with a quarterly qualification review and releases when needed. A named service owner and quarterly lifecycle review help keep the accepted configuration, maintenance dates and planned changes visible.
The ten engineering days are for approved customer-specific integration, optimization, fork evolution or enhancements. One day is eight hours. Covered support, severe-defect remediation, security backports, certification and ordinary service reviews do not consume that allowance and continue after it is used. Unused days expire annually unless agreed otherwise.
The standard window is eight hours per business day, five days per week, in an agreed time zone and holiday calendar. S1 means a critical supported production failure or material active exploitation with no acceptable workaround. A qualified engineer begins triage within four business hours; that is not a guaranteed repair deadline.
Questions for your team
What would make LTS useful to your team?
What needs to stay stable?
Identify the source revision, patch set, enabled modules and build environment that your product depends on. An installed version number alone does not describe the supported integration.
How will you know a fix is acceptable?
Bring representative regression cases, expected outputs, numerical tolerances and any meaningful resource limits. We can then discuss the acceptance basis and the customer tests that remain yours.
How long does the product need support?
Share its remaining service life, planned upgrades and retirement constraints. The starting agreement is a three-year commitment billed annually, with written maintenance end dates and a fix policy.
LTS questions
A few details before you register.
Will you support any old OpenCV version?
Support depends on assessment of the exact code, dependencies, hardware and testability. We confirm the accepted baseline and configurations in the agreement. Older releases and private forks may need additional work before they can enter service; there is no blanket supported-version promise.
Can a small private fork qualify for LTS?
Potentially. A stable patch set may fit when the main need is continuity. Its own build and test coverage must be assessed; upstream test results do not automatically qualify a private fork. Ongoing fork development may be better suited to Partnership.
What costs sit outside the annual fee?
Initial qualification is separate, indicatively $25,000-$40,000 for a standard integration. Taxes and work beyond the agreed allocation, including additional configurations, material ports or migrations, are separate. Five-year extensions require supportability assessment.
When should we choose Premier instead?
Consider Premier when production incidents require a one-business-hour S1 response during the agreed 8x5 window, deeper customer-specific diagnosis or more engineering capacity. Its planned scope includes two baselines, four profiles and thirty engineering days; LTS emphasizes stable maintenance.
Does buying support change our open-source rights?
No. OpenCV remains free and open source, and Enterprise is optional. Rights to received open-source code continue under its license when the subscription ends. Service end dates, access to release records and any continuing obligations are defined in the agreement.
Register your interest
Tell us which integration you need to maintain.
Share your OpenCV version or fork, product family, build configurations and required maintenance horizon. Registering interest helps shape the offering and lets you request launch information; it creates no purchase commitment.
Register interest in LTSPlanned 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.