Skip to content
fabrickLens
Introducing

The vision system
that doesn’t blink.

Custom-installed computer vision for quick-service restaurants. Purpose-built cameras, on-site edge compute, and real-time intervention at the stations you choose. Machine oversight that is more accurate, more consistent, and never looks away.

Watch how it works
< 300ms
Inference latency
Modular
One station or all
0
Frames analyzed today
0
Stations watching
Live kitchen feed — Fryer Station 03
Fryer Station 0330 FPS · 4K
TENDER
0.96
FRYER STATION
0.92
LiveFRAME 1024
Fryer Station 03 · 30 FPS · 4KInference 38ms · Edge appliance
STORE 4127 · 4 OF 16 STREAMS · CYCLINGLIVE INFERENCE
The full system below
The visibility gap

Humans can’t be every station, every order, every second.

A quick-service restaurant runs eight to twelve stations across cook, prep, assembly, and pass. A typical shift produces hundreds of orders. Every order carries fifteen to thirty discrete quality and accuracy checkpoints. The math does not work for human oversight.

01

Attention fatigues

Human attention degrades within minutes. Drift gets worse, not better, as the shift wears on.

02

Coverage is partial

Even the best line lead watches one station at a time. The other stations run unobserved.

03

Events are fast

An assembly sequence takes seconds. A missing item is a fraction of that. Eye-blink fast.

04

Audits are backward

Camera review happens after a complaint. By then the cost has already compounded.

The compounding cost

Every miss has a compounding cost.

These are the moments that drive refunds, NPS damage, complaints, and brand erosion. None are visible in real time today. All can be detected and resolved in real time by Fabrick Lens.

01
Burger count missed
A double leaves the line as a single. The operator never sees it.
RefundBrand trustSocial complaint
02
Wrong sauce portioned
The order spec says one sauce, a different one gets boxed.
Customer returnOrder remakeTicket time
03
Modifier ignored
Cheese on a no-cheese order. Allergen risk on the wrong customer.
Allergen riskRefundHealth complaint
04
Fry cook drift
Fryer recovers slow on a rush. Pale fries reach the bag.
NPS dropRepeat-rate declineReview damage
The product

A vision system that intervenes.

Fabrick Lens is a modular, custom-installed computer vision platform for quick-service restaurants. Industrial cameras at the stations you choose to instrument, an on-site edge appliance, and signal fusion with the equipment already on your line. Start with one station, scale at your pace.

< 300ms
Inference latency
Detection to alert, on-site
Modular
Deployment
One station or all. Your call.
24 / 7
Continuous watch
No fatigue, no blind spots
Real-time
Intervention
Drift caught before handoff
A modular QSR kitchen with cameras at chosen stations
Modular by design

Pick the stations that matter most. Add cameras one at a time or instrument the whole line. The system is built to start small and scale at your pace.

01
Capture

Cameras at your priority stations

02
Detect

Task-specific models analyze every frame

03
Decide

Rules and fusion logic evaluate the scene

04
Act

Operator alerted at the station, in real time

The intervention loop

Detection is the start. Intervention is the point.

Real-time computer vision is only as valuable as the action it triggers. Fabrick Lens closes the loop. Every detected drift becomes an alert, an intervention, and an audit entry.

TAP REPLAY
0114:32:08
Detect
Drift identified
0214:32:08
Decide
Rules evaluated
0314:32:09
Alert
Operator notified
0414:32:14
Verify
Corrected in frame
0514:32:14
Audit
Logged for BI
Example · Missing sauce intervention
14:32:08
Order #4271 boxed. Vision detects entrée and fries but no sauce cup. KDS order calls for one sauce.
14:32:09
Alert fires to assembly screen. Audio chime at pass.
14:32:14
Sauce added. Re-verified. Order released. Event logged.
How it works

Five techniques. One vision system.

A real CV product is not one model. It is a stack: detection finds what is there, classification judges if it is right, action recognition reads the sequence, tracking holds identity through occlusion, and fusion correlates all of it with equipment and order data.

01Object Detection

Anatomy of a detection.

Every detection produces four things: a class label, a confidence score, a bounding box, and a tracked centroid. Together they answer what, how sure, where, and where next.

