Building blocks, put together for your business.
Tarsyer isn’t one fixed product. We pick the pieces each business needs and fit them to how it works, on the cameras it already has.
That is how a steel plant’s crane-hook check and a QSR chain’s table check run on the same system.
Plugs into the recorder or the cameras. Starts watching.
- Any camera, any brandAnalogue or IP, through the DVR or NVR already installed, or straight from IP cameras. Hikvision, Dahua, CP Plus, Secura, TVT and ONVIF.
- Or on your own computerAlready have a server or workstation on site? Tarsyer can run there instead of on our device. No graphics card needed, and the video still stays inside the building.
- Detection runs offline, on siteEvery check runs on the device. Internet is for delivering alerts, not for detecting.
- One device fails, the rest carry onAt sites with more than one device, its cameras move to another and the checks keep running. A fault at one site never affects another.
- Manages itself in the fieldDevices update unattended, in staggered waves, and roll back on their own if an update fails. Head office sees every site’s version and health.
- Nothing worth stealing on the boxNo inbound ports, no vendor cloud in the video path, no credential on the device that opens anything else.
No graphics card. No expensive server.
We have made our models and workflows lean enough to run on an ordinary processor. One small edge device runs ten checks across fifteen cameras at once. Where a site does not need an edge device, an entry-level workstation does the same job.
On the phone that matters, with the photo attached.
Alerts reach people, not just dashboards. Every message carries a snapshot, the store, the camera and the time, so there is nothing to look up.
WhatsApp, instantly
To the store manager, the area manager, or both. Photo proof on every alert. One tap to flag a false alert.
Reviewed and stored
Every alert kept with image and timestamp. Filter by store, type or shift. Confirmed by a second model before sending.
Daily and weekly summaries
End-of-day and weekly roll-ups by email to owners and head office. No logging in needed.
One screen per role. One score per site.
Store managers see their own store. Area managers see their region, ranked. Head office sees every store. Everything exports to Excel in a click.
Built so your team keeps trusting the alerts.
The failure mode of video analytics is not missing things. It is crying wolf until everyone mutes the group. Four layers stop that.
Models tuned to your site
Trained on real store, kitchen and factory footage and adjusted per camera during setup.
A second model looks again
A larger vision model re-reads the snapshot before an alert is sent.
Auditors check the results
Our auditors check a share of every project’s alerts and catch drift early.
One tap to say “not valid”
False alerts are removed from reports and feed the next model update.
The same device, more senses.
Chillers, ovens, freezers
Low-cost sensor nodes wire into the same edge device over the store’s own WiFi. Temperature drift and equipment downtime land in the same alerts and dashboards as the cameras.
Staff feedback by voice note
Store staff record a voice note on their phone. It is transcribed, summarised and turned into products mentioned, issues raised and actions, in any Indian language.
Three things to fix today
A nightly pass over every store’s numbers writes a short, prioritised list for each manager, with a feedback button so the advice gets better every week.
See it running on your own cameras.
A 30-minute call. Bring a floor plan or a camera list and we will tell you which checks fit, what it costs and how soon it goes live.
Or write to sales@tarsyer.com
How the pieces fit together.
Over the local network, either through the DVR or NVR your cameras already record to, or directly to IP cameras. Every channel is discovered automatically. Analogue cameras connect through the recorder, IP cameras either way, and no camera is replaced or re-cabled.
Yes. Most sites use our small edge device because it needs no IT work, but if you already have a server or workstation on your premises, Tarsyer can be installed on it instead. The checks, alerts and dashboards are the same, and the video still stays inside the building. It needs no graphics card, so an entry-level workstation is enough.
No. Every check runs inside the building, on the edge device or your own server. Only alerts, snapshots and counts are sent out, which is a few kilobytes per event rather than a continuous video stream.
Detection carries on, because it runs on the device rather than in the cloud. Alerts queue locally and are delivered when the link returns. Internet is needed to deliver a message, not to spot the problem.
Four layers. Models are tuned per camera at setup, a second larger vision model re-reads the snapshot before an alert is sent, auditors check a sample of what goes out, and anyone can mark an alert not valid in one tap, which removes it from reports and feeds the next model update.
Fifteen cameras running ten checks at once on a standard edge device, and up to 50 cameras in some setups. None of it needs a graphics card. A site with more cameras than one device can carry simply gets a second device; they appear as one site.
Yes. Every model that runs on our devices, and the engine that runs it, is published under a permissive open-source licence such as Apache 2.0, which allows commercial use with no royalties and no obligation to publish anyone's code. It is worth asking every vendor the same question. Some widely used vision models are free to download, but their licence demands a paid commercial licence, or the vendor's whole product made open source, before they can be sold. That responsibility should sit with the vendor, in writing, not with you.