Skip to content
Features

What Habile iEYE does

A video management system for organisations that run many IP cameras. It records them, shows live and recorded video in a browser, raises alerts, checks every camera is healthy and tells the right people when something needs attention.

Last updated

The Habile iEYE console's overview: cameras online, alerts today, availability over the last 24 hours, recordings kept, server uptime, cameras that need attention and recent alerts
The console's overview. Sample data: a fictional organisation, people and cameras. The AI counts appear in licensed installations only.

Cameras

Connect the IP cameras you already own, of any brand that speaks RTSP or ONVIF.

  • RTSP and ONVIF cameras, found by network discovery or added by address
  • Main stream and substream for every camera, with a choice of which to record and which to show
  • A stream test before saving: codec, picture size, frame rate and audio
  • Camera credentials encrypted at rest (AES-256-GCM) and never shown again in the console
  • Locations, bulk import and export, and copying one camera's settings to others
  • Camera states: named sets of camera modes applied at once, such as "Night: record everything"
The Cameras page: a list of cameras with their live status, recording mode, connection type (ONVIF, RTSP, browser or bridge) and location
Cameras of any brand, added over ONVIF or RTSP. Sample data: a fictional organisation, people and cameras.

Live video

Watch any camera in a browser with low delay, alone or in a grid.

  • Grids of 1 to 25 cameras, saved layouts, auto-rotate, full screen and snapshots
  • Video walls for control rooms and a map of where cameras are
  • Low-latency WebRTC, with an HLS fallback each organisation can switch on
  • H.265 cameras play everywhere: the player switches to the substream, or the server makes an H.264 copy while someone watches
  • Pan-tilt-zoom with presets, and two-way audio
  • Cameras that are not recording are pulled only while someone watches, so a recorder's session limit is not used up
An illustration of the live view, not a screenshot. Camera names are made up.

Recording

Record continuously or on a schedule, and decide per camera how long to keep it.

  • Continuous or scheduled recording, with retention set per camera
  • A recording quota for each organisation
  • Bookmarks, and protection so a recording outlives its retention
  • Storage on local disks, in an encrypted S3 bucket in your own account, or on any S3-compatible service
  • Recording the substream instead of the main stream, which cuts storage by about an order of magnitude
  • Every retention and storage-limit purge leaves an audit entry

Investigation

Find the moment, check it frame by frame, and hand over the clip.

  • A timeline across many cameras at once
  • Frame-accurate playback
  • Clip and ZIP exports, in H.264 by default so they open anywhere
  • Timelapse
  • One click from an alert to its footage

Alerts and notifications

Turn what your cameras detect into alerts that reach the right people.

  • The alarms your cameras raise over HTTP, e-mail, FTP and MQTT become alerts with a snapshot
  • Every alert says why it fired, and is acknowledged with a note
  • An alerts work queue and trends over time
  • Notifications by e-mail, webhook, Discord, Telegram, Pushover or MQTT
  • Rules by alert type, camera, time of day and cooldown, and each notification names the rule that sent it

Camera health

Know which cameras are down before someone needs their footage.

  • Online and recording state for every camera
  • Outages and availability per camera
  • Stopped and idle cameras listed with the reason, so they are not mistaken for faults
  • The server's own uptime
  • A daily health digest by e-mail
The Health page: cameras grouped as critical, warning, healthy and stopped, a banner naming the cameras that should be recording and are not, and a table with each fault, what happened and what to do
Camera health, with the reason for each fault and what to do about it. Sample data: a fictional organisation, people and cameras.

Access control

Give each person exactly the cameras and actions their job needs.

  • Administrator, operator and viewer roles, with permissions per camera
  • Access requests, and accounts that expire on a date
  • Two-step verification with an authenticator app or an e-mailed code
  • Single sign-on with OpenID Connect, SAML 2.0, LDAP or Kerberos
  • API keys with scopes, allowed addresses and an expiry
  • A limit on how many sessions an account keeps, chosen by each organisation