A breaded chicken tender on a stainless prep surface
TENDER
0.00
CENTROID 412, 288
Bounding box
Four coordinates. The tightest rectangle that contains the object.
Class label
What the model identified. One of the trained menu classes.
Confidence
How certain the model is. Below a set threshold, the detection is suppressed.
Centroid + scale
Position and size. Feeds tracking, counting, and placement checks.
02Classification

Detection finds it. Classification judges it.

Once an item is located, a fine-grained classification model answers the harder question: is it right? This is where pixel-level quality assessment happens, and where a bounding box alone is not enough.

Detection
QSR assembly station
GREENS
GRAINS
HUMMUS
PEPPERS
CHICKPEAS
Finds and locates. Something is there.
Classification
QSR assembly station
GREENS
GRAINS
HUMMUS
PEPPERS
CHICKPEAS
GREENS
FRESH 0.94
GRAINS
FILL 0.91
HUMMUS
COLOR PASS
PEPPERS
FRESH 0.95
CHICKPEAS
FILL 0.62 · LOW
Judges every item. Catches the one that fails.
Why it mattersA box says something is there. Classification says exactly what, and exactly whether it is right.
03Action Recognition

Some quality questions only exist over time.

A single frame cannot tell you whether a build sequence was followed or a hygiene step was skipped. Action recognition reads a sequence of frames, building confidence as the motion completes.

Burger assembly frame 1
FRAME 01
0.12
Burger assembly frame 2
FRAME 02
0.38
Burger assembly frame 3
FRAME 03
0.62
Burger assembly frame 4
FRAME 04
0.85
Burger assembly frame 5
FRAME 05
0.97
Action confidence · Cheeseburger assembled0.12
0.12 START0.97 ASSEMBLED

A single frame cannot confirm a process step. Action recognition reads the sequence, and confirms the step actually happened.

04Tracking + Re-ID

One order, followed end to end.

Tracking holds a persistent identity on an order as it moves across stations and through occlusion. This is what makes true ticket-time decomposition possible. Not just how long, but where the time was spent.

FRAME 1024  ·  COOK
FRAME 1024 · COOK
ID_0472
FRAME 1025  ·  COOK → ASSY
FRAME 1025 · COOK → ASSY
ID_0472 · OCCLUDED
PREDICTED
FRAME 1026  ·  ASSEMBLY
FRAME 1026 · ASSEMBLY
ID_0472 · RE-ACQ
REACQUIRED
FRAME 1027  ·  PASS
FRAME 1027 · PASS
ID_0472

Persistent identity. One order held across stations and through occlusion. ByteTrack and DeepSORT re-ID.

05Signal Fusion

Vision plus sensors plus KDS. The layer no one else has.

Three input streams correlated frame by frame inside a single fusion core. Catches what one signal alone misses, separates equipment fault from human error, and confirms rather than just detects.

VISION

Detection, classification, action, tracking

EQUIPMENT TELEMETRY

Fryer temp, cook timers, holding-cabinet state, weight sensors

KDS + POS

Order content, modifiers, timestamps, bump events

Signal fusion
CORE
Frame-synced correlation across all three signal layers.
Correlated decision
  • Catches what one signal alone misses
  • Separates equipment fault from human error
  • Confirms, not just detects
Fusion in one line

The fryer reports done-at-temp. Vision reports the product is under-colored. Neither signal alone catches it. Together they say the equipment is drifting, not the cook.

Custom models

Data to deployment, then it never stops.

Every custom model moves through the same six-stage lifecycle. The first pass produces a working model. The loop keeps it accurate as your menu, lighting, and seasons change.

01
Capture
Collect footage from your stations under real operating conditions
02
Annotate
Label items, regions, and actions against your spec
03
Train
Fine-tune the task-specific model on the labeled dataset
04
Evaluate
Test against held-out footage, tune precision and recall
05
Deploy
Push to the edge appliance, run live on station streams
06
Monitor
Track drift, surface edge cases, feed them back to capture
Continuous feedback loop · Edge cases from monitor flow back into capture
Production lineage

This team has shipped production CV before.

Fabrick Lens is not a first attempt. The custom-model approach, the edge architecture, and the QSR domain work all trace to production deployments the team has built and run.

BigBasket Fresho

Fresh-produce vision at scale

Custom vision models for produce quality and self-checkout. 800+ SKUs in production, retrained per category.

800+SKUs live
< 300msinference
Wonder · QSR

QSR video analytics platform

Quality and consistency analytics purpose-built for a multi-unit QSR operator. Vision plus operational signal.

