SYSTEM REQUIREMENTS

The product is local-first, so the environment matters.

Vetrra is positioned primarily around a Windows-native desktop workflow with local tooling, local storage, and optional local OCR inference. Treat the machine as part of the product architecture.

Operating posture

• Primary public stance: Windows desktop operator workflow.
• Linux headless paths are in active testing and refinement.
• Reliable local disk access is required for intake, staging, encode, and deploy destinations.

Required local tooling

• FFmpeg for encode and stream inspection.
• MKVToolNix for mux and container inspection.
• SABnzbd for optional downloader-integrated intake.
• Ollama plus a configured vision model for local poster OCR features.

Hardware guidance

• Use Intel QSV, NVIDIA NVENC, or another validated acceleration path when possible.
• Provision enough temporary storage for in-flight transcodes and mux staging.
• Expect OCR features to benefit from stronger local inference hardware or patient batch scheduling.

Operational expectation

The application is designed for people comfortable with dependencies, path configuration, and storage policy. The site reflects that openly because the target user values technical specificity over simplified marketing language.