Intelligent Video Surveillance System: Inside VALT (a $9.7M VMS) | Fora Soft

Why Fora Soft wrote this playbook

We did not write this article from a marketing brief. We wrote it because we shipped VALT — the intelligent video surveillance system featured below — and now operate it for 650+ US organizations including police departments, child advocacy centers, and medical schools. Every architecture call, every codec choice, every PTZ workflow on this page was tested in production against real interrogation rooms, real training simulations, and real recorded evidence chains.

VALT is not a one-off. Our portfolio includes drone-based aerial surveillance for land control, custom anomaly-detection ML pipelines, ONVIF Profile M analytics integrations, and mobile-camera ingest for clients who needed surveillance beyond a fixed camera grid. Roughly 40% of our active engineering capacity sits in video, streaming, and computer vision — the disciplines a modern video surveillance development partner needs to ship a credible product.

If you are scoping a VMS, an intelligent monitoring add-on to an existing camera fleet, or a vertical surveillance product (police, healthcare, education, retail, smart city), this article walks the same trade-offs we walked with our clients — from streaming protocol selection down to dollar costs — and shows how Fora Soft delivers the build using Agent Engineering to compress timelines and price.

The VALT case in numbers

VALT is an intelligent video surveillance system — or, in industry terms, a Video Management System (VMS) with native AI analytics. Below is what the business looks like today.

The product video below shows the workflow operators actually use. It is the real interface, not a marketing render.

Watch the 2-minute VALT product walkthrough on YouTube →

What intelligent video monitoring actually means in 2026

The phrase is used loosely. To buyers, “intelligent” can mean a marketing-grade motion sensor or a full ML pipeline that classifies behaviour. Below is the working definition we use when scoping projects — built from the features modern enterprise procurement actually checks.

Tier 1 — Smart capture (table-stakes in 2026)

Motion-triggered recording. The camera or the server detects movement and only captures relevant clips, slashing storage cost by 60–90%. VALT’s motion-detection feature is what lets a 30-day retention policy fit on commodity disk.

PTZ presets and scheduled recording. Operators define camera positions for shift changes — one click sweeps the whole interrogation room or the whole lab bench. Combine with a scheduler and the camera covers a six-hour simulation without an operator.

Push-to-talk audio. Two-way voice over the same camera is the line between “CCTV” and “monitoring system.” Required for medical instructors and for child-advocacy interviewers.

Tier 2 — Searchable evidence

Spoken-word search. Type a word, the system jumps to every moment it was said. VALT layers AWS’ Amazon Transcribe on the audio track and indexes the transcripts. For police interrogations, this turns an 8-hour video into a one-keystroke evidence finder. We covered the underlying integration in our custom speech-to-text development service.

Time-stamped notes. Reviewers tag specific frames; the tags become hyperlinks in an exported PDF. The PDF is the artefact that goes to court, into student-feedback files, or into a child-protection case.

Granular permissions. Per-camera, per-folder, per-user RBAC backed by an immutable audit log. Without it the product cannot pass CJIS or HIPAA review.

Tier 3 — ML-driven understanding

Object & person detection. YOLOv8/YOLOv11 pipelines tag people, vehicles, faces, packages. Our deep dive on detection models is in Top 7 Anomaly-Detection Models for Video Surveillance.

Anomaly detection. Unsupervised models flag unusual movement patterns — loitering, after-hours presence, abnormal crowd density. See real-time anomaly detection in video surveillance for the inference patterns we use.

Behaviour analytics. Counting, dwell time, queue length, PPE compliance, fall detection. The technical playbook is documented in our guide on integrating video analytics with surveillance.

VALT under the hood — the stack we shipped

Architecture is where most VMS builds break. We chose a stack that is open, fast to iterate, and cheap to scale.

The deep dive on ONVIF Profile M and where it fits next to Profile T lives in our ONVIF Profile M explainer.

Reference architecture for an intelligent VMS

