Is Smart Parking cloud-hosted or on-premise?

On-premise by design. The web app, database, real-time monitoring service, and licensing all run on a single Linux box (or HA pair) inside the operator's perimeter. Kiosks talk to it over the operator-controlled LAN. Operators retain physical control of their data, their licence, and their hardware. Internet outages do not stop the gate from opening.

How does the RFID card lifecycle work?

A card has a unique card number, an optional unique vehicle plate, a car size (small / medium / large), an assigned pricing profile, a current balance, and an optional linked customer. Staff issues the card at the counter with an initial top-up. Every top-up, parking fee, refund, or balance transfer is recorded as a transaction with the post-transaction balance snapshot — the ledger reconstructs itself even if the cached balance is ever corrupted. Lost cards are flagged and replaced; transfers move balance between cards atomically.

How does pricing work — a fixed fee or by duration?

Both — it is the operator's choice. Each pricing profile uses one of two models: a fixed fee at exit (a flat charge per car size, deducted the moment the card taps the exit reader) or duration-based (the fee is calculated from the time parked, at a rate that can vary by car size). Because the model is set per pricing profile, a single site can run both at once — for example a flat fee for staff and resident cards and a duration-based charge for visitors. Either way the kiosk calculates the fee instantly, deducts it, writes the parking-fee transaction, records the parking session, and opens the gate — leave-time stays fast and the charge is shown on screen, so there is nothing to dispute.

What auth model does the system use?

Three auth paths. Admin and staff sign in with email and password (hashed credentials) and receive a session token with a configurable lifetime. Device authentication: every kiosk identifies itself on each request, and that identity is checked against the registered, approved device list — a kiosk that is not approved is refused. Kiosk-only operations such as the leave flow require both staff authentication and an approved device. The deployment perimeter is the operator's LAN, with device approval layered on top.

Is the admin / staff / customer UI multilingual?

The product ships RTL Arabic + LTR English as the production baseline. Customer-facing surfaces, admin and staff console all support full bilingual operation, with the i18n layer structured so that adding French, Spanish, German, Portuguese, Italian, Dutch, Turkish, Urdu, Hindi or any other language is a localised addition rather than a rewrite. For a global enterprise deployment we ship in the operator's preferred language(s) — single-language, multilingual, or trilingual setups are all well-supported.

Which currency and phone format does it use?

Currency and phone format are configuration knobs at deployment time — standard locale formatting handles the currency wiring, and a country-specific rule validates phone numbers. Switching between GBP + UK phone, EUR + DE/FR/IT phone, USD + US phone, AED + UAE phone, SAR + Saudi phone (and any other) is a small config change, not a code change.

How do you prevent cash-handling losses and fraud?

Every balance change writes a transaction with the post-transaction balance snapshot. The ledger reconstructs the balance independently of the cached column — discrepancies are detectable. Staff and admin actions are tied to authenticated users with timestamped sessions. Card top-ups happen at the counter or at staff-attended kiosks, not in cash drop boxes. For high-stakes deployments we recommend pairing with the GLARUS Visitor Management System for staff identity tracking and the Customer Feedback System for transparent dispute resolution.

What happens when a card is lost?

