Detect and track, search your whole library in plain language, ask an agent across every clip, extract structured data, and generate reports — the intelligence was always in the video. We read it out.
We are not taking new accounts at the moment. Everything below is what the product does, and it still does it — existing accounts work as normal and you can sign in as usual. If you would use this, tell us what for; that is what decides whether it opens again.
Semantic search reads what's happening across every clip you've indexed — then an agent answers questions and cites the exact timecoded frames, wherever they live.
forklift within 2m of a person, no hi-vis vest
warehouse_B · aisle 4
forklift + person · 1.4m gap
00:02:41
dock_cam_03
no hi-vis · confidence 0.91
00:11:07
warehouse_B · aisle 1
forklift + person · 1.9m gap
00:18:52
Did any vehicle block the fire lane yesterday, and for how long?
Ask a question and land on the answer. Read a hundred clips in one pass. Then set the whole thing to run on its own.
Muted · captions on
Video chat
Ask in plain English, jump to the moment that answers it
The answer arrives with the timecodes it came from, and every one of them is a click away.
Muted · captions on
Batch
Clear a hundred clips in the time it takes to watch one
Send the whole upload at once and read the findings side by side when it lands.
Muted · captions on
Schedules
Set it once and the answers keep arriving
A workflow that runs to its own schedule, with every past run kept on the record.
04 / THE SURFACE
One engine. Every read.
Detection, retrieval, reasoning, and reporting run off the same understanding of your footage — so the breadth compounds instead of fragmenting into tools.
DETECT · TRACK
Frame-by-frame analysis
Objects, actions, and events detected and tracked with persistent IDs and timecodes.
Upload, connect Drive, or point at a link. Batch as many clips as you like.
02
Detect & track
Every minute analyzed — objects, actions, events, with timecodes.
03
Index
Embeddings make the whole library searchable in natural language.
04
Ask
Query or converse with the agent; it reasons across clips and cites frames.
05
Report
Synthesize findings into a structured, exportable document.
06 / THE PAYOFF
From a thousand minutes to one document.
When the read is done, synthesize it — an executive summary, findings anchored to timecodes, and the numbers, in a document your team will actually read.
Findings tied to timecodes Every claim points back to the exact second in the source.
Numbers, not vibes Counts, dwell times, and deltas extracted straight from the footage.
Branded & exportable A clean PDF that reads like it came from your team, not a tool.
Q3 Site Read — North Gate
synthesized from 14 clips · 3h 41m
READ #0428 2026-07-28 ● COMPLETE
02:14Loose guardrail, north stairwell — recurs across 4 sitesSAFETY
08:47Two fire-extinguisher tags expiredCOMPLIANCE
21:03Loading-zone dwell up 12% vs Q2OPS
07 / REPEATABLE
Configure intelligence once. Run it forever.
A template is the set of questions you always ask, saved. Point it at next week’s footage and the same read comes back in the same shape — which is what makes two batches comparable.
01
Save the questions
Get one read right — the prompts, the depth, what the report should contain — and keep it instead of rebuilding it next time.
02
Point it at the next batch
New clips, same template. Run it across a whole upload at once rather than clip by clip.
03
Get the same document back
Same structure, same fields, same numbers in the same places — so this month can be laid next to last month and actually read.
Reads teams set up first
TRAFFICTraffic study
How many, how fast, and what went against the signal.
SAFETYWarehouse safety
People near moving equipment, missing PPE, blocked routes.
FLOWRetail flow
Where people go, where they stop, and for how long.
AUDITSecurity audit
Access events, restricted areas, anything out of hours.
08 / LIVE Coming soon
Point it at a camera, not a file.
We are building live monitoring now: connect a feed, write what you want watched in plain language, and get told when it happens. It is not something you can switch on yet — this is what it is being built to do, and an invitation to tell us what you would connect.
01
Connect the feed
Whatever your site already streams — an IP camera, an NVR channel, a restream. We are building against the formats cameras emit rather than asking you to put a new box on the wall.
02
Say what matters
The same plain language you already search a library with — a sentence or two, the way you would brief someone on their first shift.
> tell me if anyone goes into the loading bay without a hi-vis vest between 18:00 and 06:00
03
Hear about it
Nothing arrives while nothing happens. When something does, the alert says what it saw and when it saw it.
The kind of thing it is being built to watch for
RETAILLoss prevention
Someone leaving through the fire exit with a full cart. A till drawer standing open with nobody at it.
SITESafety & PPE
A person on foot inside the forklift lane. A hard hat missing past the gate line. Working at height with nothing clipped on.
PROPERTYProperty & wildlife
A vehicle on the access road after dark. Something at the feed line that is not livestock. A gate still open after the last shift.
QAManufacturing
A carton going down the line with its flap open. A jam building on the infeed. A station standing empty longer than a cycle.
TRAFFICTraffic & parking
A vehicle stopped in a live lane. The fire lane blocked past five minutes. A loading bay held long after its limit.
None of this is switched on yet. The page says what exists, what does not, and what we cannot promise about footage.
09 / QUANTIFIED
The read, as data.
Everything detected becomes a number you can track — throughput, dwell, exceptions — trended over time.
Throughput / hr
0
▲ 6.2% vs last wk
Avg dwell
0s
▲ 12% vs last wk
Exceptions
0
▼ 18% vs last wk
Coverage
0%
▲ 0.3% vs last wk
DEVELOPERS Beta
Your library, from your own code.
The reads you get in the app, available over HTTP: list a library, run an analysis, poll the batch, search in plain language. Scoped keys, one shared credit balance, and an OpenAPI 3.1 spec.
A per-seat platform fee with a generous pooled credit bundle that refreshes every month — credits are spent by the minute of video, at the depth you pick: 1 credit a minute for a fast read, 5 a minute at standard depth. Heavy reads pay for the compute they use; everyone else stays flat.
None of this is currently for sale. We have stopped opening new accounts, so there is nothing to buy on this page — the prices are here because what you would have paid is the most useful thing you can tell us. Existing subscriptions are unaffected and nothing new is being charged.
Billed annually · monthly available · top-up packs from $0.02/credit · usage capped, never surprise-billed
We do not currently offer SSO/SAML, a HIPAA BAA, SOC 2, or data-residency guarantees. Ask us what we can commit to in writing.
LIVE MONITORING Coming soon
Cameras are not priced yet — on purpose.
Uploaded video is priced on seats because it ends. A camera does not: it runs until somebody stops it, so it will be charged separately from seats and it is not included in any plan. What it should cost depends almost entirely on how fast you need to know — checking a place every ten minutes and catching something that takes two seconds are very different jobs, and they are nowhere near the same cost. We would rather ask you than guess, so there is no number here until we have.
Five questions about your cameras. Nothing to buy, nothing to switch on, and no obligation — what you tell us is what decides how this gets priced and what gets built first.
> awaiting_signal_
Your footage already knows.
All of that is built and it runs. What we do not know is whether enough people want it to keep carrying it, so we have stopped opening new accounts until we do. Tell us what you would point it at — one minute, three questions, and it is the only thing that decides this.