What Tenyks actually is

Tenyks is a vision AI platform that reads the camera feeds you already run and turns them into operational numbers. Instead of replacing cameras, it connects to the streams your existing fleet produces and applies modern vision models to count, time, and measure what happens in view. The current product is focused on restaurant and multi-unit operations: speed of service and wait times, queue and dwell, traffic by hour for staffing, and order-accuracy checks. The deliverable is a dashboard a manager can act on every shift, not another recording no one watches. Tenyks is a Cambridge, UK company and a Y Combinator graduate. See Tenyks' site for the current feature set.

The architecture is deliberately light on hardware. Tenyks connects to any camera that exposes an RTSP or RTSPS stream through your NVR or VMS, so there's nothing new to mount for the platform itself. That keeps the install about integration and tuning rather than cabling, and it's why a proven setup templates cleanly across a fleet of similar sites.

The part worth understanding is the privacy posture, because it's unusual and a genuine differentiator. Tenyks records aggregate, anonymized metrics only: dwell time, visit counts, and broad traffic patterns. It states plainly that it uses no facial recognition or biometric identification, and it's built so it can't identify specific individuals or pick out repeat visitors. On compliance it reports SOC 2 Type II certification along with GDPR and CCPA alignment, backed by external penetration tests and independent audits. For operators who want camera-driven analytics without the exposure of face-based systems, that posture is the reason to choose it.

Where Tenyks fits, and where it doesn't

We install more than seven camera and AI video platforms, so we can give you the unbiased read. Tenyks is the right call on a specific shape of deployment and the wrong anchor on others.

Where Tenyks is the right call:

  • You want operational metrics, not more recording: Tenyks turns existing camera views into numbers a manager can act on: speed of service, queue and dwell, traffic by hour, and process accuracy. If your cameras only get watched after something goes wrong, this puts them to work every shift.
  • Privacy is a hard requirement: Tenyks records aggregate, anonymized metrics and states plainly that it uses no facial recognition or biometric identification. It is built to count and time, not to identify individuals. For operators who want analytics without the privacy exposure of face-based systems, that posture is the point.
  • You run many similar units: Because the setup is stream connections plus zone definitions, not new hardware, a proven configuration templates cleanly across a fleet of similar sites. Multi-unit restaurant, QSR, and retail operators are where this model pays off fastest.
  • You want to keep the cameras you own: Tenyks connects to any camera that provides an RTSP or RTSPS stream through your NVR or VMS. No rip-and-replace. If your fleet is healthy and well-aimed, the work is integration and tuning, not new cabling.

Where Tenyks is the wrong pick:

  • You need person-level identification or watchlists: Tenyks is anonymized by design and does no facial recognition. If your use case requires identifying named individuals, recognizing repeat visitors, or running a watchlist, Tenyks is the wrong tool, and we'll tell you that rather than bend it to fit.
  • You want plain-language footage search or weapons screening: Tenyks is built for operational metrics, not investigation. If your priority is typing a description to find a moment in recorded video, a platform like Spot AI or Coram fits better. If it's weapons screening at the door, that's Evolv. We install all of those and will point you to the right one.
  • Your camera views are wrong for measurement: Counting and timing need a clean line of sight on the zone you care about. A camera aimed at a wall or washed out by glare produces weak numbers no matter how good the platform is. In that case the honest answer is a re-aim or an added camera first, which we flag in the assessment.

How Tec-Tel installs and integrates Tenyks

Because Tenyks runs on the streams you already have, the install is less about new hardware and more about getting your camera views, network, and measurement zones working together. A single site is usually live in one to three weeks once the views are confirmed usable. Here's the real sequence.

  1. Week 1: camera and stream inventory: We catalog the cameras that cover the areas you want measured, confirm each exposes a usable RTSP or RTSPS stream through your NVR or VMS, and check angle, resolution, and lighting. Tenyks runs on the feeds you already have, so the first job is confirming those views are good enough to count people and movement reliably. Output is a written assessment of which camera positions are measurement-ready as-is and which need a re-aim, a lens, or better light.
  2. Week 1 to 2: stream connection and zone setup: We connect the in-scope streams to Tenyks, then draw the zones the metrics depend on: the counter, the queue line, the drive-thru lane, the entry, the prep area. The platform reads those zones and produces anonymized counts and timings. The deliverable is the numbers, not images of identifiable people.
  3. Week 2: metric tuning against your baseline: We tune the thresholds against what your site looks like at peak and off-peak, not vendor defaults. A wait-time number is only useful if the zones and timing rules match how your floor really runs. This is what separates a dashboard people trust from one they ignore.
  4. Week 2 to 3: training, runbook, and handoff: Your managers learn to read the dashboard and act on it. We deliver a written runbook so the deployment isn't dependent on one person, put our response-time standards in writing, and do a single review with your stakeholders before sign-off. For multi-unit operators we template the setup so units two through fifty go faster than unit one.

The single biggest variable is the state of your camera angles, not the platform. A camera aimed at a wall, mounted too high, or washed out by glare produces weak numbers no matter how good the vision models are. That's why our first deliverable is an honest view-by-view assessment: which camera positions are measurement-ready as-is, and which need a re-aim, a different lens, or better light before they'll pull their weight. We'd rather flag that up front than have you discover it after go-live.

Tenyks alongside what you already run

Tenyks is operational analytics, not an investigation tool or a converged security suite. It counts and times exceptionally well, and it deliberately doesn't try to identify people or be your access-control system. That anonymized-by-design posture is a feature, not a gap, but it means you should be clear about the rest of your stack before you choose it.

A common pattern that works: Tenyks for anonymized operational metrics on the front-of-house cameras, running alongside a separate platform for security video and investigation. If your priority is typing a plain-language description to find a moment in recorded footage, that is Spot AI or Coram. If you want workplace-safety analytics on a plant floor with the same anonymized, camera-agnostic approach, that is Intenseye. And if you need doors, readers, and alarms, that is a separate access-control platform from HID, Mercury, or LenelS2.

The broader camera-agnostic overlay strategy, where modern vision AI rides on top of cameras you already own instead of a rip-and-replace, is covered end to end in AI video analytics. Tenyks is one of the platforms we deploy in that model, the one we reach for when the goal is anonymized operational measurement rather than security investigation.

What Tec-Tel adds over going direct

Buying the software is the easy part. The work that determines whether the system earns its keep is install-side: inventorying your cameras and confirming each view is good enough to measure, connecting the RTSP streams through your NVR or VMS, drawing and tuning the measurement zones against your real baseline so the numbers match how your floor runs, training your managers, and leaving a written runbook. Tec-Tel owns all of that. We're a 15-year nationwide integrator, and one accountable project manager runs the deployment from the first call through every site, with Tec-Tel-managed crews and supervised field technicians held to one spec. One company, one runbook, clear accountability throughout.

We also bring multi-vendor honesty. Tec-Tel installs Tenyks, Spot AI, Coram, Dragonfruit, Intenseye, Turing, Verkada, and Genetec, among others. If your goal is anonymized operational metrics on an existing fleet, Tenyks fits and we'll install it. If you need footage search, weapons screening, or person-level identification, Tenyks is the wrong tool and we'll point you to the right one and install that instead. The free consultation walks through your cameras, your views, and the numbers you want to act on, then lands on the platform that genuinely fits.

A note on partner-status language. Tec-Tel installs and integrates Tenyks. We don't claim a specific Tenyks partner certification on this page. If you need a vendor-certified install for a contractual reason, ask in the consultation and we'll confirm what current credentials we hold or pair the install with a certified partner where required.