Staff marks the card as lost via the card-management console. The old card stops working immediately (validated server-side, not by the kiosk's local cache). A new card is issued with a fresh card number; the customer's remaining balance is transferred from the lost card to the new card as a paired, atomic transfer. Both events are auditable. The old card record remains for compliance — it is flagged, not deleted.

Can the customer portal be used without an account?

Yes — the customer surface is intentionally no-login. A customer enters their card number on the customer portal and sees their balance, recent activity, and a card-tap leave-flow shortcut. This is by design: the customer's identity is the physical card, not a username/password. Reduces password-reset support volume to zero and removes a credential-theft attack surface.

How long does deployment take?

A typical single-site deployment takes 2 weeks: 2-3 days infrastructure (Linux server and supporting software, license issuance), 3-4 days site survey + kiosk install + barrier wiring + network configuration, 2-3 days pricing-profile setup + staff/admin user provisioning + initial card batch issuance, 2-3 days staff training + pilot operation + handover. Multi-site rollouts scale linearly per site; the license, codebase, and operations playbook are identical.

How does it scale to large operators?

Single-site deployments run comfortably on a modest 4-core Linux server, supporting tens of thousands of cards and hundreds of kiosks. For very large operators (city-scale public parking, airport groups, university networks with 50+ sites), we deploy a regional cluster: a clustered database tier, a scaled-out real-time layer for cross-instance event fan-out, license issuance per site, and aggregated reporting at the operator HQ via CSV / API export.

Does it integrate with payment gateways for the customer portal?

Top-ups today are staff-attended (cash, card, bank transfer at the counter). Online top-ups via the customer portal — integration with regional payment gateways (Stripe and other major card processors in the UK and EU, regional card processors and domestic mobile-money elsewhere) — are a standard add-on for operators who need them. The transaction ledger is gateway-agnostic; the integration sits in front of the top-up step, so no change is needed to the ledger itself.

Is it GDPR / PDPL compliant?

The architecture is designed for compliance with GDPR (EU / UK), PDPL (Saudi Arabia / UAE / GCC), and any equivalent national data-protection framework. On-premise deployment means customer data never leaves the operator's perimeter. The transaction ledger is append-only and auditable. PII captured is minimal — name, phone, car plate — and is straightforward to anonymize for right-to-be-forgotten requests. Production deployments are hardened to the operator's security policy — hashed credentials, hardware-backed signing keys, strengthened session tokens, mutual TLS for kiosk-to-server traffic, encryption at rest, and audit-log retention windows per the operator's legal requirements.

Smart Parking Solution

Smart Parking Management System

On-prem RFID smart parking — cash-free barrier gates, prepaid card lifecycle, real-time visibility and an Android kiosk fleet you fully control.

Request a demo Calculate ROI

One platform · 12 solutions · 6+ countries direct + via partners

GLARUS Core

Overview

Comprehensive Smart Parking

Zeour Smart Parking — a complete on-premise smart parking platform: RFID card lifecycle (issue, top-up, transfer, lost replacement, card-tap exit), staff card-management console, admin operations center with pricing profiles per car size, no-login customer self-service portal, real-time monitoring (live activity, transactions, alerts), an Android kiosk fleet that drives RFID card readers and barrier gates directly with a hardware watchdog, and offline-validated sovereign licensing that ties each deployment to the operator's own server. Single-tenant deployment on the operator's own infrastructure; ships engineered multilingual with full RTL as a production baseline — configurable for any locale and currency per engagement.

Replace ticket printers and gate operators with RFID cards + barrier kiosks — day-one labor savings on every shift

Cut leave-time at the gate to under 5 seconds — the kiosk calculates the fee (fixed or duration-based), deducts it, opens the barrier, and logs the session

Eliminate cash-handling losses with prepaid top-ups — every transaction flows through the audited ledger

Run entirely on-premise on the operator's LAN — no SaaS dependency, no internet outage takes the gate down

Smart Parking Management System — Overview

Smart Parking customer journey overview — issue card → drive in → top up → card-tap leave → operator audits in realtime — Customer journey: issue card → drive in → top up → card-tap leave → audit.

Deep Dive

Understanding Smart Parking — Built for Sovereignty-Sensitive Operators, Designed to Travel

The Zeour Smart Parking System has two parts: an on-premise web platform (admin, staff, and customer surfaces, the REST API, and the real-time monitoring service) and an Android kiosk app that drives RFID card readers and barrier gates directly. The web platform and kiosk app are deployed together. Offline-validated licensing, device approval for every kiosk, full RTL support, configurable currency, and configurable phone validation are first-class — every one of those is a configuration knob, not a hardcode. The system is engineered for operators worldwide who run their own infrastructure — UK, EU, Americas, GCC, MENA, Africa, Asia.

Key Functionalities

Deep dive of Smart Parking modules — admin operations center, staff console, customer portal, kiosk fleet, realtime monitor

Three Role Surfaces, One Codebase

The web app delivers three distinct UX surfaces: Admin (operations center, dashboard, transactions, pricing, system health, realtime monitor), Staff (card-management console — issue, top-up, leave, lost), and Customer (no-login balance check + card-tap leave). Each surface authenticates differently and only sees what it should.

RFID Card Lifecycle

Cards are the unit of customer identity. Each has a unique card number, an optional unique vehicle plate, a car size (small / medium / large), an assigned pricing profile, a current balance, and an optional linked customer. Full lifecycle: issue, top-up, transfer balance, mark lost + replace, deactivate.

Flexible Pricing Profiles

Pricing is built around per-customer pricing profiles. Each profile uses one of two models — a fixed fee at exit (a flat charge per car size) or a duration-based charge calculated from the time parked — and a simple flat-rate plan is available alongside for operators who want it. New cards are issued against a pricing profile. At the exit gate the kiosk reads the profile, calculates the right fee for that card, and proceeds.

Transaction Ledger (Append-Only, Auditable)

Every balance change creates a transaction record — top-up, parking fee, refund, or balance transfer — with the post-transaction balance snapshot. The ledger reconstructs the balance independently of the cached column, so discrepancies are detectable and reportable.

Parking-Session Audit Trail

Every leave creates a parking-session record capturing the fee charged and the pricing model used. Sessions are auditable by card, by date range, by staff member who processed the leave, and by the kiosk that handled the gate.

Customer Self-Service Portal (No Login)

The public customer portal lets a customer enter their card number and see balance, recent activity, and a card-tap leave shortcut. By design, the customer's identity is the card — no username, no password, no credential-theft surface. Reduces support volume dramatically.

Real-Time Monitoring Service

A standalone monitoring service fans out live activity (each card action), real-time stats, recent transactions, recent cards, running totals, and parking alerts to the admin's Realtime Monitor. Events are emitted from the API on every balance change.

Android Kiosk Fleet with Device Approval

Each Android kiosk has a unique device identity. On first boot it self-registers with the operations center. An admin reviews the request and approves (or rejects) it. Only approved devices are allowed to run kiosk-only operations. Every kiosk request carries its identity and updates its last-seen timestamp.

Kiosk Drives the Hardware Directly

The kiosk drives the RFID card reader and the barrier gate directly — there is no third-party middleware in the loop. It also feeds a hardware watchdog at fixed intervals, so a hung kiosk recovers itself automatically without an on-site visit.

Offline-Validated Licensing

Each deployment is governed by an offline-validated licence tied to the operator's own server. The licence validates entirely on-premise — no phone-home, no SaaS dependency, no internet connection required. If the licence is invalid or expired, the application fails closed, locking down with a branded notice instead of serving the page.

Software Components

Web Platform

Web Application + REST API

Server-rendered admin, staff, and customer surfaces plus a full REST API. Packaged as a lightweight single-binary deployment.

Structured Data Model

Customers, cards, transactions, pricing plans and profiles, parking sessions, admin and staff users, and device registrations — a single-tenant database per site.

Lightweight Runtime

Runs on a modern, lightweight web stack with a polished component layer. RTL is enforced at the document root for Arabic-baseline deployments.

Reverse Proxy

A reverse proxy fronts the application and routes traffic to the web app and the monitoring service through one hostname.

Auth & Licensing

Admin + Staff Authentication

Email-and-password sign-in with hashed credentials; each session token has a configurable lifetime. Every protected route validates the session and short-circuits on failure.

Device (Kiosk) Authentication

Every kiosk request carries its device identity, checked against the approved device list and rejected if missing or not approved. It composes with staff authentication on kiosk-only operations such as the leave flow.

Offline-Validated Licensing

An offline-validated licence ties each deployment to the operator's own server. It validates entirely on-premise with no phone-home. If the licence is invalid or expired, the application fails closed — it locks down with a branded notice instead of serving the page.

Realtime & Integration

Real-Time Monitoring Service

A standalone monitoring service that fans out live activity, real-time stats, recent transactions, recent cards, running totals, and parking alerts to the admin Realtime Monitor.

REST API

A full REST API covering authentication, the card lifecycle (issue, top-up, leave, lost), card lookup, the admin operations center (dashboard, transactions, activity, analytics, system health, cards, staff and admin users, devices, pricing), and device registration. Every protected route uses the auth model described above.

Payment Gateway Hook Points

The transaction ledger is gateway-agnostic. Plugging in a regional payment gateway is a per-deployment integration that sits in front of the top-up transaction step. Reference implementations are available.

Android Kiosk

Single-Purpose Kiosk App

A purpose-built Android kiosk app, landscape-locked and RTL-capable, with the system UI hidden so the panel does one job and one job only.

On-Device Persistence

Server host and hardware settings persist on the device, surviving reboots and over-the-air updates.

API Client

The kiosk calls the web platform over the operator LAN, carrying its device identity on every request, for card balance lookups, the leave flow, and device registration and status.

Direct Hardware Control

The kiosk drives the RFID card reader and the barrier gate directly — no third-party middleware — and feeds a hardware watchdog at fixed intervals so a hung panel recovers itself.

Hardware Diagnostics Screen

A built-in diagnostics view accessible from the kiosk header. It tests the card reader, the barrier-gate output, and the watchdog so an installer can verify a lane in seconds.

Hardware Components

Server (Operator Site)

Industrial Branch Server

A compact industrial Linux server that comfortably hosts the full Smart Parking platform for a single site (tens of thousands of cards, hundreds of kiosks).

Standard Linux Server

Any x86 server with 8+ GB RAM and SSD storage. For large sites we deploy an HA pair behind a load balancer.

Kiosk Hardware

Standard Android Kiosk Panel

The kiosk app runs on standard Android kiosk panels with hardware-watchdog support — operators can source panels from their preferred vendor.

RFID Card Reader

A standard RFID card reader, driven by the kiosk directly with no third-party middleware in the loop.

Barrier-Gate Output

A relay-controlled output that drives the barrier gate, triggered by the kiosk on every successful card-tap-to-leave.

Hardware Watchdog

A hardware watchdog the kiosk app feeds at fixed intervals. If the app hangs, the watchdog reboots the panel automatically — no on-site visit required.

Barrier & Lane Hardware

Electric Barrier Gate

Any standard electric barrier gate with a relay-controlled "open" input works. Wiring is straightforward: the kiosk triggers the relay, and the relay opens the barrier motor.

Vehicle Loop Detector

Optional but recommended: ground-loop or radar-based vehicle detector at each lane to prevent gate-close-on-vehicle accidents.

Loop-Triggered Safety Camera (Optional)

For high-value sites we recommend a per-lane ANPR camera as a secondary identity factor; integrates with our Visitor Management System for cross-checked entry / exit logs.

Customer Cards

EM4100 / EM4200 RFID Cards

Standard 125 kHz EM4100 / EM4200 RFID cards (printable). The card number is the customer's primary identifier.

MIFARE Classic / DESFire Cards (Optional)

For higher-security deployments we support MIFARE Classic and MIFARE DESFire cards on a compatible reader. Adds cryptographic challenge-response on top of the existing card-number identity.

Operator Workstations

Reception Workstation

Standard PC with 22"+ touchscreen for staff card issuance + top-up + leave processing.

Admin / Operations Workstation

Standard PC with a 24"+ display showing the operations center: dashboard, transactions, realtime monitor, system health, pricing profiles, staff CRUD.

Thermal Receipt Printer (Optional)

For top-up receipts and leave-fee receipts. 60mm or 80mm thermal printer with USB or LAN.

Smart Parking Three-Tier Architecture

A clean three-tier architecture: Android kiosks at the edge talk to the on-prem web platform over the operator's LAN; the web platform fans out real-time events to the admin's operations center; the licence validates offline. Single-tenant deployment per site, with optional regional clustering for very large operators.

01Architecture Tier

Tier 1 — Edge Devices

Android Kiosks · RFID Card Readers · Barrier Gates

Single-purpose Android kiosk app (landscape-locked, RTL-capable)
Device self-registration on first boot; admin approval to come online
The kiosk drives the RFID card reader and the barrier gate directly — no third-party middleware
Standard RFID card readers
Relay-controlled barrier-gate output
Hardware watchdog fed at fixed intervals
LAN-operated (operator-controlled network, no public exposure)

02Architecture Tier

Tier 2 — On-Prem Web Platform

The web platform, database, and licensing

A full REST API covering admin, staff, customer, device, and kiosk surfaces
Resource coverage spans cards, customers, transactions, pricing profiles, staff, admin users, devices, system health, and analytics
Three role surfaces in the same codebase: admin, staff, and a no-login customer portal
Structured data model: customers, cards, transactions, pricing plans and profiles, parking sessions, admin and staff users, device registrations
A lightweight runtime for the web server and the real-time monitoring service
A reverse proxy fronting the platform
Offline-validated sovereign licensing, tied to the operator's own server

03Architecture Tier

Tier 3 — Operations, Realtime & Integration

Realtime Monitor · WebSocket Events · Integrations

Realtime Monitor view in the admin operations center
Live events: activity, stats, recent transactions, recent cards, running totals, parking alerts
Optional payment-gateway integration sitting in front of the top-up transaction step
Optional ANPR camera integration per lane as a secondary identity factor
CSV / API export for accounting + BI ingestion at the operator HQ
Cross-site aggregation (a scaled-out real-time layer and a clustered database tier) for city-scale operators
Offline operation by design — internet outages do not stop the gate

Tier 1 — Edge Devices

Android Kiosks · RFID Card Readers · Barrier Gates

Single-purpose Android kiosk app (landscape-locked, RTL-capable)
Device self-registration on first boot; admin approval to come online
The kiosk drives the RFID card reader and the barrier gate directly — no third-party middleware
Standard RFID card readers
Relay-controlled barrier-gate output
Hardware watchdog fed at fixed intervals
LAN-operated (operator-controlled network, no public exposure)

Tier 2 — On-Prem Web Platform

The web platform, database, and licensing

A full REST API covering admin, staff, customer, device, and kiosk surfaces
Resource coverage spans cards, customers, transactions, pricing profiles, staff, admin users, devices, system health, and analytics
Three role surfaces in the same codebase: admin, staff, and a no-login customer portal
Structured data model: customers, cards, transactions, pricing plans and profiles, parking sessions, admin and staff users, device registrations
A lightweight runtime for the web server and the real-time monitoring service
A reverse proxy fronting the platform
Offline-validated sovereign licensing, tied to the operator's own server

Tier 3 — Operations, Realtime & Integration

Realtime Monitor · WebSocket Events · Integrations

Realtime Monitor view in the admin operations center
Live events: activity, stats, recent transactions, recent cards, running totals, parking alerts
Optional payment-gateway integration sitting in front of the top-up transaction step
Optional ANPR camera integration per lane as a secondary identity factor
CSV / API export for accounting + BI ingestion at the operator HQ
Cross-site aggregation (a scaled-out real-time layer and a clustered database tier) for city-scale operators
Offline operation by design — internet outages do not stop the gate

Operational & Resilience Pipeline

Real-time

Realtime activity / stats / alerts (degrades gracefully if the service is down)
Token-based admin + staff auth (configurable session lifetime); device auth via per-kiosk registration and approval
Append-only transaction ledger reconstructs the balance independently of the cached column
Daily database backups to local NAS / object storage; recovery in minutes, recovery point matching backup cadence
Offline-validated licensing tied to the operator's own server — physical theft of the database file alone cannot run the system elsewhere
Watchdog-fed kiosks auto-reboot on hangs; driving the hardware directly removes third-party middleware as a failure mode

Smart Parking vs Ticket Printers vs SaaS Parking Platforms vs Generic Open-Source

Most parking operators sit at one of three extremes today: tickets-and-cash at the gate (high labor, high shrinkage), SaaS cloud platforms (offshore data, monthly subscription), or open-source projects (DIY, no kiosk path). Zeour Smart Parking sits where serious operators actually need to be: on-premise, RFID-card-based, with flexible pricing, a kiosk fleet, and a realtime monitor.

Zeour Smart Parking

Best for: Operators of malls, hospitals, office towers, government compounds, universities, and city-scale public parking who need on-premise control, RFID lifecycle, multi-kiosk fleet management, and live operations visibility.

Comparison

On-premise default — customer data stays on your server
RFID card lifecycle with an append-only transaction ledger
Three role surfaces (admin / staff / customer) in one codebase
Android kiosk fleet with device registration + admin approval; the kiosk drives the hardware directly
Multilingual with full RTL as a production baseline; configurable currency; re-localizable to any market in days
Built-in realtime operations monitor
Offline-validated sovereign licensing tied to the operator's own server
Two pricing models — fixed fee at exit or duration-based — calculated automatically and shown on screen

Zeour Smart Parkingon-premise parking systemRFID parking platformparking kiosk fleet

Ticket Printer + Cash at the Gate (Legacy)

Best for: Operators who haven't modernized yet — and are paying for it daily.

Comparison

Ticket-stock cost on every entry
Cash-handling shrinkage at the gate (industry average 3-7%)
High labor cost (24/7 gate operators)
No realtime visibility into operations
Manual end-of-shift reconciliation
No customer self-service

ticket-based parkingcash gate parkinglegacy parking system replacement

SaaS Parking Platforms (US / EU Cloud)

Best for: Operators with US / EU operations and no data-residency concerns.

Comparison

Cloud-hosted in US / EU data centers
Monthly subscription per kiosk + per transaction
No control over your own data
Limited support for RTL languages or configurable currency formatting
Internet outage takes the gate down
Generic hardware path; not engineered to drive the kiosk and barrier gate directly

SaaS parking alternativecloud parking alternativedata sovereignty parking

Generic Open-Source Parking

Best for: Technically self-sufficient operators with strong in-house engineering and patience for DIY.

Comparison

Free to license
No kiosk app — operators build their own or skip kiosks
No hardware controller — no built-in way to drive card readers and barrier gates
No realtime monitor; no device registration or approval workflow
Community support; commercial support requires a partner
Operational burden of running production yourself

open-source parking alternativeparking platform DIY commercial alternative

Smart Parking — Deployment Checklist

A practical 5-phase rollout for going live with Zeour Smart Parking at a single site, then scaling across sites. Use this as the project plan with your Zeour partner.

1) Site Survey & Server Setup