The diagram below is the canonical pipeline we deploy. Cameras push RTSP into a Wowza cluster, the cluster fans out HLS for many viewers and WebRTC for the live ops console, and parallel jobs feed the ML and ASR layers.

The same eight-stage layout works whether you have 50 cameras in one school or 2,500 across a national chain — you scale ingest and ML horizontally, keep the API and search single-tenant per customer.

Streaming protocol decision — RTSP, HLS, or WebRTC

A surveillance product almost always needs all three protocols. Buyers and engineers confuse them, then over-budget. The split below is what we run on VALT.

Bandwidth and storage — the numbers that kill bad budgets

VMS budgets blow up when buyers underestimate camera bitrate. The math below is the rule-of-thumb we use during scoping.

Three rules fall out of this table. One: H.265 is non-negotiable; it halves storage at the same visual quality. Two: motion-triggered recording cuts another 70–80%. Three: use tiered storage — hot for 7 days, warm for 30, cold for the legal-hold tail — or your S3 bill becomes the line-item the CFO blocks.

Build vs. buy — the camera-count rule

The honest answer is shaped by camera count, vertical, and how custom the workflows are. Below is the framework we walk through with prospects, including the cases where we explicitly recommend buying a vendor product instead of hiring us.

Cost model — what an MVP and a production VMS actually run

We give ranges below, not single numbers, because cameras-per-tenant, ML scope, and compliance scope all dominate. The ranges reflect Fora Soft pricing using Agent Engineering — our internal AI-assisted delivery process — which lands consistently below the industry-average $132K, 13-month custom-software baseline analysts publish for projects of this size.

For run-rate, plan on $4–$9 per camera per month for cloud bandwidth + storage at 1080p H.265 with motion recording, plus ML inference cost (Jetson Orin NX at the edge ~$350 hardware one-off; cloud GPU inference roughly $0.30 per camera per day at YOLOv8 quality).

Security & compliance — what regulated buyers will ask

VALT runs in three regulated verticals, and each one tested a different compliance angle.

1. CJIS for police use. Criminal-justice data demands tamper-evident audit logs, encryption in transit and at rest, and strict separation between agencies. We isolate per-tenant storage at the bucket level, sign every write to the audit log with a hash chain, and deny export without a justification field.

2. HIPAA for medical training. Patient-identifiable footage from simulation suites needs encryption keys controlled by the institution and break-glass auditing on every replay. We support per-tenant KMS, BAA-ready cloud regions, and one-click revocation.

3. FERPA for child advocacy and education. Footage of minors carries parental-consent requirements and short retention limits. We expose retention policies as per-folder TTLs the institution sets in the UI, not the engineer.

4. SOC 2 Type II. Enterprise procurement increasingly demands it as table-stakes. The audit cost typically lands around $25–$40K for the readiness assessment plus annual auditor fees — build the controls into sprint 1, not retrofit them in year 2.

5. GDPR for EU footage. Right-to-erasure on individuals is a real engineering ask — you need cryptographic key wipe at the segment level, plus a data-processing-agreement template ready for prospects.

Use cases that pay for the product

A common mistake in surveillance products is selling “security” when buyers are paying for “evidence,” “training,” or “process control.” The verticals below are the ones that actually fund custom VMS work.

Law enforcement and corrections

Police interrogations, body-camera evidence intake, court holding cells. PTZ presets cover the standard interrogation room layout; spoken-word search lets a detective find “he said the address” in seven seconds instead of seven hours; transcription PDF goes straight into the case file. CJIS audit log is the gating feature.

Medical and clinical training

Simulation centres at medical schools record OSCE exams, surgical residency drills, and standardized-patient encounters. Examiners zoom into a hand technique, time-stamp a feedback note, and export per-student PDF reports. The same workflow ports to nursing schools, paramedic academies, and dental simulation labs.

Child advocacy and forensic interviewing

Centres recording interviews with vulnerable minors run on extreme privacy and auditability. Two-camera coverage (face + room), tamper-evident audit, and short retention windows are non-negotiable. The PDF export becomes the artefact shared with prosecutors and child-protection officers.

