Why this proof note exists
Some enterprise work runs in customer-controlled environments where not every operating detail is public. This note states what the APAC aviation case supports and what does not.
What is public
The public-facing case study is designed to support the following claims:
- Pixel ML delivered Phase one and Phase 2 work for a major APAC aviation customer
- the work was deployed in a customer cloud environment
- the system moved past offline demo into a customer-hosted rollout
- the use case centered on video search, summarization, investigation support, and operator-facing workflows
What stays private
The public page does not disclose:
- customer identity
- sensitive KPI figures
- detailed operating volumes
- customer-specific architecture beyond generalized patterns
- infrastructure and implementation details that could narrow customer operating context
- internal evaluation details that are not approved for open publication
How to read operating scope
Public wording points to:
- delivered phases in the customer environment
- customer-hosted rollout
- customer cloud deployment
This is not yet a full scaled production rollout.
Why this still matters
Even with limited public detail, the case remains meaningful. It shows Pixel ML working in a trust-heavy enterprise setting where deployment control and operational usefulness are both required.
Related public page
◆ Main case study: /cases/apac-aviation-video-intelligence