Frequently asked questions

No. Arisa runs entirely on your internal network and needs no Internet for any part of its operation: not for live view and recording, and not for AI analytics. Maps are served from your own local server too, so every capability remains available even on a fully isolated network. Remote access is possible, but only if you choose it and through your own secure infrastructure.

For a small deployment a server with a 4-core CPU, 8 GB of RAM and a disk with adequate sustained write throughput is enough. Real sizing depends on three factors: the number of cameras, the resolution and frame rate, and which analytics you plan to run. Recording pressures disk and bandwidth; AI analytics pressures CPU and, in heavy cases, the GPU. Retention length also drives storage. Before you buy, our specialists size the hardware based on your camera count and retention target so you neither run short nor overspend.

Licensing is modular and transparent. Camera capacity is purchased perpetually and stays yours; when a support term ends the system keeps running on its current version. Advanced capabilities such as AI analytics, SMS notifications and clustering are separate modules, so you only pay for what you actually use. Support and updates are annual and separate from the base licence. At any moment you can see how much capacity is consumed and which modules are active, so growing the system brings no hidden costs.

Yes, and this is one of the main differences between Arisa and closed systems. Every added capability is a standalone plugin, installed and enabled whenever you need it without bloating or destabilising the core. The SDK is multi-language: Python for AI and image processing work, Go for lightweight high-performance services, C# for teams already in that ecosystem, and other languages through standard interfaces. A plugin can register new events and actions in the rule engine and even ship its own UI page. Plugin packages are signed and install fully offline.

Yes. Arisa is an open platform and connects through several paths. The REST API exposes cameras, events and archive to external systems; webhooks push every important event to the target system instantly; and plugin actions let you build custom responses. Common integrations include access control for door release, relays and sirens on alarm, SMS through various gateways, and user authentication against your AD or LDAP. All of it happens inside your network with no dependency on an external service.

From a handful of cameras in a small office to several thousand in a large infrastructure. You start with a standalone master and add nodes whenever camera count or processing load grows. A smart scheduler spreads recording and analytics across nodes, and you can run that distribution automatically, semi-automatically or entirely manually. Importantly, adding a node happens without service downtime, so growth is not a risky project and can follow your annual budget.

In most cases yes. Rather than tying itself to one brand, Arisa builds on the open ONVIF and RTSP standards, which virtually every reputable brand supports. Your existing mixed-brand cameras can therefore be managed side by side in a single dashboard and your earlier investment is preserved. The system auto-discovers network cameras and adding them usually only requires their credentials. For very old or unusual models we test one unit before any bulk purchase to confirm full compatibility.

For a small site, installing the system and adding cameras usually takes a few hours, because auto-discovery removes most of the manual work. For larger projects the timeline depends on network readiness, the number of sites and the depth of integration with other systems. Our usual path is: requirements and design, installation and configuration, camera onboarding and tuning, rules and alarms, then operator and administrator training. Multi-site projects are typically phased so each stage is stable before the next begins.

Support is local and in Persian, so you never wait on a foreign reseller. More importantly, support requests are raised from inside the system itself, with no phone call or separate portal needed. During rollout we run practical training for two groups: operators who work in the monitoring workspace daily, and administrators who manage settings, users and reports. Persian documentation is handed to your team as well. Annual support contracts cover troubleshooting, version updates and advice as the system grows, and updates can be installed offline.

From inside the system itself. Arisa includes a ticketing section where a user can raise a subject and description without leaving their workspace, attaching a screenshot or file if needed. There is no separate portal to register with and no customer number to look up, because your organisation is identified automatically. Importantly, the technical context needed for diagnosis, such as system version, camera count and server resource status, is attached automatically, so the support engineer has a clear picture from the first message and repeated back-and-forth disappears. Every ticket has a clear status and can be tracked until it is closed.

The system is designed for exactly this. If a node becomes unreachable, Arisa detects it and moves that node's cameras to healthy nodes so recording and monitoring continue with minimal interruption. Once the node is back and stable, its cameras are handed back without disruption. Alongside this, the health of every server, disk and network device is monitored continuously and you are warned before a situation turns critical. Keeping storage separate from processing also stops one failure from taking the whole system down.

Yes. The whole Arisa interface is available in Persian with a right-to-left layout, from the monitoring workspace to settings and reports. An English interface is available too and each user can pick their preferred language. Dates and numbers are shown in familiar local formats. The system is fully web based and opens in the browser, so adding a new operator requires no installation on their machine.

You define retention yourself and it can differ per camera or camera group: entrance cameras for three months, indoor cameras for two weeks, for example. After that period the system automatically deletes the oldest footage so there is always room for new recording and recording never stops because a disk filled up. If storage approaches a warning threshold you are notified before it becomes critical. To save space, low-traffic cameras can use motion or event based recording instead of continuous.

Yes. Arisa is designed and developed from the ground up by an Iranian team and is a wholly domestic product. Contracting, invoicing and support are domestic, and for a purchase, a customization or any problem you deal directly with the people who build it - not a reseller and not a foreign company. The interface was designed for Persian-speaking users from the start rather than translated onto a foreign product.

No. Arisa runs entirely on your own infrastructure and needs no outside service or connection to work. On a completely closed network with no internet, live monitoring, recording, archive search, alarms and even the map work exactly the same way. Whether your organization keeps watching does not hinge on anything beyond it, and support remains available domestically and in Persian.