Checklist

Inventory lanes, barrier gates, kiosk locations, network drops, power, lighting

Confirm the RFID card readers and barrier gates per lane and verify kiosk compatibility

Provision the Linux server (an industrial branch server or equivalent) with the platform and its database

Issue the offline-validated licence, tied to the operator's own server

Configure currency, phone format, language, locale direction (RTL / LTR) for the operator's market

2) Database Schema + Pricing + Users

Checklist

Initialise the database schema; create the first admin and staff users

Define pricing profiles — pick the fixed-fee or duration-based model per profile and set rates per car size; a simple flat-rate plan is available alongside

Provision admin users + staff users; review role-based access and session lifetimes

Harden the deployment per your security policy before going live

Decide payment-gateway integration (Stripe, regional card processors, domestic mobile-money) — if any

3) Kiosk Installation + Device Approval

Checklist

Mount kiosks at each lane; wire the barrier-gate relay and connect the RFID card readers

Install the Android kiosk app; on first boot, each kiosk self-registers with the operations center

Admin reviews each device in the operations center and approves (or rejects) it

Test the card-tap-to-leave flow per lane: card validates → fee deducts → parking session logs → gate opens

Run the built-in hardware diagnostics screen on each kiosk to verify the lane

4) Pilot + Training

Checklist

