Built around the security infrastructure you already have
PARVEK reads standard camera streams, runs alongside your existing recorder, and drives the response hardware on site. Everything below carries its real status — deployed, integrated per site, or scoped per site.
Cameras and video
The integration that matters most, and the one with the most deployment behind it. PARVEK reads standard streams rather than talking to a vendor SDK, so the question is the stream, not the badge on the housing.
The primary path. Any camera that serves a usable RTSP stream meeting the baseline below.
Supported ONVIF profiles for discovery and stream setup.
PARVEK reads cameras directly or through the recorder, and the recorder keeps recording exactly as before. It is not replaced.
Both decoded. MJPEG works but is inefficient for continuous analytics.
Need an encoder to produce an IP stream first. That is a hardware addition, not a software setting.
Access control (PACS)
We build the connection to your access-control system as part of onboarding, and you watch it run on your own doors during the 30-day trial — before you commit to anything.
Representative platforms, not a certified-connector list. What decides it is whether your system can produce an event export carrying a system id, event id, badge id, user id and timestamp — through an API, a database view or a scheduled export. Most enterprise platforms can, including ones not named here. We confirm yours before you commit to anything.
Reading door events — system id, event id, badge id, user id, timestamp — from an API, a database view or a scheduled export. Built against your system during onboarding.
Pairing each door event with the camera frame from that moment, and matching the badge user against the person recognized.
Not planned. PARVEK reads events and correlates them; locking and unlocking stays entirely with your access-control system.
Response hardware
Where a detection needs to do something physical. These are wired at commissioning and depend on hardware being present on site.
Local spoken warning on a detection, in the area where it happened.
Driven through relay outputs on the appliance.
Switched on a detection — frequently the most effective response, and the one that also fixes the detection problem.
Anything a dry contact can trigger. What it is wired to is a site decision.
Notification and workflow
Where events land once they are raised. Everything here is outbound only — no inbound ports are opened on your network.
Alerts with the frame attached, to the people you nominate.
The operations console on your own network, with role-based access per site.
Scheduled summaries and per-event reporting.
Pushing events into your own tooling. Possible, but scoped per deployment rather than shipped as a connector.
What a camera has to meet
This is a compatibility minimum, not a preference. Meeting it does not guarantee good results — the scene, lens and lighting still decide that — but missing it rules a camera out.
Resolution
2 MP / 1080p or higher.
Frame rate
15 fps or higher for general analytics.
Codec
H.264 or H.265.
Streaming
RTSP, or supported ONVIF streaming.
Network
Stable IP network connectivity to the appliance.
Image quality
Usable day and night image quality for the scene.
Representative examples, not a blanket guarantee. Compatibility is model, firmware and stream dependent — we confirm the specific models on your site rather than the brand.
Representative vendors whose current professional IP ranges generally meet the baseline. Not an endorsement, not a partnership, and not a guarantee for a specific model — check yours.
Frequently Asked Questions
Why is there no list of supported camera brands with ticks against it?
Because compatibility is decided by model, firmware and stream, not by brand. A vendor can sell both a camera that works and one that does not. Representative examples, not a blanket guarantee. Compatibility is model, firmware and stream dependent — we confirm the specific models on your site rather than the brand.
Which access-control systems are supported?
We integrate with the one you run rather than publishing a logo wall. The correlation needs an event export carrying a system id, event id, badge id, user id and timestamp, which most platforms provide through an API, a database view or a scheduled export. Tell us what you run and we will confirm what it can feed before you commit.
Do you need an SDK or a partnership with our camera vendor?
No. Reading standard RTSP and ONVIF rather than per-vendor SDKs is what lets PARVEK work across a mixed estate — which is what most real sites have after a decade of piecemeal purchasing.
What does "scoped per site" actually mean in cost terms?
That it is quoted as part of the deployment rather than included in the subscription. The assessment establishes the work; you get the number before anything is committed.
Our estate is mixed and partly undocumented. Where do we start?
The camera check and the site assessment, in that order. Both are free, and both are designed to tell you what you have before anyone proposes what to buy. If something cannot work, you hear it there. Ask at contact@parvek.ai.
Tell us what you run
Cameras, recorder, access-control system. We will tell you what connects today, what is in development, and what would be project work — before you spend anything.