Workflow illustration · Not a detection result

iPad Pro · Industrial AR visual inspection

Overlay the design on the real part.
See every deviation at a glance

Check for missing parts, wrong assemblies and missing bolts.
In-house tracking · Offline inspection · Private deployment.

Integration prototype. Accuracy and stability require on-site acceptance on your parts.

  • Markerless tracking
  • LiDAR depth fusion
  • In-house engine
  • Pluggable tracking interface
  • Evidence-gated lock
  • Separate reference and inspection sets
  • 7 checkpoint types
  • 5 overlay modes
  • Dimension screening ± tolerance
  • Photo mark-up
  • Voice notes
  • Works offline
  • On-premises
  • PDF · CSV · XLSX · JSON
  • MES / QMS webhooks
  • Open schemas
  • One-tap diagnostics
  • Frame-by-frame replay
  • Simulation regression tools

Live demo

A real iPad screen recording — not a render

Engine A on a real device: searching for the part, fitting the blue CAD outline over it and snapping into a lock. This is an early-prototype recording; footage of typical production parts will follow.

iPad Pro screen recording · real time

  • Engine A · edges + LiDAR
  • Search → align → auto-snap
  • Early prototype · production-part footage coming

3-in-1 suite

Plan, inspect, review — one dataset end to end

Author the inspection plan in Studio, run it on the iPad, review and archive in the browser. Same project package, same schema.

Authoring · macOS / Windows / Linux / Web

CADAR Studio

Import STEP, auto-decimate and generate the tracking model; pick reference parts, click the model to add checkpoints, attach documents; publish a versioned project package.

Shop floor · iPad Pro · LiDAR

CADAR App

Auto-snap alignment, step-by-step guidance, one-tap OK / NOK, photo mark-up, voice notes and dimension screening; PDF on session end, fully offline, syncs when online.

Review · Browser · On-premises server

Web review & archive

Locate checkpoints in the fixed-version model, compare criteria, photos and original / reviewed results, generate standard reports and track reinspections. Customer templates and MES receipt rules require implementation testing.

In-housePluggable interface · Backends validated per use case
iPad ProLiDAR · M-series chip
3-in-1Studio · App · Web review
STEPIGES · STEP / STP / IGS
7 / 57 checkpoint types · 5 overlay modes
4Report formats PDF · CSV · XLSX · JSON
100%Offline inspection · auto-sync

The workflow in 60 seconds

Align · Lock · Judge · Report

A Aligning 41%
A Tracking 93%
Aim at the part and fit the blue model over it
Locked · overlay follows the part
Stiffener R2 · not installed · photo marked up
PDFInspection report · MCH-PS-2026-0910
Checkpoints24
OK / NOK / Review21 / 2 / 1
Annotated photos6
Synced to plant server · CSV / XLSX / JSON generated
  1. 01

    Align

    Fit the blue outline over the part. Markerless, guided by a preset start pose; it snaps when the match is good enough.

  2. 02

    Lock

    Alignment quality is checked against edge and depth evidence. Insufficient evidence produces a degraded-quality prompt for operator review.

  3. 03

    Judge

    Review the expected parts step by step. The inspector confirms OK / NOK, with annotated photos, notes and dimensional screening as evidence.

  4. 04

    Report

    End the session and the iPad generates the PDF. Fully offline; syncs to the plant server when a connection is available.

Check suitability, then validate the complete inspection workflow

This is an integration prototype. Available software, capabilities requiring site validation and planned work are distinguished below. A pilot is assessed against agreed parts, versions and acceptance records.

Capabilities and validation status

CapabilityCurrent statusConfirm during the pilot
Studio authoring, version publishing and browser reviewAvailable · integration prototypeAcceptance criteria, access scope, fixed-version reports and reinspection workflow
iPad alignment, tracking and offline retryValidate on actual partsDevice and app version, lighting, distance, occlusion, repeated geometry and reconnect behavior
AR dimensional screeningAssistance · human confirmation requiredCompare against calibrated instruments; not a substitute for metrology
MES webhooks and private deploymentInterfaces available · integration requiredNetwork, authentication, event idempotency keys, receipts and correction events
ARKit reference objects / GPU stationsUse-case validation requiredReference training, GPU configuration and station network
Third-party engine bridge, two-way MES ordersReserved / plannedOutside the current standard delivery; agree scope separately

