Leo · 2026-10
A CCTV storage appliance OEM for integrators is an agreement in which a manufacturer builds recording hardware to the integrator’s own brand specification. woCyber, the export brand of a Beijing-based storage hardware manufacturer, builds white-label AiNAS appliances with edge AI event filtering, ONVIF and PoE camera onboarding, and 7, 14 or 30-day retention, with volume supply on request.
Security footage stopped being a small line item once cameras moved to 4 MP and above and clients began asking for 30-day retention as a default. Every added megapixel and every added retention day lands on the recorder rather than on the camera. A regional integrator is now expected to quote storage as a designed subsystem, covering capacity, redundancy, retention depth and a support path, while still holding the camera margin that won the deal.
That expectation leaves one narrow problem to solve. The recorder has to fit the client’s camera count today, survive a camera count half again as large in year three, and arrive as an OEM product that the integrator brands, packages and supports. Both halves have to be settled in the agreement, because the terms left open tend to resurface later as change orders, and closing that gap is the job a CCTV storage appliance OEM for integrators takes on before the first purchase order.
Most integrators overspend on camera resolution and underspend on retention. Retention is the part the client is genuinely buying, because an incident that falls outside the retention window is footage the client never had. Resolution is visible on a comparison sheet. Retention depth stays invisible until the day it matters.
The term describes a commercial arrangement rather than a product category. A manufacturer builds the recording hardware to the integrator’s brand specification, and the integrator sells the finished appliance as its own product. The manufacturer supplies the hardware platform, the firmware baseline and the certification file set. The integrator supplies the brand layer, the sales channel and the service relationship.
That split shows up at the first support call. If the appliance is a re-badged box from a brand the integrator does not control, the firmware path, the spare-parts path and the retention default belong to someone else. Under an OEM arrangement those three decisions sit with the integrator and are fixed in the agreement rather than discovered in month nine.
Five groups of numbers decide whether two storage quotes are comparable at all: camera count and bitrate, retention days, redundancy level, network port speed, and the chassis ceiling in bays and terabytes.
Quotes that omit the retention window and the RAID level cannot be compared, because one headline capacity figure can describe two very different usable volumes.
Daily storage per camera equals the recording bitrate in megabits per second multiplied by about 10.8, which yields gigabytes per day, and total capacity equals camera count multiplied by that daily figure multiplied by retention days.
Storage in GB = cameras x bitrate in Mbps x 10.8 x retention days.
Consider a hypothetical 12-camera office and warehouse site recording at an assumed 4 Mbps with 30-day retention. The arithmetic is 12 x 4 x 10.8 x 30 = 15,552 GB, or about 15.6 TB of recording data. A four-bay chassis fitted with four 8 TB drives in RAID 5 presents roughly 24 TB of usable space, which leaves headroom for the camera additions the client has not committed to yet.
Two adjustments belong in the same pass. Codec choice moves the bitrate, because the ITU H.265 recommendation compresses an identical scene at a lower bitrate than H.264 and lowers the daily figure without touching the retention window. Redundancy choice moves the usable share, because RAID 5 on four bays keeps three quarters of the raw capacity while RAID 6 keeps half and tolerates two simultaneous drive failures.
The bitrate figure is a project input supplied by the camera set or measured on site. A manufacturer cannot publish it on the buyer’s behalf, and a quote built on a guessed bitrate is a quote that will be revised.
Edge AI filtering changes the storage math by deciding what gets written before the footage reaches the disk, so event-driven recording stores less than a continuous stream at identical camera settings. The woCyber S1 appliance classifies people, vehicles and pets on the device itself, publishes a false alarm rate below 3 percent on its product page, and keeps 100 percent of the computation local. A lower false alarm rate also keeps the review queue short enough for one operator to work through.
Integrators standardizing a white-label security line can review products/s1-security-kit, which pairs on-device classification with 7, 14 and 30-day retention tiers, ONVIF camera onboarding and physically isolated accounts on one appliance. The retention tier is chosen per deployment rather than per camera model, which keeps the SKU ladder short.
The 30-day tier fits multi-site and regulated clients, while the shorter tiers fit offices and single-site retail, because the tier has to match how long an incident takes to surface after the fact.
| Retention tier | Client profile that usually specifies it | What it changes in the storage design |
|---|---|---|
| 30 days | Multi-site retail, clinics and sites carrying an insurance or audit requirement | Capacity is sized on 30 days of every camera at full bitrate, the single largest driver of bay count |
| 14 days | Offices, schools and smaller industrial sites | Roughly half the capacity of an otherwise identical 30-day design |
| 7 days | Single-site retail and low-traffic commercial sites | Fits two-bay hardware at moderate camera counts |
Retention is a recording-policy setting, and the number the client cares about is the number that survives the first incident review. Writing the tier into the agreement is what stops a 7-day deployment from being compared against a 30-day bid on price alone.
ONVIF and PoE cut installation labor by standardizing the two things that used to be vendor-specific on a camera project: how a camera is discovered and controlled, and how it is powered. The ONVIF profile set defines a common interface, so a recorder that implements the profile can onboard cameras from different manufacturers without a per-model integration. Power over Ethernet carries data and power on one cable run per camera, which removes a separate power drop and its conduit from the labor estimate. The IEEE 802.3 family defines the PoE power classes that camera and recorder vendors build against.
For smaller sites where the camera count stays modest and the client also wants shared files on the same chassis, products/a2-pro-nas documents a two-bay platform with ONVIF and PoE camera onboarding, RAID 1 and a 48 TB ceiling. One appliance can serve as the file share and the camera recording target, which removes a second chassis from the bill of materials.
Open standards also answer a question North American buyers keep asking: what happens when the camera vendor changes. A recorder that onboards over ONVIF is not tied to one camera brand, so the camera set can be replaced without replacing the storage layer. Buyers who want to test that claim on a live clip can work through the capacity figures in nas-video-surveillance-retention-storage-sizing and the verification list in ai-nas-security-features-to-verify-before-deployment.
A white-label agreement has to fix five things in writing before tooling starts: the brand layer, the packaging and documentation, the power region, the compliance file set, and the ownership of anything custom.
Where an existing platform is reconfigured, the minimum order quantity is confirmed per project, and a new PCB respin or new tooling raises it to 1,000 units. Custom tooling is either amortized into the unit price or invoiced separately, and ownership transfers to the buyer once it is paid for; customer-specific tooling is not reused for other clients. Payment terms and warranty terms are confirmed in writing at quotation. Sample units are charged at the published single-unit price, and the sample fee is credited in full against the first production order.
Four verification steps protect a program order: the production process behind the appliance, third-party factory checks, the written commercial terms, and the certification file set for the destination market.
Fix the retention tier and the capacity math before the brand layer is negotiated, because those two numbers decide the chassis and everything else is cosmetic by comparison. Integrators who settle the logo and the packaging first usually end up re-specifying the hardware after the first site survey, which costs more than the delay.
The oem-odm overview covers the white-label options in more detail, and vetting-nas-server-manufacturers-us-brands sets out the checks a buyer can run before committing to a program. One habit is worth adding on top of both: keep the retention tier inside the supply agreement rather than in a commissioning note, so the next site extension inherits the number the client actually signed off.
From a per-project minimum: white-label app, custom firmware, silkscreen or laser-engraved logo, market-specific documentation and packaging. Our export engineering team replies within one working day.
Key takeaways An FCC-recognized lab must hold the right scope for your device's rule part, not just any accreditation. A 2-bay NAS…
November 3, 2026Shared storage for deskside AI clusters refers to a storage appliance on the office LAN that holds datasets, checkpoints and embeddings for…
November 3, 2026A cloud storage subscription cost is the recurring fee a business pays to keep its files on a provider's servers, billed per…
Ask our export team for the OEM/ODM cooperation guide and a written quotation.