Adjacent verticals worth scoping

Manufacturing safety: PPE-compliance object detection feeding alerts to floor managers. Retail loss prevention: dwell-time and exit-anomaly detection with LPR at the parking lot. Smart city: traffic counting, crowd density, vehicle classification. Drone-based aerial monitoring: covered in our DSI drones case study — a different camera class, identical pipeline downstream.

Mini case — what shipping VALT taught us

Situation. The client came to Fora Soft with a working but bandwidth-bound product: roughly 400 cameras, frequent stream stalls when more than 30 reviewers were live, and an evidence search that scanned filenames only. The roadmap demanded scaling to thousands of cameras, adding spoken-word search, and supporting iPads as cameras inside child-advocacy interview rooms — without tripling the cloud bill.

Plan. Twelve weeks. Sprint 1–2: replace the stream encoder with Wowza, switch cameras to H.265 ingest. Sprint 3–4: layer Amazon Transcribe + OpenSearch for word search. Sprint 5–6: ship native iOS/Android encoders so phones become RTSP cameras. Sprint 7–8: PTZ preset workflow, time-stamped notes, PDF export. Sprint 9–10: tenant-isolated audit logging, CJIS-grade encryption review, soak test at 2,500 cameras.

Outcome. Camera count rose from 400 to 2,500 (+525%); concurrent reviewers crossed 25,000 daily; bandwidth per camera dropped 48% thanks to H.265 + motion-only recording; revenue grew to the $9.7M/year run-rate the product holds today. The product now serves 650 organizations across police, medical, and child-advocacy verticals on the same multitenant codebase. Want a similar 12-week assessment for your VMS?

Edge AI vs. cloud inference for ML features

Once you add ML, you decide where it runs. Two principles dominate.

A decision framework — pick a VMS path in five questions

1. Are you reselling the product, or just using it? If you plan to sell it as SaaS, you must build — you cannot resell Verkada. If you only need it internally, COTS is almost always cheaper.

2. How many cameras in 24 months? Under 100 favors COTS. 100–500 favors hybrid (Milestone/Genetec SDK + custom UI). Over 500 with a vertical workflow favors a custom build like VALT.

3. What is the regulatory floor? CJIS, HIPAA, FERPA, GDPR, SOC 2 each pull architecture in slightly different directions. The earlier you fix the floor, the cheaper the build.

4. Latency target? Sub-second → WebRTC + edge inference. 5+ seconds OK → LL-HLS + cloud inference, half the cost.

5. ML model lifecycle? If the analytics customer asks change every quarter, plan a feedback-loop pipeline (label-store, retraining cadence) into sprint 0. Bolting it on later is the most expensive shortcut in this space.

Pitfalls we have watched VMS teams fall into

1. Underestimating bandwidth at peak. Average bitrate is comforting; peak-hour bitrate is what saturates your uplink. Provision 1.5× theoretical peak, not 1× theoretical average.

2. Ignoring time sync. Without NTP discipline across cameras, evidence chronology fragments. The audit log becomes inadmissible the day the first lawyer notices.

3. Bolting compliance on at the end. CJIS-grade audit logging adds 3× the cost retrofitted versus designed-in. The same is true for HIPAA encryption.

4. Skipping false-positive tuning. A motion-detection feature that fires on a passing cloud at 4 AM destroys adoption faster than no feature at all. Tune thresholds with the customer in week 2, not month 6.

5. Naive single-tier storage. 1080p 24/7 on a single S3 tier costs roughly 4× what tiered storage costs at 30-day retention. The CFO finds this in month 3 and the project bleeds.

KPIs — what to actually measure

Quality KPIs. Stream uptime per camera (target 99.5%+), end-to-end latency p95 (sub-second for ops, <5s for review), false-positive rate on anomaly alerts (under 5% by month 3), search recall on spoken-word queries (over 90% on clear audio).

Business KPIs. ARR per camera, gross margin per tenant, churn by vertical, expansion revenue from added features (transcription, ML upgrade tiers). VALT’s public number is $9.7M ARR / 2,500 cameras — roughly $3,800 per camera per year, which is the benchmark to beat.

