finds.dev

gtxaspec/raptor

A microservices-based streaming platform for Ingenic T-series based embedded IP cameras

View on GitHub

★ 45CGPL-3.0updated Oct 2026

// the take

Raptor is a microservices-style replacement for the typical monolithic streaming daemon on Ingenic T-series IP camera SoCs (T10-T41, plus A1), splitting video capture, RTSP, WebRTC, recording, motion detection, etc. into separate processes connected by SHM rings and control sockets. It's aimed at embedded/firmware developers building camera products on these specific closed-vendor-SDK chips, notably the thingino firmware project.

The isolation argument is concrete, not just buzzwords: the vendor IMP SDK is closed, stateful and not thread-safe, so putting it in its own process means a WebRTC or RTSP crash can't take recording down with it, and daemons can be swapped live. Ring reference mode is a real optimization, not a vanity feature - it drops per-stream ring buffer size from ~1.5MB to ~9KB by mmap'ing the encoder's backing store directly instead of memcpy'ing frames into shared memory. The project actually tests like it means it: ASAN/TSAN builds, fuzzers with real corpora for the RTSP auth and SDP parsers, and an external black-box conformance suite that runs against RSD and RSD-555 identically. Ed25519 hash-chain signing for recordings and signed snapshots with tamper localization is a legitimately useful feature for a security camera, not just a checkbox.

It's hard-wired to a closed Ingenic vendor SDK (libimp) on a narrow family of MIPS SoCs - this isn't a general camera streaming stack, it's infrastructure for one hardware ecosystem, and any bugs or quirks in that SDK are something Raptor can route around but never fix. At 45 stars and 14 forks with what looks like a single primary maintainer, there's real risk if gtxaspec's attention moves elsewhere, especially since the architecture is split across six satellite repos (raptor-hal, raptor-ipc, raptor-common, compy, raptor-test) that all need to stay in sync. The V4L2 backend, the one path that doesn't depend on the closed IMP stack, is explicitly described in the README as scaffolding: one H.264 stream only, no sub-stream, JPEG, OSD or motion detection, and reconfiguration calls return 'unsupported' rather than working. Operationally, trading one process for twelve independently-started daemons means a field failure now means correlating logs and control-socket state across several binaries instead of one, which is a real cost even if each individual daemon is easier to reason about.

We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →

search the same ground:

// at a glance

Stars
45
Forks
14
Language
C
License
GPL-3.0
Last commit
7 Oct 2026

// nearby

If raptor isn't quite it.

All repos →