Skip to content
Domi Gate
Menu

Features

Six modules on one platform. Each section says what the module does, what it does not do, and its status.

Domi Gate is finished software running on a test installation. The first pilot building is planned. Nothing on this site describes a building that already uses the product.

Video calls

Live video and two-way audio between the entrance and the resident's phone, over Wi-Fi or mobile data, relayed through the Domi Gate server.

What it does

  • Rings the resident’s phones over Wi-Fi or mobile data, woken by a push message, at home or anywhere else.
  • Shows the live video from the entrance as the call opens, with the resident’s microphone still off. Nothing is sent from the phone until the resident taps a button.
  • Four buttons: Audio to talk with the camera off, Video to talk and show the resident’s own camera, Open door to release the lock, End to finish. The resident’s camera is off unless they turn it on.
  • Open door asks the server for a single-use authorisation, which is logged. It works without answering the call.
  • Several phones per apartment ring. The first one to answer takes the call; the others stop ringing.
  • Works with the app in the background. During a call the app runs as a foreground call service so the phone does not pause it.
  • All media is relayed through the Domi Gate server. A phone is never connected directly to the entrance panel or to a stranger’s device.

What it does not do

  • It does not record calls. A call is live and leaves no recording.
  • It does not connect the phone and the panel to each other, and it does not open any port on the building’s network.
  • It does not run on iPhone yet. An iOS app is planned.
Image to follow The resident app during an incoming call, with live video from the entrance and the four buttons.

Access control

Secure cryptographic tags: in development

PINs with schedules and limits, NFC tags, and guest QR codes made by residents. All checked offline at the door.

What it does

  • PINs. Individual or shared codes with a validity period, a weekly schedule (overnight windows included), and a use limit. Five wrong entries lock the keypad for a minute, and the lock grows with every further attempt. A PIN is shown once when it is created and stored only as a one-way hash.
  • NFC tags. Press Open Door on the panel and hold the tag against the reader. Tags suit people without the app, such as children, cleaners or the post; service tags carry a label instead of a name. A tag is enrolled from the portal by holding it against an online panel.
  • Guest QR codes. A resident makes one in the app, names the guest, sets a time window and a number of entries, and shares the picture. The guest holds it up to the panel’s camera. The time window follows the clock at the entrance, the door counts the entries, and the code works when the internet is down. A resident or a manager can revoke it; it stops working within seconds.
  • Every credential is checked by the panel itself against an encrypted local copy, so the door opens even when the server or the connection is down.
  • Every opening and every refused attempt is written to the access log with the time, the door, the method and the person or label. The code itself is never logged.

What it does not do

  • A tag is matched by its number today, so it is exactly as secure as a key that can be copied. Tags with a secure chip are in development; until then, do not rely on tags alone for a high-security door.
  • A photo of a guest QR code opens the door like the code itself. Set a time or a number of entries, and delete the code when it is no longer needed. The app warns when a code has neither.
  • Nobody can read a PIN back, not even a manager. A forgotten PIN is replaced, not revealed.
Image to follow The entrance panel showing the PIN keypad with the entered digits masked as dots.

Missed-call clips

Nobody answered? The household can watch a short clip of who rang. Deleted if the call was answered.

What it does

  • When a call is not answered, cancelled or ignored, the residents of the apartment that was called find a short clip of the visitor in the app, with the walk-up before the ring.
  • Only that household can see it. This is enforced by the server, not just hidden in the app. Nobody in another apartment can see it.
  • The clip stays on the panel for about 48 hours. After someone in the household plays it for the first time, it can be replayed for 30 minutes. Then it is gone.
  • If the call was answered, or a resident saw the visitor and ended the preview, the clip is deleted at once.
  • The clip screen blocks screenshots and screen recording.

What it does not do

  • It does not keep footage. The clip is for seeing who came, not for building a video archive.
  • It does not record answered calls.
  • It is not visible to managers. A manager fetches motion clips through a separate, audited request.

Recordings

