VibeNVR is a modern, modular, and containerized video surveillance system designed to manage IP cameras, recordings, motion detection, and a unified event timeline. It features a custom high-performance video engine (VibeEngine) built for efficiency and reliability, wrapped in a premium React-based interface.
Project Status: This is a Vibe Coding Project. Extensive testing has been performed to ensure stability, but we are always open to new help and contributions from the community!
⚠️ IMPORTANT: When updating, always check the Release Notes and ensure yourdocker-compose.prod.ymland.envare synchronized with the latest version.Language Policy: Please note that English is the official and only supported language of this project. All code, user interface elements, commit messages, issues, and documentation (including wikis) must be written strictly in English to maintain consistency and accessibility for the global community.
We are building VibeNVR to be the best local NVR experience, and we can't do it without you.
Found a bug? Have a great idea for a feature? Want to share your setup? Please Open an Issue! We are extremely proactive, always available to fix problems, and love adding new capabilities requested by the community. Your feedback is what drives this project forward.
This software is currently in active beta development. The database schema is still evolving and may undergo changes. While we strive for backward compatibility, manual database cleanup or migration steps might be required when updating to newer versions.
| Feature | Description |
|---|---|
| 🖥️ Modern Web Interface | Ultra-premium UI built with React, Vite, and Lucide icons. |
| 🎨 Customizable Dashboard | Toggle widgets and graphs to suit your monitoring needs. |
| 🛡️ Secure by Design | Full JWT authentication, 2FA with Trusted Devices, Rate Limiting, and HttpOnly Media Cookies. |
| 📷 Advanced Video Engine | Custom Python engine using PyAV & FFmpeg for RTSP streaming, with OpenCV for motion detection and image processing. |
| ⚡ Passthrough Recording | Direct Stream Copy support for near-zero CPU usage recording (experimental, with auto-fallback). |
| 🎯 Smart Motion Detection | Native motion detection with adjustable sensitivity, gap, and pre/post-capture buffers. |
| 📅 Event Timeline | Unified browser for movie recordings and high-res snapshots with instant filters. |
| 🔑 API Access Tokens | Secure, read-only API tokens with TTL (Expiration) and hashed storage for 3rd party integrations. |
| 💾 Storage Management | Automated background cleanup (FIFO) and Bulk Deletion tools. |
| 📁 Camera Groups | Organize cameras into custom groups for logical multi-view management. |
| 🕙 Timezone Synchronization | Full ISO 8601 support ensures perfect timing between engine, backend, and UI. |
| 📊 Real-time Monitoring | Native WebCodecs H.264 low-latency WebSocket streaming, with selectable modes and adaptive JPEG polling fallback. |
| 🛡️ IP Ban Protection | Automated ffprobe pre-flight checks and per-camera RTSP Transport selection (TCP/UDP) to ensure maximum compatibility. |
| 🐳 Docker-Native | Zero-dependency deployment with Tag-Driven CI/CD for stable, predictable releases. |
VibeNVR is built with security as a priority. For detailed information regarding our security model, authenticated media, internal port protection, vulnerability reporting, and Role-Based Access Control (RBAC), please see our dedicated Security Documentation.
VibeNVR maintains a public, anonymous telemetry dashboard where you can see global usage statistics, active versions, and hardware trends: View Public Telemetry Dashboard
We only collect non-sensitive, anonymous technical data:
- Application Version: To see how many users are on the latest release.
- Hardware Profile: CPU count, total RAM (rounded to GB), and GPU acceleration status.
- Usage Metrics: Total number of cameras, camera groups, and events in the database.
- System Info: Operating System and hardware architecture (e.g., Linux x86_64).
- Anonymous ID: A randomly generated UUID that uniquely identifies the installation without linking it to any personal identity or IP address.
- Feature Flags: A simple indicator if notifications are configured (no addresses or tokens).
The report is sent once 30 seconds after startup and then once every 24 hours.
Your privacy is paramount. You can disable telemetry at any time:
- Navigate to Settings in the web interface.
- Open the Privacy & Analytics section.
- Toggle off Enable Anonymous Telemetry and save.
- Docker & Docker Compose (V2 recommended)
-
Get the files: Download the docker-compose.prod.yml file.
Alternatively, clone the repository to get all files (recommended for easier updates):
git clone https://github.com/spupuz/VibeNVR.git cd VibeNVR -
Configuration (.env): VibeNVR is configured using a
.envfile.- If you cloned the repo, you can use the included
.envfile as a base. - If you just downloaded the compose file, create a file named
.envin the same directory.
Important: Update your
.envwith secure values:# .env content example # ENV Configuration SECRET_KEY=change_this_to_a_long_random_string # CRITICAL: Security key (min 32 chars). Application won't start in production with a weak key unless ALLOW_WEAK_SECRET=true is set. WEBHOOK_SECRET=change_this_to_a_long_random_string # REQUIRED: Validates engine->backend communication. Set SAME as SECRET_KEY. # POSTGRES_PASSWORD=vibenvrpass # Storage & Paths # VIBENVR_DATA=./viben_data # Where recordings and logs are stored # VIBENVR_DB_DATA=./viben_db_data # Database persistence path # Ports # VIBENVR_FRONTEND_PORT=8080 # Frontend Access Port # VIBENVR_BACKEND_PORT=5005 # Backend API Port # Hardware Acceleration # HW_ACCEL=true # Enable Hardware Acceleration (true/false) # HW_ACCEL_TYPE=auto # auto, nvidia, intel, amd
See the
.envfile in the repo for all available options. - If you cloned the repo, you can use the included
-
Start the service:
docker compose -f docker-compose.prod.yml up -d
When a new version is released, follow these steps to ensure a clean update:
-
Back up your .env file:
cp .env .env.bak
-
Retrieve the new production compose file: Ensure you are in the project root.
curl -O https://raw.githubusercontent.com/spupuz/VibeNVR/main/docker-compose.prod.yml
-
Pull the new images:
docker compose -f docker-compose.prod.yml pull
-
Stop the current stack:
docker compose -f docker-compose.prod.yml down
-
Start the new stack:
docker compose -f docker-compose.prod.yml up -d
The default configuration above uses Bind Mounts (mappings to local folders like ./data/recordings) which makes it easy to access your video files directly from the host system.
Option A: Using Local Folders (Bind Mounts - Recommended) This allows you to easily backup or view recordings using tools on your host machine.
- Recordings:
./data/recordings - Database:
./data/db
Option B: Using Docker Volumes
If you prefer to let Docker manage storage (better for performance on some non-Linux filesystems), change the volumes section in docker-compose.yml:
volumes:
- vibenvr_data:/dataAnd define the volume at the end of the file:
volumes:
vibenvr_data:VibeNVR integrates perfectly with gethomepage.dev using the customapi widget.
Example services.yaml configuration:
- VibeNVR:
icon: mdi-cctv
href: http://your-vibenvr-ip:8080/
description: Video Surveillance
server: your-docker-host # Optional: Requires docker socket access in Homepage
container: vibenvr-backend
widget:
type: customapi
url: http://your-vibenvr-ip:8080/api/v1/homepage/stats
headers:
X-API-Key: "your-api-token-here"
method: GET
mappings:
- field: cameras_online
label: Online
- field: events_today
label: Events (24h)
- field: storage_used_gb
label: Storage (GB)
- field: uptime
label: Uptime
- field: cameras_recording
label: Recording
- field: storage_total_gb
label: Total Disk (GB)Since VibeNVR binds to 127.0.0.1 by default, you MUST use a Reverse Proxy to access it from other computers or the internet.
Recommended Setup with Nginx Proxy Manager (NPM):
- Network Setup: Ensure NPM and VibeNVR containers can talk to each other. The easiest way is to put them on the same Docker network, or point NPM to the host IP (
host.docker.internalor gateway IP). - Proxy Host Configuration:
- Domain Names: Set up your domain (e.g.,
nvr.yourdomain.com). - Scheme:
http - Forward Host:
vibenvr-frontend(if on same network) or Your Host LAN IP. - Forward Port:
80(container port) or8080(host mapped port).
- Domain Names: Set up your domain (e.g.,
- Websockets Support: Enable "Websockets Support" in NPM for live streaming stability.
- SSL: Enable "Force SSL" and strictly use Let's Encrypt certificates.
Why this is safer? Attackers scanning your public IP will find all ports (5000, 8000) closed. They can only access the NVR through port 80/443 via your Proxy, which enforces HTTPS and potentially extra authentication layers.
If you're running VibeNVR on a system with the Proxmox kernel (pve-kernel), OpenMediaVault, Synology, QNAP, or similar NAS devices, you may encounter permission errors like:
PostgreSQL errors:
could not create Unix socket for address "/var/run/postgresql/.s.PGSQL.5432": Permission denied
FATAL: could not create any Unix-domain sockets
Engine/Backend errors:
socket.socketpair()
PermissionError: [Errno 13] Permission denied
Solution: These errors are caused by kernel security restrictions (seccomp/AppArmor). Try the following solutions in order:
Option 1: Disable seccomp and AppArmor
Add these lines to each service (backend, engine, db) in your docker-compose.yml:
security_opt:
- seccomp:unconfined
- apparmor:unconfinedOption 2: Use Privileged Mode for ALL Containers
⚠️ CRITICAL WARNING: Running containers in privileged mode bypasses Docker's isolation and grants root-level access to the host machine. Only use this if absolutely necessary on specific problematic kernels (like older Proxmox/OMV) and ensure your system is well-segmented.
If Option 1 doesn't work (common on OpenMediaVault + Proxmox kernel), you MUST change privileged: false to privileged: true for every service (frontend, backend, engine, db) in your docker-compose.yml:
services:
frontend:
privileged: true # Change from false to true
backend:
privileged: true # Change from false to true
engine:
privileged: true # Change from false to true
db:
privileged: true # Change from false to trueOption 3: System-level fix (if all else fails)
# Enable unprivileged user namespaces
sudo sysctl -w kernel.unprivileged_userns_clone=1
# Make it permanent
echo "kernel.unprivileged_userns_clone=1" | sudo tee /etc/sysctl.d/99-userns.conf
sudo sysctl --system
# Restart Docker
sudo systemctl restart dockerAfter making changes, restart the containers:
docker compose down
docker compose up -d| Login Screen | Main Dashboard |
|---|---|
![]() |
![]() |
| Live View (Grid) | Video Playback |
|---|---|
![]() |
![]() |
| Event Timeline | Camera Scanner |
|---|---|
![]() |
![]() |
| Camera Management | Camera Groups |
|---|---|
![]() |
![]() |
| Camera Config (General) | Camera Config (Motion) |
|---|---|
![]() |
![]() |
| System Settings | Notification Channels |
|---|---|
![]() |
![]() |
| Dashboard | Live View | Timeline |
|---|---|---|
![]() |
![]() |
![]() |
VibeNVR is split into four main microservices:
- Frontend: React-based SPA providing a sleek, responsive dashboard.
- Backend: FastAPI server handling logic, secure database access, and secure HttpOnly cookie-based media relay.
- VibeEngine: Custom processing engine for motion detection, recording, and overlays. Uses PyAV for RTSP stream ingestion and OpenCV (cv2) for frame processing.
- Database: PostgreSQL for persistent storage of camera configs and events.
If you find VibeNVR useful, please consider giving it a star or buying me a coffee! Your support helps me maintain and improve the project.

This project is open source and available under the MIT License.
DISCLAIMER: THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Made with ❤️ by spupuz
















