How an installation works

What Abriu is, who does what in an installation, and the path from start to finish with the time each step takes.

Abriu is the site's access control: face recognition terminals at the doors, a small hub (a Raspberry Pi) that talks to them, and a web panel the manager and the front desk use to register residents, visitors and service providers. This guide is for whoever installs and for partner companies. It is public: no login is needed and it can be sent to anyone.

The parts of the system

Part	What it is	Who looks after it
Terminals	Hikvision face readers at the doors, with card and PIN. They open the lock.	The installer mounts, powers and sets them up.
Hub (Raspberry Pi)	Stays at the site, on the same router as the terminals. Holds the data and syncs it to them.	The installer plugs it in; it installs itself.
Panel	`https://<site>.abriu.app`, used by the manager, the property manager and the front desk.	Abriu creates it; the manager gets the access.
Fleet	Abriu's remote follow-up: knows whether each hub is up and updates the system.	Abriu.
Camera recorder	Optional: the site's Hikvision DVR or NVR, registered on the panel. It opens no door; the system watches it (see Camera recorder).	The installer registers it, if the client wants.

People's data (photos, cards, fingerprints) stays on the hub, inside the site, encrypted. None of it passes through the installer or Abriu. See Privacy at the handover.

Who does what

Abriu registers the site in the fleet, creates the panel and hands the installer what the hub needs (an install code or a first-boot file). After the installation, it follows the hub from afar and gives remote support.
The installer supplies and installs the material (hub, terminals, locks, network), sets up the terminals, plugs in the hub and hands over to the manager with a door test.
The manager or the property manager is the panel's first administrator: gets an e-mail to create the password and, from there, registers people (or delegates it).

The path, start to finish

Request. The partner gives Abriu the site's data (see Requesting a site's registration). Abriu registers it and returns the panel's address and the install code or file. One business day.
Material. The installer buys or sets aside what is in Material. It can happen in parallel.
Network and terminals. At the site: terminals mounted, powered and with fixed IPs; hub wired to the router. See The site's network and Preparing the terminals. One to four hours, by the number of doors.
Hub. The card is written and the hub plugged in; it installs itself in 10 to 20 minutes. See Installing the hub.
Panel. The manager creates the password from the e-mail they get; the installer (or the manager) registers the terminals on the panel and makes a test record. Half an hour.
Handover. The Handover to the manager list, with the door test and what stays with the site.

When something does not go as expected, When something goes wrong lists what usually happens and what to do.

What the installer gets from Abriu

The panel's address: https://<id>.abriu.app. The <id> is the site's short name, chosen at registration.
The install code (XXXX-XXXX-XXXX-XXXX) or, simpler, the first-boot file (user-data, and network-config if the hub will use Wi-Fi). Both work once and for 14 days, and make the hub install itself. Treat them as a password: whoever has them installs a hub in the site's name.
The site's public status page, https://status.abriu.app/<id>, which shows whether the system is up.
Abriu's support contact for the installation day.

The installer gets no panel password and no access to the fleet: the panel belongs to the site and the fleet to Abriu's team. When the installer needs the panel during the handover, the manager creates a user for them (and can deactivate it afterwards).

Words used here

Word	What it is
Hub	The site's Raspberry Pi with Abriu's system. Also called the Pi.
Terminal	The face reader at the door.
Panel	The site's website where whoever enters is registered.
Fleet	Abriu's system that follows every hub.
Install code	The one-time code that makes the hub install itself.
First-boot file	The `user-data` written to the card, which carries the code and lets the hub install with no keyboard or screen.
Manager	Here, whoever answers for the site and receives the panel: the manager, the property manager or an appointed caretaker.