Motion at the entrance is recorded on the panel itself, encrypted, 48 hours rolling. Managers fetch a specific clip on demand.

What it does

  • Records a short clip when there is movement at the entrance, with about five seconds from before the movement began.
  • Keeps the clips encrypted on the panel for about 48 hours, with a cap on the space they may use. Older clips are deleted automatically.
  • Lets a manager request one specific clip. The panel uploads it, the manager watches or downloads it through a link that expires, and the server’s copy deletes itself.
  • Writes every step to the audit log: the request, the upload, the download and the deletion.
  • Works in the dark. The panel’s camera exposes for low light so a night clip shows the visitor.

What it does not do

  • It does not stream video to the cloud and it does not keep a permanent recording anywhere.
  • It does not show clips in the portal before a manager requests them.
  • It does not record calls. Live calls are never stored.
Image to follow The management portal listing the clips recorded by a panel, with a request button per clip.

Management portal

Data export and erasure: on request (portal buttons in development)

Buildings, apartments, residents, codes and tags, access log, alerts and device settings in one web portal.

What it does

  • Buildings and entrances. Apartments with their floor and the name shown on the panel. The name is optional; an apartment can show its number only.
  • Residents and invitations. A resident is invited with a one-time code shown once, as a QR card, a printed card or a message to paste. A lost code is re-issued and the old one stops working.
  • PINs, tags and guest codes. PINs with validity, schedule and use limit, replaced instead of revealed. Tags enrolled by holding them against an online panel. Guest QR codes made by residents, listed with every property, revocable one by one or all at once for a person.
  • Access log. Who opened which door when, and every refused attempt, by method: PIN, tag, QR code, phone, portal. Never the code itself.
  • Call history. Who was called, when, and whether it was answered.
  • Alerts. Pushed to the managers’ phones when critical: panel offline, door controller offline, enclosure tamper, panel overheating, a burst of refused attempts. Warnings in the portal: door held open, storage low.
  • Kill switches. Revoke a code, disable a person, retire a panel. Effective within one sync, which is seconds while the panel is online.
  • Device settings. The panel describes its own settings and the portal edits them, including the panel’s language.
  • Audit log. Every sensitive action, who did it and when.

What it does not do

  • Data export and erasure for a resident are handled on request today; the portal buttons are in development.
  • Invitation codes are handed over by the manager as a card, a QR code or a message. Email delivery is in development.
  • It does not show a PIN. A PIN is shown once when created, and then only replaced.
Image to follow The building page of the management portal with apartments, residents and their invitation status.

Door controller

Production board and enclosure: in development. Today: development board on our bench

A separately powered controller opens the lock. It accepts only authenticated, replay-protected commands from its paired panel.

What it does

  • Sits on the secured side of the door, on its own power supply, within Bluetooth range of the panel.
  • Switches a fail-secure electric strike: a pulse opens the door, about three seconds by default, and with no power the door stays locked.
  • Accepts only commands that are authenticated with the panel’s hardware key, encrypted and protected against replay. Keys are agreed fresh for every connection. A copied command does nothing.
  • Pairs with one panel, by pressing a button on the board. A different board, or a board that no longer trusts the panel, is reported to the manager.
  • Reads a door-position contact and an enclosure-tamper contact and reports them to the panel. The manager is alerted when the enclosure is opened and when the door stays open too long.
  • Proves the link to the panel every 15 seconds. If it stops answering, the manager is alerted within about a minute, and until the link is back nothing opens the door.

What it does not do

  • It does not open the door on its own, on a timer or on a network command. Only the paired panel can ask it to.
  • The exit button and the fire input have terminals on the board but are not active in the current firmware.
  • On our bench the controller drives a test light, not a strike. The production board and the enclosure are in development.
Fire alarm and emergency-egress functionality must not depend only on BLE, Android or normal application software.
Image to follow The development bench with the entrance panel, the door controller board and a power supply.

Want to see it work?

We show a live call, the door controller and the management portal, online or in Skopje.

Pricing on request.