Cloud-native multi-site video management using compatible existing cameras, gateways and sensors.
Product and system guidance
Arcules centralizes live/playback, search, sharing, health and administration without a VMS server at each site. A design still needs local gateway/edge recording, camera compatibility, upstream bandwidth, cloud retention, cybersecurity, subscriptions and outage behavior.
- Multi-site cloud organization, locations and roles
- Gateway/edge connectivity and existing camera reuse
- Cloud/edge retention, playback and evidence sharing
- MFA/SSO, device health, updates and subscription ownership
- Scene survey, pixels on target, lens and mounting
- Bandwidth, storage, retention and evidence export
- Firmware, cybersecurity, user roles and remote access
- Current regulatory, procurement and customer compliance requirements
Engineering before procurement
Boston High Tech validates current model availability, firmware, licenses, analytics, VMS compatibility and storage calculations. We do not publish private certificate numbers or named certificate-holder records; qualifications can be confirmed through appropriate private channels.
Request a video-system design review
Serving projects from our Charlotte headquarters and local client offices in Massachusetts, New York and New Jersey. Office visits are arranged in advance.
Official manufacturer references
How to compare and specify this product family
For Arcules Cloud Video Surveillance and VSaaS, the right model and architecture depend on the site, existing infrastructure and operating policy. A proposal should clearly document the following video-surveillance system decisions before equipment is ordered:
- Scene purpose and required pixels on target
- Lens, mounting height, WDR, IR and low-light needs
- Analytics supported by the selected camera and VMS
- Bandwidth, PoE and network segmentation
- Retention, storage throughput and export workflow
- User roles, cybersecurity, health monitoring and support
Installation, testing and handoff
Design starts with the evidence or operational result required at each scene—not megapixels alone. We document fields of view, identification targets, lighting, camera placement, network load, recording profiles and retention assumptions. Commissioning covers focus, exposure, time synchronization, analytics calibration, user permissions, mobile or remote access, export testing and health alerts. Final documentation records device names, locations, addressing, retention settings and administrator procedures without publishing private credentials.
Frequently asked questions
Buyers evaluating Arcules VSaaS raise these points about camera reuse, gateway recording, upload bandwidth and evidence sharing.
Does going cloud mean we can pull the recorder out of every closet?
Moving to the cloud removes the VMS server at each site, not the recording device. Arcules centralizes live and playback, search, sharing, health and administration, while local gateway or edge recording still lives at the location. How much that local device has to hold depends on the split you choose between cloud retention and what stays on site.
Which of our current cameras can move over without replacement?
Existing camera reuse turns on compatibility with the gateway and on what each model can stream, so the check happens camera by camera before a reuse list reaches the proposal. Boston High Tech validates current model availability, firmware and analytics support for each one, because a camera that connects is not automatically a camera whose analytics carry into the cloud.
How much upload bandwidth is this going to need?
The number is calculated rather than estimated: upstream bandwidth follows from camera count, stream settings and how much video the design sends to cloud retention instead of keeping on the local gateway. Storage calculations are done before procurement so the internet service at each site is sized to the design, and the figure lands in the proposal where later camera additions can be measured against it.
If a site loses its internet link, is that video gone?
Video availability during an outage depends on the outage behavior defined for your design, which is settled before procurement rather than while the link is down. Local gateway/edge recording is specified alongside cloud retention, and the design states what has to remain available at the site and how health alerting and search behave until connectivity returns.
How do we control who can log in and watch live video?
User roles are defined per location as part of the multi-site cloud organization, with MFA/SSO configured before accounts are handed out. Name who receives device health alerts and who owns the subscription in the same document, because an alert with no named recipient is an alert nobody acts on and a subscription with no owner lapses quietly.
An investigator asks for footage. What does that process look like?
Evidence sharing and export is a workflow the design writes down: who may export, what format leaves the system, where the exported file is held and how the release is recorded. Export gets tested before handoff along with playback and remote access, so a request during an incident is not the first time anyone tries the procedure.
Arcules owner, administrator and buyer resources
Discuss Arcules installation, maintenance or service
Detailed guides are maintained by 360TechnologyGroup.com, the parent-company knowledge center.
Official Arcules software, firmware and support
Official manufacturer resources. We link out rather than host firmware.
Before updating: confirm model, hardware revision, current version, entitlement and rollback plan, and schedule monitored or life-safety-adjacent systems with the administrator.