The Khronos Group is an open, non-profit, member-driven consortium of over 150 industry-leading companies creating advanced, royalty-free interoperability standards for 3D graphics, augmented and virtual reality, parallel programming, vision acceleration and machine learning. Khronos standards include Vulkan®, Vulkan® SC, OpenGL®, OpenGL® ES, OpenGL® SC, WebGL™, SPIR-V™, OpenCL™, SYCL™, OpenVX™, NNEF™, OpenXR™, 3D Commerce™, ANARI™, and glTF™. Khronos members are enabled to contribute to the development of Khronos specifications, are empowered to vote at various stages before public deployment and are able to accelerate the delivery of their cutting-edge accelerated platforms and applications through early access to specification drafts and conformance tests.
To get involved, please visit our Membership page.
IP Zones are an organizational mechanism layered over the IP framework. The Khronos Board identifies which working groups are routinely sharing design contributions and organize them into IP Zones in order to clearly manage a web of Working Group Exclusion Certificates. An ‘IP Zone’ is simply an agreed set of working groups that are sharing design contributions. Learn more about Khronos’ IP Framework in Attachment A of the Khronos membership agreement.
Multiple Khronos standards are often relevant to developers with similar requirements. Khronos currently identifies six such market segments. Working Groups within a segment coordinate and cooperate to develop coherent solutions and outreach programs.
Application developers may always freely use Khronos Standards when they are available on the target system. To enable companies to test their products for conformance, Khronos has established an Adopters Program for each standard. This helps to ensure that Khronos standards are consistently implemented by multiple vendors to create a reliable platform for developers. Conformant products also enjoy protection from the Khronos IP Framework, ensuring that Khronos members will not assert their IP essential to the specification against the implementation.
To learn more, visit the Adopter page.