Train reception staff on card issuance + top-up + leave processing + customer lookup

Train operations admin on dashboard + transactions + realtime monitor + pricing-profile management + system health

Pilot with internal staff cards for 3-5 days; sit-by with reception during the first shifts

Issue customer cards in batches (start with mall employees, residents, weekly visitors, etc.)

Track KPIs: avg leave time, transaction error rate, kiosk uptime, NPS at the counter

5) Live Operations + Scale

Checklist

Configure scheduled database backups + licence backups to off-site storage

Wire monitoring (uptime, disk space, kiosk last-seen status, transaction throughput, watchdog reboots)

Enable customer self-service portal at the lobby + on customer phones

Roll out to additional lanes / additional sites; aggregate reporting at the operator HQ via CSV / API export

Plan for peak periods (holidays, exams, major events) — pre-provision card stock and pricing-profile changes

Smart Parking Management Gallery

Visual highlights of Zeour Smart Parking — RFID lifecycle, kiosk fleet, real-time monitoring, and on-prem licensing.

Smart Parking admin dashboard with today's transactions, cards in circulation, kiosk fleet status, realtime monitor — Admin dashboard — transactions, fleet, KPIs, realtime activity.

Staff card issuance — multilingual record, car size, pricing profile.

Smart Parking Android kiosk at the exit lane with card-tap UI, balance shown, fee deducted, barrier opening — Exit kiosk — card tap, fee deducted, barrier opens in under 5 seconds.