Multi-unitdeployment
QSRdomain
Pattern AI · EdgeVision

Edge-deployed production CV

Edge-first computer vision with on-site inference and real-time event generation. The architectural lineage for Lens.

Edge-firstarchitecture
Real-timeevents
What you can measure

Six categories. Every one tied to the P&L.

Built from the way a multi-unit operator actually thinks. Each category ties to a revenue line or a brand-risk line, and each is measured continuously through the fusion of video and equipment data.

Fabrick Lens dashboard on a kitchen tablet
01

Order Accuracy

Perfect-order rate, item-level error rate, count accuracy, modifier compliance, condiment attach rate, packaging accuracy.

02

Food Quality & Consistency

Cook doneness conformance, cook-time conformance, temperature at handoff, hold-time compliance, portion and build consistency.

03

Speed & Throughput

Ticket time decomposed by station, station dwell, cook recovery time, drive-thru time, throughput per labor hour, predicted SLA breach.

04

Food Safety & Compliance

Temperature danger-zone events, hold-time violations, handwash compliance, cross-contamination risk, vision-verified HACCP checkpoints.

05

Equipment Health & Calibration

Calibration drift, oil quality and fryer health, recovery-time degradation, holding-cabinet conformance, sensor-fault detection.

06

Labor & Waste Efficiency

Staffing vs demand, throughput per labor hour, SOP adherence, overproduction waste, portioning cost variance, remake and refire rate.

The fusion advantage

The KPIs that only exist with fusion.

These five do not exist in a camera-only system or an equipment-only system. They require video and equipment data cross-referenced, frame by frame. They are the reason signal fusion is the moat.

01

Calibration drift

Fryer reports done-at-temp. Vision reports under-colored. The equipment is the problem, not the cook.

02

True ticket-time decomposition

Not 'the order took six minutes' but 'it lost ninety seconds at assembly.' Tracking plus KDS timestamps.

03

Sensor-fault detection

Holding cabinet reports a full pan. Vision sees it empty. The sensor needs service, flagged automatically.

04

Root-cause quality

Oil TPM rising, product color darkening in step. The fries are worse because the oil is spent.

05

Predictive SLA breach

Queue depth and per-station throughput forecast a ticket-time miss sixty to ninety seconds before it happens.

The moatCompetitors with cameras can copy detection. They cannot copy what they have not instrumented: the equipment signal layer underneath.
Product architecture

Cameras, compute, sensors, AWS-native cloud.

Three zones. A custom install in the restaurant, one edge appliance running vision and fusion locally, and AWS-native managed services for training, fleet management, and reporting. Designed for AWS QSR customers, end to end.

On-premise·Restaurant

Custom installation per store

FryerIndustrial camera + temp probe
PrepTop-down vision camera
Cook lineProfile + top vision
AssemblyTop-down + weight sensor
HoldingTop vision + timer signal
Pass / handoffProfile camera + KDS feed
Edge appliance·Lens

One per restaurant

Stream ingest
Detection models
Tracking + Re-ID
Sensor fusion
Rules engine
Event generator
AWS cloud·Orchestration

Managed services

Model trainingSageMaker
Foundation modelsBedrock
Fleet managementIoT Core + SSM
Event busKinesis + EventBridge
StorageS3 + Timestream
APIs + dashboardsAppSync + CloudFront
Built on AWS · Zero cloud round-trip in the detection path · Fleet-at-scale ready
Edge appliance in a QSR back-of-house
Engagement

Pilot to production. Then chain rollout.

Custom install means a structured roadmap. Each phase has clear outputs and acceptance criteria. Pricing tiered by chain size to support pilot economics and scale economics.

Phase 00Week 0 to 1

Discovery

Camera audit, station prioritization, AWS architecture review, pilot store selection.

Phase 01Week 2 to 6

Install + pilot

Custom camera install, edge appliance, first signature model, UAT on pilot station.

Phase 02Week 7 to 14

Hardening

Additional models, sensor fusion, dashboard tuning, multi-store readiness.

Phase 03Week 15+

Chain rollout

Zero-touch provisioning, per-store onboarding, continuous model expansion.

The takeaway

See every station.
Catch every drift.
Intervene in real time.

Production-grade computer vision for QSR operations. Custom models, custom installed, AWS-native. Methodology you can audit, KPIs you can run the business on.