Pricing
Priced per camera. Paid back in rejects.
From $200 per camera per month, or per line with batch investigation and QMS integration. No recipe engineer, no capital approval cycle.
Per camera
Up to $800 depending on resolution, frame rate and station count.
- Few-shot teaching, unlimited products
- Zero-shot deviation detection and maps
- Inspection records with audit trail
- Reject signal to the machine over OPC-UA
- Edge appliance included during pilot
Per line
Most pilotsAll stations on a line, batch investigation and system integration.
- Everything in Per camera
- Batch and component-lot correlation
- Draft deviations to QMS, results to MES and LIMS
- Validation package per model version
- Named validation engineer during pilot
Site & enterprise
Air-gapped deployment, CSV support and SLAs.
- Everything in Per line
- Air-gapped and segregated networks
- Computer system validation support
- Cross-site deviation intelligence
- Uptime and response SLAs
Pilot pricing and volume discounts available. Camera pricing scales with resolution and throughput; we'll quote after a 30-minute line review.
Pilot
How a pilot runs.
We don't ask you to model a five-year ROI. We ask for one station, one product and a few weeks in shadow mode.
- Week 0Line reviewA 30-minute call to choose the product, the station and the deviation that costs you most in rejects or investigations.
- Week 1Teach and run in parallelThe edge appliance is installed on the existing station cameras and a few dozen conforming units are captured. Phamqyra inspects in shadow mode the same week.
- Weeks 2–4Compare and qualifyResults are compared unit by unit with your current inspection and defect kits. You see the escapes it catches and the false rejects it avoids.
- Week 4+Release and extendWith qualification evidence in hand, QA decides whether to release the model to production and which station comes next.
03 / Comparison
Manual inspection tires. Rule-based AVI ossifies.
Phamqyra learns each product's normal and keeps learning under change control.
| Criterion | Manual visual inspection | Rule-based AVI | Phamqyra |
|---|---|---|---|
| Set-up for a new product | Qualify inspectors with defect kits | A recipe engineer per presentation | A few dozen conforming units |
| Deviation types nobody defined | Sometimes — attention dependent | Only what the recipe encodes | Zero-shot deviation detection |
| Consistency across a shift | Fatigue limits booth sessions | Consistent, until the product changes | Same model, every unit, every shift |
| False rejects of good product | Conservative by necessity | Tight thresholds reject variation | Learns conforming variation |
| Root cause for investigations | Inspector notes, after the fact | Pass/reject counts only | Correlated to batch and component lot |
| Records for batch release | Paper forms and signatures | Machine logs, limited context | Signed e-records with frame hashes |
07 / Questions
What QA asks first.
Validation, data integrity and how it fits the line you already run.
Yes — if the model is treated like any other configured system. Each Phamqyra model is locked at release, versioned with the units it learned from, and shipped with protocol templates (IQ/OQ/PQ), a risk assessment and a traceability matrix. A released model does not change in production; improvements arrive as new versions through your change control.
Start a pilot
One station, one product, a few dozen good units.
Pilots run alongside your current inspection, so you see what Phamqyra catches — and what it stops rejecting — before anything changes in your batch record.