Residential communities
Automatic entry for residents, guests, couriers, and service providers.
How the system works
Vehicles gain access automatically
Where it is used
One solution for different types of sites
Offices and business centers
Access for employees, tenants, visitors, and company vehicles.
Parking facilities
Manage regular customers, subscriptions, and temporary permissions.
Warehouses and industrial sites
Control entry for employees, contractors, suppliers, and freight vehicles.
Hotels and resorts
Automatic guest access for the duration of their stay.
Property management companies
Centralized entry management across multiple sites.
Technical details
How the solution works internally
This is a complete access-control workflow rather than a standalone camera feature. Video acquisition, recognition, access rules, gate control, event storage, and external integrations work as one system.
License plate recognition
The video stream is received from an IP camera over RTSP using H.264 or H.265. Camera discovery and connection use the ONVIF standard.
The detector first finds a vehicle and the license-plate region. Recognition runs only when relevant content is present, so processing capacity is not wasted on empty frames.
A plate is confirmed across several consecutive frames. This suppresses false matches and prevents repeated opening commands during a single vehicle pass.
Entrance requirements
- Camera: 2 MP or higher, mechanical IR-cut filter, night illumination, and an exposure setting suitable for a moving vehicle.
- Position: the horizontal and vertical angle must keep the plate readable without severe perspective distortion; the complete plate must remain inside the recognition zone.
- Vehicle speed: up to 20 km/h inside the recognition zone — typical for approaching a gate or barrier.
- Network: the camera and controller require access to the site LAN, with static addresses or DHCP reservations.
Gate and barrier control
The gate opens through a dry-contact output connected to the drive controller’s standard control input. Existing automation does not need to be replaced.
Commands are delivered to the controller over MQTT. At startup, the device reports its model, firmware version, inputs, and outputs to the platform, reducing manual configuration when entrances are added.
Access decision logic
An access rule links vehicle plate + site + entrance + validity interval. One vehicle can hold several rules, such as permanent parking access and temporary loading-zone access.
- Was the license plate confirmed?
- Is there a rule for this entrance?
- Is the current time inside the permitted interval and schedule?
- Has the permission been revoked?
Only after every check succeeds does the platform send an opening command.
Roles and administration
Administrator permissions are separated by role: log viewing, temporary-pass issuance, permanent-list management, and administration of sites and users.
Administrative actions are audited. The history shows who issued or revoked a permission and when. Vehicle lists can be maintained manually, imported from a file, or synchronized through the REST API.
Data and reporting
Users, sites, entrances, and access rules are stored in a relational database. Entry events and site-load metrics are stored in an analytical database for reporting across arbitrary time periods.
Each event includes a vehicle frame and recognized plate. The log can be filtered by site, entrance, plate, date range, and verification result, then exported for reporting.
System architecture
From camera event to verified entry
The platform is the decision point between the physical entrance and systems that already manage customers, bookings, subscriptions, or employees.
External systemCRM, billing, bookingREST API: lists and permissions
Entrance cameraRTSP / ONVIFVehicle frames
GatePermit.pro platformRecognition and access verificationRules, schedules, roles, audit
Gate or barrierMQTT → dry contactOpening command
Entry logPhoto and resultWebhook to external system
External systems
Designed to become part of your infrastructure
Vehicle access does not have to become another isolated system. GatePermit.pro exchanges permissions and events with the software already used by the site.
REST API
Manage vehicle lists and access rules, issue or revoke permissions, and retrieve entry history.
Webhooks
Deliver entry events to external systems as soon as they occur.
File import and export
Load large vehicle lists in one operation and export reports for accounting or investigation.
Typical connections
CRM and accounting systems, parking billing and subscriptions, hotel booking systems, existing access-control and video-surveillance platforms, security and dispatch services.
Reliability and security
Access keeps working as part of the site’s security boundary
Encrypted communication
Platform communication uses protected channels. Every controller connects with its own credentials inside its organization’s topic namespace, isolating entrances belonging to different customers.
Buffered events
If the cloud connection is interrupted, events are buffered on the device and uploaded after connectivity returns, so the entry history is preserved.
Manual control remains available
Operators can open the entrance from the web dashboard or mobile application. Existing on-site opening methods continue to work in parallel with automatic plate access.
