Every parking system
you run, in one console.
Parkeze runs enforcement, permits and payments itself, and connects the pay apps, meters, gates, cameras and sensors you already have into the same record. Use ours, keep yours, or both. Officers check one screen, staff run one console, and every number is ready for AI.

Our own enforcement and payments, or the systems you already run
Ten systems, ten logins, and one question nobody can answer.
Did this car have the right to park here? Today the answer is spread across a pay app, a permit system, a meter vendor and a gate. Parkeze connects them, so the answer is one record.
- Pay app portal
- Meter back office
- Permit system
- Citation system
- Appeals inbox
- Gate software
- LPR console
- Sensor dashboard
- LNS, SIM and gateway portals
- The spreadsheet that ties them together
Parkeze
- One record
- One console
- One plate check
- One API
One plate check against every pay app and permit.
Officers stop juggling vendor apps. A plate answers with paid sessions from every source, permits, passes and earlier tickets, and the citation carries the evidence behind it.
- Sessions from every pay app and meter
- Dispatch a tow or send an officer from the map
- Appeals, hearings, notices, boot and tow

Every dollar, from every channel, in one ledger.
Parking, permits, reservations, citations and validations land on one payment record from checkout to settlement, through the processor you already use.
- App, web, QR, text, phone and cashier
- Refunds, disputes and processor fees in one place
- Revenue by zone, product and day

Every lane, from any gate vendor, on the same map.
Each passage records who came through, on what credential and why they were let in. The gate asks the same question an officer does: does this vehicle have the right to park?
- Plates, cards, fobs, QR and mobile credentials
- Permits and paid sessions open the gate
- A manual open is logged like any other passage

Notice first. Tow last. Every step recorded.
Automations climb a ladder you write: the evidence on a case, time to pay, a mailed notice and a text, and only then a tow that a supervisor approves. Each step stops the moment the ticket is paid. They run on the ontology, the one record every connected system writes to, so the same rules hold whichever vendor the evidence came from.
- Evidence on the case from the first step
- Mail, text and wait before anything drastic
- A tow only with a supervisor's approval

We started by making sensors. We still sell them.
Parkeze began in 2024 building parking sensors, and the network we built to run them became Parkeze Net: the LoRaWAN and Bluetooth network server, SIMs, gateway management and device codecs in one console. Buy our sensors, bring your own, or run any device on it.
| Job | Usually | Parkeze Net |
|---|---|---|
| Devices, keys and joins | Your LNS console | One console |
| SIM activation and data use | Your SIM provider's portal | One console |
| Gateway config, firmware, remote access | Gateway management software | One console |
| Payload decoders | Scripts copied from each vendor | One console |
| Bluetooth beacons and their passwords | A separate BLE platform | One console |
| Decoded data, dashboards, alerts | Yet another application | One console |

Our sensor is a 95 mm magnetometer puck: five minutes to install, ten years on a battery, no camera and no plates. Sold on its own or with a network we run for you.
Tell us what you run.
We'll show you one console.
Send your current vendors and what you manage. We will come back with how they connect to Parkeze, what changes for your staff, and what it costs.