← Back to work
BackendBackend only

FaceMe Recognition Server

Device registration, face enrollment, and live recognition events.

What they needed

A licensed FaceMe SDK needed a real server layer: register cameras (RTSP), enroll users with validity windows, run recognition without blocking the API, and query events afterward.

What I delivered

  • Early API: webcam/RTSP recognition plus user face CRUD over FastAPI
  • Later FaceMe Server: devices, users, images, event filters, Alembic + PostgreSQL
  • Async processing so SDK work does not freeze the web server
  • Setup guides and multi-milestone handover packages

Why it helped

Recognition became an HTTP service the rest of the product could call — enroll once, watch devices, query who was seen.

How the work unfolded

Recognition API MVPWebcam/RTSP endpoints and basic face enrollment.
Full FaceMe serverDevices, users, events, migrations, and ops documentation.

Tech in the build

PythonFastAPIPostgreSQLOpenCVCyberLink FaceMe SDK

Access

Backend-only (Swagger / local API — requires licensed SDK)