Skip to content

Sentinel v1.1.0 — Feature Update

Latest

Choose a tag to compare

@hemkesh2021-dotcom hemkesh2021-dotcom released this 05 Jul 15:16
· 447 commits to master since this release
5a16b6e

Second public build of SENTINEL — a fully on-device AI surveillance system running
three neural networks together on a single 8 GB NVIDIA Jetson Orin Nano Super.
Detection, face recognition, and vision-language scene understanding — all local, no cloud.

Highlights

  • Person detection & tracking — YOLOv8n (TensorRT) + ByteTrack
  • Face recognition — DeepFace / Facenet512, known-vs-stranger with session Re-ID
  • Scene understanding — LFM2-VL-1.6B via llama.cpp: JSON threat/fire analysis + a
    natural-language chat about the live frame
  • Live web dashboard — Flask, MJPEG stream, HTTP Basic Auth
  • Telegram alerts — strangers / threats / fire, with cooldowns
  • Headless, launched via start_sentinel.sh

The engineering story

The Orin Nano has no dedicated VRAM — CPU and GPU share 8 GB. Running three memory-hungry
models together required launching llama.cpp with GGML_CUDA_ENABLE_UNIFIED_MEMORY=1,
going headless, and starting the VLM before the engine so it claims GPU memory first.
Details in BUILD.md.

Docs

Setup → SETUP_GUIDE.txt · Build (TensorRT + llama.cpp) → BUILD.md · Config → .env.example

Known limitations

  • Multi-person face association can bleed identities (single-person recognition is solid)
  • No TLS on the dashboard yet; face DB uses pickle
  • No systemd auto-start; software video decode (NVDEC not yet used)

Tested on

NVIDIA Jetson Orin Nano Super (8 GB) · JetPack 6.x · CUDA 12.6 · Imou Ranger S2 camera.

Historical v1 release — not production-hardened. Do not deploy in public spaces without
complying with local privacy / biometric law.

— Hemkesh

Full Changelog: V1.0...v0.1.0

Version naming

On 15 October 2026, this release was renamed from v0.1.0 to v1.1.0 and classified as a regular v1 release. Both tags identify the same original commit, 5a16b6e4a217a0973abdaf3c5fcdff7cd0f40412. The legacy tag is retained for existing links. No source code changed as part of this naming update; the original scope and limitations still apply.