Parking Software

The architecture is hybrid. Central management can run in the cloud, and the full platform can also be deployed on-premise in a municipal data center. Critical data can stay on institutional servers, and data ownership remains with the municipality.

No. With the Edge Controller architecture, plate recognition, barrier control, and transition logs continue in offline mode. Accumulated records are synchronized automatically when connectivity returns.

Standard installations include at least 2 hours of UPS backup. For critical locations, 4-6+ hour capacities can be provided. Depending on load profile, optimized 3 kVA online UPS setups can support longer operation windows.

The platform supports daily incremental backups, weekly full backups, and instant snapshots. Backups can be stored in municipal infrastructure or Turkey-based data centers, with optional automatic transfer to the municipality IT unit.

Data in transit is protected with SSL/TLS, and data at rest is encrypted at AES-256 level. Access is restricted through role-based permissions and tracked with timestamped audit logs.

Stable operation has been validated in single-site scenarios with 10 active entry/exit barriers. On the central side, simulations and load tests were performed up to 10,000 parking facilities.

Barrier commands are processed at millisecond-level latency. Edge processing, queue management, and load balancing reduce central dependency during peak traffic, with support for at least 25 FPS processing.

With the right camera configuration, Turkish plates target accuracy above 99%. For foreign plates, results depend on the plate format and camera position.

Yes. IR-assisted night vision, anti-glare optics, and correct field positioning provide strong low-light performance. Optional dual-camera validation further reduces error rates.

Single-site scenarios with 100,000+ active vehicle records have been tested. The platform runs on clustered architecture; user limits are not hard-coded and scale with server resources.

Yes. Field transactions are stored in the local database, and debt/subscription/blacklist checks continue offline. Once connection is restored, data reconciliation runs automatically.

Yes. Migration is supported via CSV, Excel, or API. The process includes validation, duplicate detection, format standardization, and data cleansing.

Yes. The open protocol approach supports dry contact, RS485/TCP-IP, ONVIF, and RTSP-based integrations. A pre-install inventory analysis is performed and a compatibility report is prepared.

The commercial model is finalized contractually per project. A perpetual one-time licensing approach can be combined with maintenance/support coverage, while committed core updates are managed under the agreed scope.

Daily, monthly, yearly, and custom date-range reports are available with parking-lot and staff breakdowns. Cash, card, QR, mobile, and subscription collections are tracked separately and exported as PDF, Excel, or CSV.

REST API is the primary method. SOAP/web services and file-based integrations (JSON/XML/CSV) are also supported when required. Daily batch transfer, real-time transaction transfer, and bi-directional reconciliation can be implemented.

Entry-exit plate matching, manual barrier-open logs, camera-transaction matching, and suspicious transaction reports run together. Immutable logs provide full retrospective auditability.

Data ownership belongs to the relevant institution. Operations are designed for KVKK-aligned compliance processes, and retention rules are configured by policy and regulation. At end-of-retention, deletion/anonymization/destruction actions are logged.

For software incidents, 24/7 remote support is provided with priority handling for critical cases. The modular architecture enables stepwise expansion by adding parking sites, cameras, barriers, and server resources.