Reliability KPIs. Mean time to detect a stuck stream (under 2 minutes); mean time to recover (under 10 minutes via auto-failover); audit-log completeness (100%, no gaps); RTO and RPO inside vendor SLA. Compliance auditors look at these first.

When NOT to build a custom VMS

We tell prospects to step back from a custom build when (a) the camera count is below 50 with no SaaS resale ambition; (b) the workflow has no vertical specialisation that COTS cannot handle; (c) the operations team is not ready to own a 24/7 streaming platform; or (d) the total budget under $80K cannot stretch beyond a hardened MVP.

In any of those cases, a Verkada or Eagle Eye Networks subscription combined with an integration project — we still help build the integration — gets you to value six months faster.

FAQ

What is the difference between a VMS and an intelligent video surveillance system?

A VMS (Video Management System) records, streams, and stores camera feeds. An intelligent video surveillance system layers AI on top — motion detection, object recognition, anomaly alerts, spoken-word search. VALT is a VMS with all four AI layers built in.

How long does it take to ship an MVP intelligent VMS with Fora Soft?

Three to four months for a smart-capture MVP (ONVIF ingest, motion recording, web playback, RBAC, audit log). Adding searchable evidence and ML analytics typically adds two to four months on top, depending on scope. Agent Engineering at Fora Soft compresses these timelines materially below the industry baseline of 13 months.

Can a smartphone really replace a fixed IP camera?

For pop-up sites, training rooms, and child-advocacy interviews — yes. VALT’s mobile SDK turns any iOS or Android device into an RTSP source feeding the same Wowza ingest. You lose PTZ and 24/7 mounting, but you gain deployable-in-minutes capture for less than $400 in hardware.

Why H.265 and ONVIF Profile T — not Profile S?

Profile S is the legacy ONVIF tier — H.264, weak authentication. Profile T is the modern tier — H.265 (50% storage savings), HTTPS, modern PTZ. Buyers running Profile S today should plan a refresh; firmware support is winding down across major camera vendors.

Should ML run on edge hardware or in the cloud?

Edge (Jetson Orin NX) when the camera fleet exceeds ~50 per site and bandwidth or privacy is the constraint. Cloud when the model fleet changes frequently, you want fewer moving parts, or per-customer model tuning is on the roadmap. We routinely ship hybrid — edge for hot-path detection, cloud for retraining and analytics.

Is VALT the only video-surveillance product Fora Soft has shipped?

No. We also built DSI Drones — aerial surveillance for land control — and contributed ML pipelines documented in our anomaly-detection guide. Around 40% of our active engineering work sits in video, streaming, and computer vision.

How is Fora Soft cheaper and faster than the industry baseline?

We use Agent Engineering — an AI-assisted internal delivery process that automates scaffolding, refactoring, and large parts of regression testing. The result is consistently shorter calendars and lower fully-loaded cost per feature. We will share concrete delivery examples on a scoping call.

What integrates with VALT-style systems out of the box?

Any ONVIF Profile S/T camera, any RTSP source, mobile devices via SDK, AWS Transcribe and Whisper for ASR, OpenSearch/Elastic for full-text search, and standard IdP (SAML/OIDC) for SSO. Custom integrations — Genetec, Milestone, Avigilon — we scope per project.

What to Read Next

Ready to ship your own intelligent video surveillance system?

A modern intelligent video surveillance system has four jobs — capture cleanly, search instantly, understand automatically, and prove provenance. VALT shows the four jobs working together at $9.7M ARR; the architecture, the codec choices, and the ONVIF tier are the levers that decide whether your build hits the same numbers or burns out at the bandwidth bill.

If your camera count, your vertical, or your SaaS go-to-market puts you in the build column of the table above, the fastest next step is a 30-minute call with the team that already shipped a system serving 25,000 daily users. We will walk the architecture, the codec math, and the realistic cost in one session — and tell you honestly when buying instead would be cheaper.