Smart Parking real-time monitor showing live activity, recent transactions, parking alerts, kiosk health — Real-time monitor — live activity, transactions, alerts.

Smart Parking three-tier architecture — kiosks, on-prem web platform, operations and realtime layer — Three-tier architecture: kiosks → on-prem web platform → operations layer.

Problem vs Solution

Why Ticket-and-Cash Parking Fails

Ticket-and-cash gates are slow, leak revenue, and need staffing every shift — here is why an RFID smart parking system is essential.

Why ticket-and-cash gates, SaaS parking platforms, proprietary locked-in hardware, and open-source DIY fall short for serious parking operators — Why ticket-and-cash, SaaS parking, and proprietary locked-in hardware fall short.

The Problem01

Ticket Printers Are a Cash-Handling Liability

Traditional ticket-on-entry + cash-on-exit operations bleed money in three ways: ticket-stock cost, cash-handling shrinkage at the gate, and gate-operator labor 24/7. Reconciliation at end-of-shift is manual and error-prone.

The Zeour Approach

Prepaid RFID Cards Eliminate Cash at the Gate

Customers pay at the staff counter, balance lives on the card, the gate is cash-free. Every transaction flows through the audited ledger with post-transaction snapshots. Cash shrinkage at the gate goes to zero overnight.

