Processing on site
Recognition runs on a computer at your site. Only events like “truck KTR 4821 arrived” leave the building.
Checking lists at the gate, recounting pallets and keeping timesheets take up to 6 hours every shift. Cameras do it on their own, around the clock: under a second from plate to open gate. Start with a 2-week pilot at a price fixed before work begins.
↓ scroll
Six typical scenarios: what the camera sees, what the system does and what lands in your Telegram.
You get a messageKTR 4821 arrived at 02:14. Booking found, spot B‑14. Gate opened.
You get a message124 spots free. Level −2 is full, level −1 has 38 free.
You get a messageGate 3: 24 pallets loaded, 1 left without a scan. Photo attached.
You get a messageShift A: 212 of 220 on site. 3 people late, list attached.
You get a messagePeak today 18:00–20:00. Treadmills 92% busy, rowing machines idle.
You get a messageTruck AA 1234 · container MSCU 482190 · cleared, gate 2.
Your existing cameras or new ones. Vehicles, people, boxes and plates, day or night, in any weather.
Recognition runs on a computer next to the cameras. The video never leaves the site.
Opens the barrier, writes to 1C, sends a message to Telegram.
You don’t have to open a dashboard. Message the bot the way you’d message a colleague and get an answer with numbers and photos.
Nothing here yet. Pick a question or type your own.
Example conversation. In your project the bot answers from your own cameras and systems, and only shows what each person is allowed to see.
The system is built from five blocks. You pay only for the ones your site needs.
$ happ modules --list --site=your-site
→ 5 modules ready · pay only for the ones you need
The exact set of modules and integrations is fixed in the proposal after we visit your site.
Recognition runs on a computer at your site. Only events like “truck KTR 4821 arrived” leave the building.
If the connection drops, gates and counting keep working. Data syncs when the link is back.
Each person sees only their own sites and reports. The bot has the same access rights.
Every gate opening and every alert is stored with the frame behind it. Any disputed case is easy to check.
ProblemTrucks and containers at the port gates were logged by hand.
What we builtCameras read plates, estimate cargo volume in 3D and send everything to the customs database.
ProblemNobody knew how full the car park was. Barriers were controlled by hand.
What we builtCameras at 12 entries and exits, a live dashboard and an app for drivers.
ProblemBadges were shared and attendance was kept by hand across 5 security zones.
What we builtFace recognition at the turnstiles, with hours sent straight to payroll in 1C.
ProblemNo data on attendance or how the equipment was used.
What we builtVisitor counts, equipment heatmaps and Telegram alerts for trainers.
ProblemPeople sorted products into categories and wrote descriptions by hand.
What we builtThe system recognizes products from photos, tags them and drafts descriptions. A person checks the unclear ones.
We mount the cameras, run the cable and set up the hardware. We test the model in rain, darkness and glare on your actual site.
You get the source code, the trained models and access to the servers. No per-camera fee, and you can switch contractors at any time.
Data goes into 1C, ERP, warehouse software or Telegram. Nobody re-types numbers.
10 years in software engineering. Building automation since 2018.
LinkedIn ↗7+ years in business analytics and automation, 10+ in enterprise sales.
LinkedIn ↗10 years in systems development. C++ and Python.
Product and interface design for AI products and industrial dashboards.
LinkedIn ↗10+ years growing tech companies in the US, Europe and CIS.
LinkedIn ↗Computer vision, data science, DevOps, mobile, telephony and on-site engineering.
FROM FIRST CALL TO A WORKING SYSTEM · 2–4 WEEKS
We visit the site, watch how work is done and pick camera spots. You get a plan with a fixed price.
We design the system, buy hardware and start teaching the model on your footage.
Recognition, dashboard and connections to your systems, with a short demo every day.
Installation on site, training for your team, then 3 months of monitoring and support.
Price and acceptance criteria for the pilot are agreed before any work starts.
The camera takes over routine work: checking, counting, writing down. Enter your posts and staff cost to get a rough payback estimate.
A rough estimate, not a promise. The real numbers come out of the on-site assessment, before you pay for anything.
Ranges for typical projects. The exact price depends on cameras, integrations and support and is fixed after the site visit.
Usually not. Most IP cameras from the last 5–7 years will do. If a camera hangs in the wrong spot, we’ll tell you during the visit where to move it.
Recognition runs on a computer at your site, so gates and counting keep working. Messages and reports catch up when the connection returns.
Every decision is saved with a photo. When the system isn’t sure, it asks a person with one tap instead of guessing. We measure accuracy on your site before handover.
A pilot for one task is $10,000, fixed. Bigger projects are $18,000–30,000. The price is agreed after the visit and does not change. There are no monthly fees per camera.
You do. You get the source code, the trained models and access to the servers. You can keep working with us or with anyone else.
It depends on the country and the purpose. We design it carefully: warning signs, storing only what’s needed, access rights and deletion periods. The final check is with your lawyer, and we’ll prepare the technical part.
Yes. We connect in both directions, so data flows in by itself and staff don’t re-type anything.
Describe your site in a couple of sentences. Within 24 hours we reply with what is possible and book a 30-minute call. Then a site visit with a plan and a fixed price, then a 2-week pilot at one point.