AI-first · Perception · Automation

Machines that see, read, and then do the work.

An AI-first company building the whole stack: generative and agentic AI, computer vision and video understanding, and the document intelligence underneath. We turn unstructured reality into structured facts, then put agents on top that finish the task - on factory floors, in hospital corridors and open fields, not just in demos.

Live inference below On-prem · Edge · VPC Human-in-the-loop
citructure runtime · v4.2
Trigger
Defect rate on line-2 crossed 3× baseline inside twelve minutes.
Reason
The cluster is confined to one part family, so this is upstream, not the camera. Find what changed.
Tool call
mes.batch.lookup(line=2, window="09:10-09:34")
material lot changed 09:12 · lot A-7741 · 3 pallets in circulation
Tool call
vision.query(class="surface_scratch", window="09:10-09:34")
41 of 47 defects trace to lot A-7741 · confidence 0.96
Action · policy gate
Quarantine the lot, open a work order, hold the remaining pallets.
production hold requires approval · S. Rao (quality lead) · approved 09:36
Committed
Work order WO-2291 open · lot quarantined · supplier claim drafted.
Elapsed 94 seconds. Nobody was watching the monitor.
agent contract audited
agentquality.excursion.responder
toolsmes.batch · vision.query · wo.create · mail
may_writework_order, lot_hold, supplier_claim
needs_humanany production stopgate
may_notalter recipes, release quarantine
evidence47 frame crops + telemetry window
retention7 years · immutable log
fallbackpage the shift supervisor
Every step reversible · every claim cites a source
housing_a 0.98
seal_ring 0.94
⚑ surface_scratch 0.91
CAM-04 · LINE 2 · 1080p 60 fps · 13 ms
inspected 1,284 flagged 7
model ctv-det/8n-edge jetson orin nx
event stream streaming
ROI full frame · reject gate armed · sink MES / OPC-UA
Plant manager · 06:40
Why did line 2 miss target on Tuesday?
CItructure assistant
Line 2 lost 47 minutes against plan, in three blocks. The largest was an unplanned stop at 08:58 from an infeed jam 1 - the cycle-time drift that preceded it was already visible eleven minutes earlier 2. The second block was a changeover that ran 11m 40s against a 7-minute standard 3. The remaining nine minutes were a guard-door safety stop at 08:36 4. Material was not a factor here: the lot change you are thinking of is Wednesday, not Tuesday.
1 cam-11 clip · 08:58:41 2 cycle telemetry · 08:47 3 cam-11 clip · 08:27:45 4 PLC event log · 08:36:19
Asked what caused the jam itself: “I do not have evidence for that in the retrieved window.” It does not speculate, and it does not fill the gap with something plausible.
grounding trace 4 sources
scopeline-2 · Tue 08:00-16:00
searchedvideo events · MES · PLC log · shift notes
retrieved31 candidates → 4 cited
permissionsscoped to plant-ops roleok
dropped2 sources · outside date rangefilter
groundingevery claim maps to a sourcepass
unsupportedrefuse, do not infer
modelruns inside your boundary
Answers in clips and rows
What we build

Six capabilities. One idea underneath.

Everything we ship does the same thing in a different medium: take something unstructured, give it a schema, and hand it to something that can act. Pixels and paper are the same problem.

Agentic AI automation

Perception is step one. Our agents match, reconcile, chase exceptions, write the email and post to the ledger - inside a permission contract your risk team can read.

  • Tool use across ERP, MES, PACS, CRM and your own APIs
  • Scoped write permissions, not prompt instructions
  • Approval gates wherever the stakes justify one
  • Full trace: prompt, tool, result, actor, timestamp

Generative AI & assistants

Assistants grounded in your own operation - footage, telemetry, tickets, archives. They answer with the clip and the row they used, or they say they do not know.

  • Retrieval across video, sensor and text sources at once
  • Every claim cited back to its evidence
  • Permission-aware: it sees what the user may see
  • Refuses rather than fabricating a plausible answer

Computer vision & detection

Detection, recognition, segmentation, counting, measurement and tracking - trained on your parts, your produce, your equipment, your lighting.

  • Defect and anomaly detection
  • Multi-object tracking with stable IDs
  • OCR-in-the-wild: plates, serials, batch codes
  • Millisecond budgets on edge hardware

Video understanding

Frames are cheap; events are what matter. We turn continuous footage into a queryable timeline of actions, states and exceptions.

  • Action and process-step recognition
  • Cycle-time and dwell analytics
  • Natural-language search over archives
  • Clip-level evidence for every claim

Document AI

Extraction that survives real paper - and understands it. Smudged invoices, 400-page bundles, handwritten margin notes that contradict the line item.

  • Zero-template extraction, bound to your schema
  • OCR and handwriting for the pages others return blank
  • Classification, splitting and duplicate detection
  • Field-level confidence and page-region citations

Applied ML on your history

Once the pipeline has been producing structured data for a while, it becomes training data. Forecasting, scoring and anomaly models built on your own record.

  • Duplicate, fraud and spend anomalies
  • Yield, downtime and demand forecasting
  • Drift monitoring and scheduled retraining
  • Explanations, not just scores