The Users & Access page: people with their role, status, camera access, two-step verification method and last sign-in
Roles, per-camera access and two-step verification for every person. Sample data: a fictional organisation, people and cameras.

Audit and accountability

Answer "who changed this" and "who watched that" from the record.

  • An audit trail of every privileged change, filterable and exportable as CSV
  • A log of who watched which camera, live or recorded, and for how long
  • Sessions that can be listed and ended
The Audit page's Viewing tab: who watched which camera, live or recorded, when, for how long and from which address
The viewing log: who watched which camera, for how long, from where. Sample data: a fictional organisation, people and cameras.

Many organisations, one installation

Run video for branches, sites or clients without them ever seeing each other.

  • Each organisation is separated by the database itself (PostgreSQL row-level security), not only by application code
  • An organisation sees only its own cameras, users, recordings and alerts
  • Per-organisation name, logo and accent colour, and its own quotas
  • A help centre inside the console with user, administrator and platform guides, and a first-visit tour
Who uses it

Four people, four jobs

The console gives each of them what their job needs and nothing else.

  • Security operator

    Watches live grids and video walls, reviews alerts, plays back and exports footage.

  • Viewer

    A manager, resident or auditor who watches the cameras they were given and reviews recordings and events.

  • Organisation administrator

    Adds cameras, users and permissions, schedules, notifications and branding.

  • Platform operator

    HabileLabs, a partner or your IT team: creates organisations, sets quotas and watches the servers.

Phone and desktop apps

Built, and not yet released

Today the console is a web application that works in a desktop or phone browser. Native apps are finished in code and in testing; we will not call them available until they are in the stores.

  • Phone apps for iOS and Android

    Alerts that reach you when the app is closed, live view, and the clip behind an alert. One app connects to any Habile iEYE console.

    Built, in pre-release testing. Not yet in the app stores.

  • Desktop app for Windows, macOS and Linux

    The console on several monitors, starting by itself, for control rooms.

    Built, in pre-release testing. Not yet published.

Honest limits

What to know before you rely on it

Proven on your equipment, during a pilot

These are implemented and tested against protocol simulators. Cameras and networks differ, so we validate them on your hardware before you depend on them.

  • Pan-tilt-zoom on your camera models over ONVIF
  • Footage sync from recorders (NVRs) that stay in place: Hikvision, Dahua and ONVIF Profile G
  • Kerberos sign-in against your domain
  • Federation between sites over your WAN
  • The AWS Marketplace edition is a single-instance appliance

    Recording pauses while the instance restarts or updates, for a few minutes. Above about 750 cameras, run more than one appliance or plan a multi-server deployment with us.

  • The AWS Marketplace appliance does no detection of its own yet

    As of version 4.4.0 its alerts come from the alarms your cameras raise. AI detection and the AI use cases run in licensed installations.

  • H.265 needs a browser that can decode it, or conversion

    Browsers without H.265 support play the substream in live view. From 4.3.0 an organisation can switch on H.264 conversion on the server for live view, recordings and exports.

  • Sizing is yours to get right, and we give you the numbers

    A 2 MP camera at 4 Mbit/s writes about 43 GiB a day. Camera counts per instance size are design targets, so leave headroom and watch the CPU alarm in the first week.

  • The console is in English

    The text is organised for translation, but no other language ships today.

Get started

See it on your own cameras

Start the free trial from AWS Marketplace and have a console in about six minutes, or book thirty minutes with a HabileLabs engineer to walk through the console and size a deployment for your cameras.

Or email support@habilelabs.io · Monday to Friday, 10:00–19:00 IST

  1. Subscribe on AWS Marketplace30 days with no software charge on one instance; AWS bills the instance and storage.
  2. Launch the stackPick a Region and a size. A working console in about six minutes.
  3. Add your camerasGive the stack a route to your site (a VPN, Direct Connect or a peered VPC) and add each camera by its address.