The Problem02

SaaS Parking Platforms Send Your Data Offshore

Most commercial parking platforms are SaaS-only and host transactions, customer PII, and card data in a foreign cloud. For sovereignty-sensitive operators worldwide that's legally and operationally problematic — data residency rules and intermittent international links make it untenable.

The Zeour Approach

On-Premise Default = Data Stays in the Country

The entire platform — web app, database, monitoring service, and licensing — runs on the operator's own server inside their perimeter. Data residency is a deployment decision, not a vendor decision.

The Problem03

Proprietary Gate Hardware Locks Operators In

Many barrier-gate vendors ship closed, bundled software with their hardware. That forces operators into a single vendor's ecosystem — switching to better software, or fixing a hardware bug, means waiting on that vendor for every fix or change.

The Zeour Approach

The Kiosk Owns the Hardware Path End to End

The kiosk app drives the RFID card reader and the barrier gate directly — there is no proprietary middleware in the loop. The operator owns the hardware path end to end and is never waiting on a third-party vendor to ship a fix.

The Problem04

Generic Domestic Solutions Are Underbuilt

Many domestic parking operators worldwide still run on spreadsheets + a barrier-gate relay + a cash drawer. Operations don't scale, audits are impossible, lost cards are a constant battle, and cash leakage is endemic.

The Zeour Approach

Sovereign-First, Audited Like an Enterprise

RTL Arabic + LTR English baseline, configurable currency, configurable phone validation — with the operations discipline of an enterprise SaaS: full Transaction ledger, append-only audit trail, role-based auth, realtime monitor, kiosk fleet management. Operators get both.

The Problem05

Manual Fee Calculation Slows the Gate

When a gate operator keys in the fee by hand — or a customer argues the minutes on a printed ticket — every exit turns into a negotiation. The lane backs up, shifts run long, and end-of-shift reconciliation never quite ties out.

The Zeour Approach

Automated Pricing the Customer Can See

The kiosk calculates the charge the instant the card taps — a flat fee per car size or a duration-based rate, whichever the pricing profile uses — deducts it, and shows it on screen. Nothing is keyed in by hand, the fee is transparent, and the gate opens in under 5 seconds.

The Problem06

No Realtime Visibility = No Operations Discipline

Without live dashboards, operators discover hardware failures hours after they happen, find out about cash-handling anomalies at end-of-day reconciliation, and have no visibility into per-staff or per-kiosk performance.

The Zeour Approach

Realtime Monitor = Operations Discipline by Default

The admin's realtime monitor surfaces every card action, every transaction, every system-health change in seconds. Hardware fault on Kiosk #4? You see it instantly. Unusual top-up pattern? You see it instantly.

Features

Smart Parking Features

Discover the powerful features that make our smart parking the preferred choice for enterprises worldwide.

Key features of Smart Parking — RFID lifecycle, per-car-size pricing, realtime monitor, Android kiosk fleet, offline-validated licensing — Feature highlights — RFID, fleet, realtime, sovereign licensing.

RFID Card Lifecycle — Issue, Top-Up, Transfer, Mark Lost, Replace

Staff Card-Management Console (issue at counter, top up, process leave, look up by card or vehicle plate)

Admin Operations Center — Dashboard, Transactions, Staff, Devices, Pricing Profiles, System Health, Realtime Monitor

Customer Self-Service Portal — No Login (balance check + card-tap leave flow)

Two Pricing Models per Profile — Fixed Fee at Exit or Duration-Based

Per-Car-Size Pricing Profiles (small / medium / large) Assigned per Card; Simple Flat-Rate Plan Available

Append-Only Transaction Ledger with Post-Transaction Balance Snapshots (top-ups, parking fees, refunds, transfers)

Configurable Currency — any locale per engagement

Configurable Phone Validation — country-specific prefix and format set per deployment

Real-Time Monitoring — Live Activity, Stats, Transactions, Parking Alerts

Multi-Kiosk Android Fleet with Device Registration + Admin Approval Workflow

Android Kiosk — Single-Purpose, Landscape-Locked, RTL-Capable, Watchdog-Protected

Kiosk Drives RFID Card Readers and Barrier Gates Directly — No Third-Party Middleware

Hardware Watchdog Auto-Recovers a Hung Kiosk Without an On-Site Visit

Built-In Hardware Diagnostics Screen on Each Kiosk

