Native CDF export
Every Hullproof passport emits CDF Asset + Events JSON via /api/passports/{id}/cdf. External-id-keyed for dedup; metadata flattened to CDF's 10240-char string limit. Labels follow the hullproof:asset-type:<type> convention.
Partner · For Cognite
The visual condition data product CDF customers are asking for.
Aker BP, Equinor, Var Energi, and most other Cognite Atlas AI customers all face the same gap: structured tilstand-data for visually-inspected physical assets (jackets, subsea, monopiles, FPSO hulls) doesn't exist in their CDF instance today. Hullproof emits CDF-ready Asset + Events JSON for every inspection. One integration; thirteen verticals.
Multi-vertical from one schema
Hullproof covers 13 asset types — vessel hulls, jackets, monopiles, blades, bridges, pipelines, tanks, subsea, harbor, pylons, naval. Same CoatingPassport JSON across all of them. One CDF integration unlocks the full surface.
EU AI Act + audit-ready by design
Every finding carries confidence, frame count, image quality, AI model version, source frames. Every passport tags its EU AI Act class. Review workflows in append-only history. Compliant with the regulatory expectations Cognite customers face.
Footage-agnostic
ROV, drone, handheld, fixed monitoring, satellite, crawler. No hardware lock-in. Compatible with whatever inspection contractors a Cognite customer already uses.
Partnership topics we'd like to discuss
- • Hullproof CoatingPassport listing in Cognite Marketplace
- • Reference architecture in Cognite's data-product docs
- • Co-marketing with Atlas AI joint customers (Aker BP, Equinor, Var Energi)
- • Optional: Hullproof as a Cognite-native function or stored procedure
- • Joint POC with one shared customer across two asset classes