Initialization, drift and frame-rate figures on this site are pilot targets or illustrations, not fleet acceptance results. Measurements must record part, device, distance, lighting, occlusion, software version, sample size and failures.

Is your part a good fit?

Good pilot candidates

Static rigid parts, complete CAD matching the actual revision, stable distinguishable reference geometry, and visible missing, misassembled or incorrectly counted attachments.

Test a small sample first

Specular, transparent, low-texture or repetitive surfaces, severe occlusion and look-alike parts need evaluation. Record dimensions, working distance and target defect size on site; do not assume a universal accuracy.

Not an acceptance method for

Moving or deformable parts, hidden internal defects, safety interlocks, unattended release, regulated metrology or non-destructive testing. Evaluate suitable alternatives for these requirements.

Review the result and its evidence together

The existing device video demonstrates prototype alignment and locking only. The four scenarios below use synthetic data to explain the workflow. They are not customer cases, field benchmarks or acceptance endorsements.

  1. Correct assembly: inspect against a fixed plan, record results and upload required photos. Generate a reviewed report after supervisor confirmation.
  2. Missing part: record expected and actual counts, mark NOK and identify the correction needed.
  3. Incorrect assembly: record the orientation difference against the drawing and model. Confirmation retains NOK; it does not release the item.
  4. Insufficient evidence: retain an incomplete result, add photos or create a new reinspection session. Claim, submission and closure remain traceable.
Expand technical implementation and validation notes

More than drawing CAD over a camera feed

From alignment quality to traceable inspection records

AIn-house · edges + LiDAR
BARKit reference object
CGPU workstation
DThird-party bridge · reserved
TrackingEngine C ABI · one interface · world frame world_from_model

In-house, pluggable tracking engine

In-house tracking is the main path. ARKit reference objects and GPU stations require use-case validation; the third-party bridge is reserved, not integrated.

Edge inliers
Depth consistency
TRACKING

Evidence-gated lock

Combines edge and depth evidence and reports degraded quality when evidence is insufficient. Validate false-lock risk on repetitive structures and similar parts.

Separate reference and inspected parts

Reference parts determine alignment while inspection parts are checked separately, reducing interference from missing parts.

Engine target · 10–30 Hz
Render target · 60 Hz

Recheck alignment when returning

Pose is maintained in the ARKit world frame. Recheck the overlay after losing sight or quality; occlusion and relocalization still need site testing.

Dimension screening

Point-to-point distance or deviation from the CAD face, judged against nominal ± tolerance.

Pending upload3
Inspecting offline…

Works without network

Inspect, photograph and report fully offline; syncs automatically when online.

Field issue
One-tap bundle
Frame replay
Simulation regression
Fix shipped

Closed-loop diagnostics

Tracking loss, failed initialization and thermal events can trigger diagnostics. Replay and simulation tools help reproduce issues; regression frequency and coverage depend on actual test records.

{
  "partId": "fnv1a:8f3c…",
  "result": "NOK",
  "defect": "missing",
  "world_from_model": [16]
}

Open data contracts

JSON Schema and FlatBuffers shared by all three apps; your data leaves with you if you switch vendors.

Review deployment and data flow

Projects and reports support private deployment with role permissions and audit logs. R&D diagnostic bundles use Alibaba Cloud OSS; confirm data scope and access before enabling diagnostics.

Translucent
Wireframe
Split
Section
Magnifier

7 checkpoint types × 5 overlay modes

Presence · Position · Visual / weld · Count · Dimension · Photo · Document.

On-site comparison

Use the same parts and acceptance conditions

← swipe →

Check
CADAR
How to verify
Tracking quality
Reports degraded evidence
Use similar parts and repetitive structures to test false locks.
Missing-part interference
Separate reference and inspection parts
Remove an inspected attachment and compare alignment.
Dimensional screening
Records nominal values and tolerances
Compare with gauges; screening does not replace metrology.
Inspection workflow
Author, inspect and review
Import one part number and complete a report with photos.
Offline and sync
Inspect offline, sync when connected
Disconnect, inspect, reconnect and verify report completeness.
Deployment and data
Private projects/reports, OSS diagnostics
Verify diagnostic settings, storage locations and access.

This prototype has not completed a head-to-head acceptance test with Twyn / SuPAR. Compare the same parts, viewpoints and reference measurements rather than marketing figures.

What goes in the contract

We don’t sell magic

01