Offline-Capable Operations — Licensing Validates Without an Internet Connection

Offline-Validated Sovereign Licensing Tied to the Operator's Own Server

License-Expired Failsafe — App Locks Down with a Branded Notice Instead of Failing Open

Per-Card Customer Records (locale-aware names, phone, optional vehicle plate)

Vehicle-Plate Uniqueness Enforced at the Database Level (one card per plate)

Parking-Session Audit Trail (every leave creates a timestamped session record)

Token-Based Auth for Admin + Staff (configurable session lifetime)

Kiosk-Only Operations Gated by Device Approval (non-approved devices are refused)

System Health + Admin Realtime Monitor (operator sees what every kiosk is doing right now)

Lightweight Single-Binary Deployment (runs on a small Linux box)

Structured Data Model: Customers, Cards, Transactions, Pricing Plans & Profiles, Parking Sessions, Admin & Staff Users, Device Registrations

LAN-Operated Android Kiosks (operator-controlled network, no public exposure required)

Internationalization-Ready — Pluggable Currency, Phone Format, Date Format, and Locale Direction (RTL/LTR)

Core Components

Smart Parking Components

The building blocks that power our smart parking and deliver exceptional results.

Smart Parking core components diagram — RFID lifecycle, role surfaces, pricing profiles, realtime, kiosk fleet, direct hardware control, offline-validated licensing, customer portal — Core building blocks of a complete smart-parking deployment.

RFID Card Lifecycle Management

Card is the unit of customer identity. Full lifecycle from issuance through transfer, replacement, and deactivation.

Unique card number + optional unique vehicle plate enforced at the database level
Car size (small / medium / large) drives pricing
Assigned pricing profile per card
Append-only transaction ledger with post-transaction balance snapshots

Three Role Surfaces

Admin operations center, staff card-management console, no-login customer portal — one codebase, three UX surfaces.

Admin: dashboard, transactions, staff, devices, pricing, system health, realtime monitor
Staff: issue, top-up, leave, lost, customer lookup
Customer: balance check + card-tap leave (no login)
Distinct auth paths per surface; token TTLs separately configurable

Flexible Pricing Profiles

Each pricing profile uses one of two models — a fixed fee at exit per car size, or a duration-based charge from the time parked. Cards are assigned to a profile; the kiosk applies the right model and fee automatically at exit.

Two models per profile — fixed fee at exit or duration-based
Multiple pricing profiles (per customer segment, per zone, per time window)
A simple flat-rate plan is available alongside
Profile assignment can change per card without re-issuing it; pricing changes are immediate and audit-logged

Real-Time Operations Monitor

A standalone real-time monitoring service surfacing live activity to the admin operations center.

Live events: activity, stats, recent transactions, recent cards, running totals, parking alerts
Drives the admin Realtime Monitor view
Updated on every balance change
Fault-tolerant: the app degrades gracefully if the monitoring service is offline

Android Kiosk Fleet

Single-purpose Android kiosk, device registration with admin approval, direct hardware control.

Landscape-locked, RTL-capable, system UI hidden
Device registration with an admin approval workflow
Drives the card reader and barrier gate directly, with a hardware watchdog
Built-in hardware diagnostics screen accessible from the kiosk header

Direct Hardware Control

The kiosk drives RFID card readers, barrier gates, and a hardware watchdog directly — no third-party middleware required.

Drives standard RFID card readers directly
Triggers the barrier-gate output on a successful leave
Feeds a hardware watchdog at fixed intervals
Works with standard hardware from the operator's preferred vendor

Offline-Validated Sovereign Licensing

An offline-validated licence ties each deployment to the operator's own server. It validates on-premise with no phone-home; if invalid or expired, the app fails closed with a branded notice.

Validated entirely on-premise — no phone-home, no SaaS dependency
Tied to the operator's own server
Fails closed (a branded notice) rather than failing open
Resale or unauthorized cloning of the system is infeasible

Customer Self-Service Portal

A no-login customer portal. The customer enters their card number and sees their balance, recent activity, and a card-tap leave shortcut.

No username, no password, no credential-theft surface
Customer identity is the physical card
Reduces support volume to zero for balance inquiries
Designed for thin LAN clients — works on basic Android tablets in the lobby

Benefits

Why Choose Our Smart Parking

Real-world advantages that drive measurable business outcomes.

Benefits infographic for Smart Parking — zero cash shrinkage, sub-5s leave, on-prem control, transparent pricing, realtime ops — Measurable outcomes: zero cash shrinkage, sub-5s leave, audit-ready.

Replace ticket printers and gate operators with RFID cards + barrier kiosks — day-one labor savings on every shift

Cut leave-time at the gate to under 5 seconds — the kiosk calculates the fee (fixed or duration-based), deducts it, opens the barrier, and logs the session

Eliminate cash-handling losses with prepaid top-ups — every transaction flows through the audited ledger

Run entirely on-premise on the operator's LAN — no SaaS dependency, no internet outage takes the gate down

Per-car-size pricing lets one car park handle small cars, sedans, and SUVs/buses at correct rates without operator override

Live realtime monitor surfaces hardware faults, kiosk disconnects, and unusual transactions in seconds — not days

