Zones, tariffs & geometry
Zones drawn as polygons on a map, with colour, type, working hours, holidays and max stay. Reusable tariffs carry price, VAT and effective dates. Changes reach the payment flow immediately.
Intelligence in Motion
Smarter zones.
Seamless payments.
Real municipal revenue.
Kinergon is a configurable ecosystem for public parking management. Zones and tariffs, residents and permits, payment channels, enforcement, reporting and settlement — every module switched on and shaped to how your city actually works.
Run the whole ecosystem, or only the modules that fill your gaps.
The loop
One loop, from the curbside to the treasury.
Whatever channel a driver uses and whichever modules a city runs, every parking event travels the same four beats. Nothing is a dead end — what happens on the street comes back as reconciled revenue.
-
01
Sense
A payment message, a permit holder, an inspector check or a device reading — normalised into one record, whatever alphabet the plate was written in.
-
02
Decide
The zone the vehicle sits in, the tariff in force at that moment, the working hours, the holiday calendar, and any permit or exemption that applies.
-
03
Act
Take the charge on the enabled channel and confirm it to the driver — or open an enforcement request and route it to the role that handles that step.
-
04
Impact
Every transaction reconciled against the collecting party, the municipality's share remitted on its own split, and the period reported without a spreadsheet.
The ecosystem
Eight modules. One core.
Each one stands on its own and every one shares the same data model, so adding a module never means migrating a city.
Residents, permits & subscriptions
Define any number of permit types with their own price, duration, district and discount rules. Intake, review, approval and activation on payment — including instalment plans and exempt vehicles.
Payment channels
Start with SMS on a single short number and direct carrier billing across every operator in the market. Card, wallet, QR and the citizen app extend the same charging core rather than replacing it.
Enforcement & penalty parking
Split clamping and towing into your own steps and assign each one to a role. Sanction records carry coordinates, photos and who acted. Release protocols and amounts due calculate themselves.
Field enforcer app
A handheld app for inspectors: check a plate against every channel at once, capture location, address, time and photos, and raise a clamp or tow request straight into the back-office workflow.
Reporting & settlement
Live figures for the agency, period reports broken down by channel and collecting party, reconciliation against what was actually collected, and a configurable revenue split remitted on schedule.
Users, roles & audit
Every role defines which interfaces, functions and data it reaches. Users set their own passwords, nobody else can read them, and payments, approvals and enforcement steps are recorded against a name.
Integration adapters
One canonical core, one adapter per city. Whatever a municipality already runs — records, cash desk, a central parking system — connects through its own adapter while the product stays a single product.
Configuration
Configured, not customised.
No two municipalities price, schedule or enforce parking the same way, and none of them should need a release to change their mind. Everything a city governs is an editable object in the platform — the code underneath stays one product for everyone.
That is what keeps a deployment measured in weeks instead of a bespoke build, and what keeps every city on the same version.
- Zones colour, type, polygon boundaries, districts, capacity
- Tariffs price per unit, currency, VAT, effective-from and to
- Time working hours per weekday, free days, holiday calendar
- Messages the full text set the citizen receives, edited in place
- Permits types, durations, districts, discounts, renewal reminders
- Sanctions violation types, prices, and the wording on the notice
- Workflow the steps of a clamp or a tow, and the role that owns each
- Revenue the municipality's share of the split, net of commission
- Access roles, the functions they reach, and the data they see
Integration
Fits the system you have. Replaces the one you don't.
Some cities already own a central parking system and need the layer in front of it. Others have nothing and need the whole thing. The same platform does both.
Driver
Pays on whichever channel the city has enabled, and is told what they owe and until when.
Kinergon
- Zones, tariffs & geometry
- Permits & subscriptions
- Charging & channels
- Enforcement workflow
- Notifications
- Reporting & settlement
Authoritative on the fee and the paid state.
The city
Its existing systems join through a per-client adapter; its field staff carry out the physical acts.
In our court
- Zone and tariff definitions, including boundaries
- Subscriptions and resident permits
- Charging, channel connectivity and the citizen's reply
- Enforcement workflow and penalty parking, as a system of record
- Reporting, reconciliation and settlement
- A published API specification for whoever integrates next
Deliberately not ours
- The physical acts — staff place the clamp and tow the vehicle
- The municipal ordinance and the enforcement policy behind it
- Whatever the city's own records system is already good at
Drawing this line is the point. It is why a deployment is a configuration exercise and not a rebuild of how a city already works.
Product family
One identity. Three energy states.
The modules group into three products. Take one, take all three — they share a core, so they never disagree about a vehicle.
Kinetic Blue
Kinergon Core
The system of record: what the zones are, what they cost right now, who holds a permit, and who is allowed to change any of it.
- Zones, tariffs & geometry
- Residents & permits
- Roles, audit & adapters
Trust · Tech · Intelligence
Kinetic Lime
Kinergon Pay
Every way a driver can settle a stay, and every way the money finds its way back to the municipality.
- SMS & carrier billing
- Card, wallet, QR and app
- Reconciliation & settlement
Innovation · Energy · Growth
Signal Orange
Kinergon Enforce
What happens when a vehicle has not paid: the check, the sanction, the clamp or the tow, and the release at the end of it.
- Enforcement workflow
- Penalty parking & release
- Field enforcer app
Action · Performance · Impact
About
Kinetic + ergon: energy applied to work.
Public parking is a system that already exists in every city, and in most of them it is stitched together from a payment supplier, a spreadsheet, a records office and a radio. Kinergon replaces the stitching with one configurable platform — and leaves each municipality in charge of its own rules.
We build for the part that touches the real world: a vehicle at a kerb, an inspector with a handheld, a treasury expecting a number it can defend. That is what the mark means — motion that produces a result.
1Canonical core
8Modules
0Forks per city
Configure it for your city.
Tell us how your parking works today — the zones, the channels, the systems you are keeping. We will show you the profile that fits it.