Accelerating mission-critical computer vision innovation. Turn your computer vision challenge into a production-ready MVP

Kindly review these guidelines before applying. They outline the Program’s eligibility and selection process, project scope, MVP limitations, applicant responsibilities, data and confidentiality considerations, timelines, and terms governing participation.

1. Submission of an application does not guarantee participation in the Obraz Vision Catalyst Program.
2. Participation in the Program is entirely at the sole discretion of Obraz.
3. Obraz reserves the right to accept or reject any application based on its evaluation criteria, project relevance, technical feasibility, available engineering capacity, or other internal considerations.
4. Obraz may request additional information or clarification from an applicant during the evaluation process before making a selection decision.
5. The applicant must provide accurate and complete information in the application form and must have the necessary authority to submit the application on behalf of the organization.
6. Selection will generally consider the clarity of the Computer Vision problem, technical feasibility, potential impact, alignment with the Program, potential for measurable outcomes, and the organization’s ability to participate in the project.
7. The final scope of work for a selected project will be determined by Obraz following technical evaluation and discussion with the selected organization.
8. The Program does not guarantee that every capability, service, technology, or development activity described on the Program website will be provided to every selected organization.
9. Depending on the project, support may include technical discovery, solution architecture, secure data strategy, dataset planning, annotation support, computer vision model development, MVP engineering, and deployment guidance.
10. The Program covers the development of one agreed Minimum Viable Product (MVP) or first-version solution only.
11. The Program does not automatically include the development of a complete commercial or production-scale product.
12. Features, enhancements, additional functionality, integrations, future versions, production deployments, maintenance, long-term support, or work outside the agreed scope are not included in the Program.
13. Any work outside the agreed MVP scope will require a separate commercial agreement and may involve additional fees.
14. Timelines are dependent on project complexity, technical requirements, data availability, applicant responsiveness, and Obraz’s available engineering capacity.
15. Any estimated timeline provided by Obraz may change depending on project requirements and circumstances.
16. Applicants are responsible for providing the information, datasets, technical context, domain knowledge, feedback, approvals, and other inputs reasonably required for the agreed project.
17. Delays in providing required information, feedback, access, approvals, or project dependencies may affect the project timeline.
18. Applicants should not submit classified, highly sensitive, personal, regulated, or confidential information through the public application form unless specifically requested or an appropriate secure mechanism has been provided by Obraz.
19. Confidentiality, intellectual property, data handling, and other project-specific arrangements will be governed by separate agreements where applicable.
20. Participation in the Program does not automatically transfer ownership of Obraz’s pre-existing intellectual property, proprietary software, platforms, tools, methodologies, infrastructure, or technology to the applicant.
21. Obraz’s proprietary technology, including its internal tools and LabelOps annotation platform, remains subject to applicable intellectual-property protections and separate agreements.
22. Participation in the Program does not guarantee production deployment of the resulting MVP.
23. Production deployment, enterprise-scale implementation, additional integrations, maintenance, monitoring, support, and future development may require a separate commercial engagement.
24. Obraz does not guarantee that the MVP will achieve a specific commercial outcome, model accuracy, revenue result, regulatory approval, or operational result unless expressly defined and agreed within the applicable project scope.
25. Where a project involves regulated, safety-critical, medical, defense, biometric, surveillance, or other high-risk applications, additional legal, regulatory, security, compliance, and technical requirements may apply.
26. Selection into the Program does not constitute regulatory approval, certification, government authorization, medical approval, defense authorization, or compliance certification.
27. Applicants remain responsible for obtaining any regulatory approvals, certifications, licenses, permissions, or authorizations applicable to their own products, services, data, or operations.
28. Obraz may decline or discontinue a project if the proposed use case becomes technically infeasible, falls outside the Program scope, creates unacceptable security or compliance concerns, or cannot reasonably be supported within available engineering capacity.
29. Obraz reserves the right to modify, suspend, postpone, or discontinue the Vision Catalyst Program at any time.
30. Program participation does not create an employment, partnership, joint venture, investment, agency, or other formal business relationship between Obraz and the applicant unless separately agreed in writing.
31. Submission of an application does not itself create an obligation for Obraz to provide development services.
32. A project will proceed only after the organization has been selected, the applicable scope has been defined, and any required project-specific agreements have been completed.
33. Any additional commercial work requested after completion of the agreed MVP may be evaluated and offered separately by Obraz.
34. The applicant must review and agree to the Program Terms & Conditions before submitting the application.
35. The applicant confirms that they are authorized to submit the application on behalf of the organization.