Device registration with admin approval prevents rogue kiosks from being plugged into the network and used to issue cards

Offline-validated sovereign licensing ties each deployment to the operator's own server — resale or unauthorized cloning is infeasible

Locale-aware out of the box (RTL Arabic baseline; configurable currency and phone format per operator) — drops in for any market with a small re-localisation pass

Re-localizable for any market in days, not months — currency, phone, language, locale direction are all configurable

Process

How Smart Parking Works

A simple, streamlined process to get you up and running quickly.

Issue Card at Reception

Staff issues a new RFID card to a customer: locale-aware name, locale-aware phone format, optional vehicle plate, car size (small / medium / large), pricing profile, initial top-up amount. The system mints a unique card, writes the customer and card records, and records the initial top-up transaction with the post-transaction balance.

Customer Drives Into the Lot

The customer pulls up to the entrance kiosk and taps the RFID card. The Android kiosk reads the card via the RFID reader, validates the card and its balance, and opens the barrier gate directly.

Top Up at Counter or Kiosk

When the balance runs low, the customer tops up at the staff counter (or self-service kiosk). Each top-up writes a transaction with the post-transaction balance snapshot and triggers a live activity event so the admin's realtime monitor sees it instantly.

Customer Drives Out

At the exit kiosk, the customer taps the card. The kiosk processes the leave atomically: it reads the car size and pricing profile, calculates the fee — a flat charge per car size, or a duration-based amount from the time parked — deducts it, writes the parking-fee transaction with the new balance, records the parking session, and opens the barrier gate. End-to-end: under 5 seconds.

Operator Monitors + Audits in Real Time

Admin opens the operations center: dashboard KPIs, today's transactions, recent activity, system health per kiosk, pricing-profile management, staff and admin user management. The Realtime Monitor streams live activity, stats, recent transactions, and parking alerts. Every action is auditable from the transaction ledger and parking-session history.

Issue Card at Reception

Customer Drives Into the Lot

The customer pulls up to the entrance kiosk and taps the RFID card. The Android kiosk reads the card via the RFID reader, validates the card and its balance, and opens the barrier gate directly.

Top Up at Counter or Kiosk

Customer Drives Out

Operator Monitors + Audits in Real Time

Industries

Industries We Serve

Our smart parking is designed to deliver value across diverse industries and operational environments.

Industries served by Smart Parking — malls, hospitals, airports, offices, universities, hotels, mosques, government, stadiums, compounds — Industries where Smart Parking delivers a complete operations workflow.

Open the deep dive by vertical

Healthcare

Patient flow + clinical EMR, multilingual by engineering

Retail

Queue + signage + parking + feedback under one platform

Education

Campus flow + visitor mgmt + wayfinding + payment kiosks

Airports

Passenger flow + wayfinding + signage + parking

Parking

RFID + Android kiosks + sovereign on-prem licensing

Shopping Malls

Office Buildings & Business Parks

Hospitals & Medical Centers

Airports & Transit Hubs

Universities & School Campuses

Hotels & Resorts

Mosques & Religious Complexes

Government Buildings

Stadiums & Event Venues

Residential Compounds & Gated Communities

Public Parking Operators

Logistics & Warehouse Yards

Convention Centers

Theme Parks & Entertainment Venues

Hospitals & Healthcare Campuses

Manufacturing Plant Lots

Bus Terminals & Taxi Stations

Embassies & Diplomatic Compounds

Public Service Halls

Multi-Tenant Commercial Towers

FAQ

Frequently Asked Questions

Get answers to the most common questions about our smart parking.

Explore Related Solutions

Complementary solutions that work seamlessly with our smart parking.

Related GLARUS solutions to Smart Parking — visitor management, self-service kiosks, digital signage, wayfinding, customer feedback — Solutions that extend Smart Parking into a full customer-experience stack.

Visitor Management System

Pair Smart Parking with visitor management to cross-reference vehicle ownership with visitor identity — useful for high-security compounds, hospitals, and corporate campuses.

Learn more

Digital Self-Service Kiosk

For larger sites, lobby self-service kiosks let customers self-issue cards, top up balance, view their history, and print receipts — without staff intervention.

Learn more

Digital Signage System

Live signage at the gates: current available spaces, current pricing, queue length at the staff counter, lane open/closed status — all driven by the same real-time feed.

Learn more

Wayfinding System

For large multi-level lots, pair Smart Parking with wayfinding to guide drivers to available zones and back to their vehicles via QR-code session handoffs.

Learn more

Customer Feedback System

Post-leave customer feedback capture — SMS, kiosk-screen survey, or QR code — closes the loop on parking experience and surfaces friction points fast.

Learn more

Get Started Today

Ready to Transform Your Operations with Smart Parking?

Get started today with a personalized demo and see how our smart parking can revolutionize your customer experience and operational efficiency.

Request a Demo Calculate ROI

Glossary

Definitions for the operational terms that appear across this page. Tap any chip to read the long-form entry plus its cross-links.

Air-Gapped Deployment ANPR / LPR Bilingual Baseline Cyber Essentials Data Residency Discovery Phase Gate Barrier IEC 62443 +13 more · browse glossary