Overlays and LiDAR values are for screening and guidance; the pass / fail verdict is the inspector’s.

02

When the fit degrades we show it — no forcing the overlay to look good.

03

Every number is labelled target or measured; side-by-side comparisons on your floor are welcome.

< 10 sinitialisation · target
< 5 mmdrift on walk-around @ 2 m · target
0.8–2.5 mrecommended working distance
16on-site acceptance items
4month pilot plan · indicative
Show the 16 acceptance items
  1. CAD import & model processing
  2. Inspection plan authoring: 7 checkpoint types, attachments, versioned publish
  3. Package distribution & session creation
  4. Localisation & lock
  5. AR overlay, 5 modes + per-step display
  6. Step-by-step inspection & minimap
  7. Result capture & photo mark-up
  8. Dimension entry & out-of-tolerance flag
  9. Missing-part prompt
  10. Session pause / resume
  11. Offline inspection & sync
  12. Report generation & export
  13. Server archive & browser review
  14. Users & roles (4 roles)
  15. One-tap issue report
  16. Training & documentation

Deployment

One iPad · one PC · one on-premises server

CADAR Studio

macOS · Windows · Linux

Import STEP → author checkpoints → publish

Plant server

On-premises · browser review

Archive · roles · MES/QMS webhooks

CADAR App

iPad Pro · LiDAR

Offline inspection · auto-sync
  1. M1Month 1 · deploy + first part number
  2. M2Months 2–3 · pilot on 3 part numbers
  3. M3Month 4 · acceptance · training · maintenance handover

FAQ

Questions you might have

Do I need markers on the part?

No. Stand at the preset start pose, fit the blue outline over the part and it snaps; manual placement and ARKit reference-object recognition are also available.

How accurate is it? Can it replace a CMM?

No, and it shouldn’t. It performs visual conformity checks and screening: missing, wrong, mis-oriented or clearly misplaced parts. Metrology verdicts stay with gauges and inspectors; engineering targets are listed under “What goes in the contract”.

How long to onboard a new part number? Any training?

STEP → import in Studio (tracking model generated automatically) → pick reference parts, author checkpoints → publish. The default engine needs no training and there is no per-model licence.

Which CAD formats?

Current import supports STEP / STP and IGES / IGS. Convert other formats first; native JT / CATIA import is not available.

Where do I open Studio?

The web version opens from “Open Studio” in the top-right corner, hosted on your plant server; the desktop app (macOS / Windows / Linux) is distributed by the implementation team.

Biggest differences from Twyn and SuPAR?

An in-house, pluggable engine with no per-model licence; diagnostics and replay as first-class citizens; open data formats and transparent acceptance criteria.

Pilot deliverables and site preparation

Pilot deliverables

  • Project package, inspection plan and acceptance instructions for agreed parts and versions
  • Browser Studio, a package for the target iPad and a deployment configuration record
  • Operator training, sample inspection records, original and reviewed reports
  • Reinspection records, issue list, site acceptance and agreed follow-up scope

Equipment and network

  • LiDAR-equipped iPad Pro; agree the exact model and iPadOS during the pilot
  • A supported browser, CAD and authorized correct / missing / misassembled samples
  • Server domain, HTTPS, access permissions, storage backups and permitted outbound network
  • Inspect locally offline; downloads and evidence sync need connectivity. Enabled diagnostics use Alibaba Cloud OSS only

Installation, support and quotation

  • Request a package for your devices by email below; there is no public App Store download currently
  • Provide part, station and device counts, CAD formats, report templates, MES interfaces and deployment model
  • Agree deployment, training, maintenance, support hours, upgrades and customization in the pilot proposal
  • Confirm software, CAD preparation, implementation, integration and ongoing support separately; no unconfirmed prices are implied
Open the pilot input checklist

Book a demo

Bring your STEP file and a real part —
watch the CAD snap onto it

About 60 minutes: import the model, author 3 checkpoints, align and lock on the iPad, run an inspection, generate a report with photos. Feel free to put Twyn / SuPAR on the same station.

To request a demo, create a draft or copy your requirements and send them to demo@cadarai.com. Without a mail app, paste the recipient and text into webmail. This page does not send automatically or issue a ticket number. A reply from the implementation team confirms receipt; response times and alternative contacts will be agreed in that conversation.

This page does not collect form data. Your information is passed only to your mail app or clipboard. Recipient: —