Skip to content
Gentex Ironvex
03 / Planned, not delivered

Roadmap

Everything on this page is planned, not delivered. Dates are an order of operations, not a commitment.

In progressactively being builtNextcommitted for that quarterPlannedintended, not startedExploringmay not happen

  1. Q3 2026 — Foundations

    In progress
    • Bench validation on real hardware.
    • Relay cold-boot testing before any relay drives anything real.
    • Live data replacing the simulated dashboard.
    • Field panel enrolment.

  2. Q4 2026 — Operable by someone else

    Next
    • Event history and audit trail.
    • Notifications on line fault, tamper and zone activity.
    • Time-of-day and day-of-week schedules.
    • Commissioning guide and site planner.
    • Board auto-detection in the flasher.

  3. Q1 2027 — Access control

    Planned
    • OSDP readers, with Wiegand as the legacy path.
    • Electric strikes, mag locks, request-to-exit, door position.
    • Credentials and a user directory.
    • Door-forced and door-held-open as first-class events.

  4. Q2 2027 — Video

    Planned
    • ONVIF discovery and RTSP snapshots on event.
    • Clips correlated to the zone that triggered them.
    • UniFi Protect and Synology Surveillance Station first.

  5. Q3 2027 — Server edition

    Exploring
    • A Linux head end on a small dedicated machine for larger sites.
    • Multiple users and roles, event history, reporting.
    • Setup performed on the device itself.
    • Field panels and the device protocol are unchanged.

  6. Q4 2027 — Integrations

    Exploring
    • MQTT and Home Assistant.
    • REST API and webhooks.
    • Central-station alarm monitoring.
    • Intercom and SIP.

  7. Undated — Purpose-built hardware

    Exploring
    • Gentex-designed boards with I/O, supervision and relay protection integrated.
    • One board per panel instead of three and a loom.
    • Development boards remain supported.

  8. Undated — Connected tier

    Exploring
    • Optional remote access without port forwarding or a VPN to configure.
    • Off-site backup of configuration and event history.
    • Push notifications, multi-site management and monitored alerting.
    • Subscription funded, never required.

The connected tier

Exploring

An optional connected tier is being explored. It would only add capabilities that are genuinely impossible on an isolated network — never unlock capability the hardware already has.

What it would add

  • Remote access without port forwarding or a VPN to configure. The head end would make an outbound connection; nothing inbound would be opened on the site network.
  • Off-site backup of configuration and event history, so a stolen or destroyed head end does not take the site records with it.
  • Push notifications to a phone that is not on the site network.
  • Multi-site management for someone maintaining many installations.
  • Monitored alerting, including handoff to a central monitoring station.
  • Firmware and update distribution without a site visit.

How it would be designed

  • The head end would initiate the connection. No inbound ports would be opened on the customer network.
  • The connection would be encrypted end to end.
  • Site credentials and the pre-shared key would stay on the hardware, not be uploaded.
  • It could be turned off, and the system would continue working exactly as it does now.
  • Nothing would be collected that the customer has not chosen to send.

These are design intentions for something that does not exist yet. No certification, audit, standard or security review has taken place, and none is claimed. There is no pricing, no launch date and nothing to sign up for.