The pipeline

Five stages. Most vendors stop at three.

Handing you a JSON file or a bounding box is not the deliverable. The last two stages are where work actually leaves someone's desk.

STAGE 01

Ingest

Email, SFTP, scanners, RTSP cameras, drones, PACS, an API, or a photo taken on a loading dock.

IN RTSP · PDF · JPG · DICOM · API · EML
STAGE 02

Perceive

OCR and vision models tuned for the bad cases - poor light, motion blur, skew, stamps, handwriting, occlusion.

OUT text · boxes · masks · tracks
STAGE 03

Structure

Layout- and scene-aware models bind every value to its label, its table, its frame - and to your schema.

OUT typed entities · relations · events
STAGE 04

Verify

Cross-checks against your systems of record. Anything below threshold routes to a reviewer with the evidence open.

OUT pass · flag · human queue
STAGE 05

Act

An agent posts the entry, opens the work order, halts the line, books the follow-up, closes the ticket.

OUT SAP · Oracle · MES · your API
Where it runs

The same stack, pointed at very different rooms.

A conveyor, a ward and a forty-hectare block have more in common than they look: continuous signal, scarce expert attention, and a decision that has to happen now.

Manufacturing

Inspection that never blinks, on hardware that already fits your line.

Surface defects, weld porosity, misassembly, missing fasteners, label and batch-code verification - caught at line speed on an edge box beside the conveyor, with the reject gate wired to the same signal. Video understanding adds the layer above: cycle times, operator ergonomics, changeover duration, and the ten seconds before every unplanned stop.

  • Defect detection and classification at 60 fps
  • Assembly-step verification and pick confirmation
  • Root-cause clips auto-attached to downtime events
  • Goods-receipt and invoice reconciliation from the same platform
99.4%Defect recall we engineer for
12 msEdge inference latency budget
4×Target changeover-audit speed-up
Healthcare

The paperwork and the pixels, both handled - inside your walls.

Referral letters, discharge summaries, insurance pre-auth packs and handwritten ward notes become structured clinical data. On the imaging side, detection and segmentation models act as a second reader that never gets tired, always flags rather than decides, and always shows the region it is talking about.

  • Clinical document abstraction and coding support
  • Region-of-interest detection with radiologist-in-the-loop review
  • Claims and pre-authorisation packet assembly
  • De-identification before anything leaves the premises
6 hrsClerical time we target to save, per bed-day
100%Processing inside your perimeter
0Autonomous clinical decisions
Agriculture

A crop scout with perfect memory and no travel time.

Drone, tractor-mounted and fixed-camera imagery turned into per-plant records: stand counts, canopy cover, disease and pest signatures, weed maps for spot spraying, ripeness grading at the pack house. Every observation carries a location, a date and an image crop, so the agronomist checks the evidence rather than the claim.

  • Plant counting, spacing and stand-establishment maps
  • Early disease and pest detection with severity grading
  • Weed maps that drive variable-rate spraying
  • Grading, sorting and traceability at the pack house
34%Target reduction in spray volume
41 haScoutable per flight, per-plant
9 daysTarget earlier-detection window
Finance & public services

Four hundred pages in, forty typed documents out.

Loan files, KYC packs, claims bundles, land records and legacy municipal archives - split, classified, named, extracted and cross-checked, with a reviewer queue for everything the model is not sure about. The archive stops being a warehouse and becomes something you can ask questions of.

  • Page-level classification, splitting and auto-naming
  • KYC, credit and claims file assembly with cross-checks
  • Grounded assistants that cite the page and clause
  • Duplicate and fraud signals from your own history
412 → 39Pages split into typed documents
91%Straight-through processing target
Every claimCited to a page and clause
0%Field-level accuracy target
0 msEdge inference latency budget
0 wksTo a working pilot on your data
24/7Unattended operation
How we behave

Your data does not leave your perimeter, and neither does the model.

We deploy inside your VPC, your datacentre or an edge box in the plant. Nothing is used to train a shared model. Every automated action is attributable, reversible and logged - and anything the system is unsure about becomes a human's queue item, not a silent guess.

  • On-prem, private cloud or air-gapped edge deployment
  • PII and PHI redaction before storage or inference
  • Role-scoped retrieval - the assistant sees what the user may see
  • Immutable audit log: input, model version, output, actor, timestamp
  • Confidence thresholds you set, per field and per class
deployment.yaml
# where the model lives is your call
deployment:
  mode: on_prem        # on_prem | vpc | edge | air_gapped
  egress: none
  gpu: 2 × L4          # or Jetson Orin at the line

privacy:
  redact: [pii, phi, account_no]
  retain_raw: false
  train_on_customer_data: never

humans:
  review_below: 0.92
  approve_writes_over: 100000
  queue: ops.exceptions

audit:
  log: immutable
  fields: [input_hash, model_ver,
           output, actor, ts]
  retention: 7y
Start here

Send us the ugliest data you have.

Ten scanned documents nobody wants to open, or an hour of footage from your worst-lit camera. We come back in two weeks with a working prototype on your own data and an honest read on what it will and will not do.

Two-week proof of concept · Your data, your infrastructure · No lock-in