For operators & authorities

The platform under
the pavement.

Everything a city, an operator or an enforcement authority needs to run parking as infrastructure — APDS-conformant, auditable, and open to integrate.

APDSAlliance for Parking Data Standards
3Portals — admin · operator · customer
عربيBilingual by design
The estate model

One model, every shape of estate.

Multi-level · gated

Buildings with levels and sections.

A multi-storey garage models each floor as a level and each area within a floor as a zone, down to the individual bay. Levels are optional — use them only where the building has them. Gates are part of the model, so drive-in entry and exit belong to the place.

One level · sections

Flat parking, divided into zones.

A surface lot that needs different rules per area splits into zones on a single level — each zone can carry its own tariff, its own eligibility and its own capacity, while the place stays one estate node.

One level · no sections

The simplest shape there is.

No levels, no zones — bays sit directly on the place. One tariff, one pool of capacity, modelled in minutes. Most small lots never need more than this.

On-street

The curb as a place.

An on-street zone hugs the street: an identified area with curb bays and no levels at all. Pay-by-plate sessions, patrol and ANPR enforcement all attach here — this is most of Riyadh today.

Mixed · free inside paid

Free parking inside paid parking.

Eligibility is data, so a zone inside a paid place can be free — for everyone, or only for exempt groups such as residents, permit holders or exempt vehicle types. No special cases in code; it is just another rule on the zone.

The capability map

From estate model to settled money.

01

Model the estate

The city as a governed hierarchy — campus, place, level, zone, space.

  • Guided hierarchy explorer with type-aware creation
  • Geometry on every node — boundaries, footprints, points on the map
  • Readiness gates before anything goes on sale
  • Commerce inheritance down the hierarchy, with barriers where you need them
02

Price as data

APDS-conformant commercial modelling — no code changes to change a tariff.

  • Rate matrices, rate tables and rate lines with effective dating
  • Products (rights) with pools, validity and monetary value
  • Eligibility as first-class data — audiences, vehicles, exemptions
  • Free parking, windows, day patterns and tiered pricing
03

Sell the curb

A public catalog and a booking engine that never oversell.

  • Public search, near-me and place detail with live tariffs
  • Exact quotes for any time window — VAT included, 15-minute validity
  • Atomic capacity claims — sold out means sold out
  • Session start on payment, extend with an accurate re-quote
04

Own the money

Every riyal accounted for, engine-verified, and auditable.

  • Card via hosted checkout and prepaid wallet with auto-refill
  • Insert-only receipts and wallet ledger — corrections, never edits
  • Self-healing reconciliation against the billing engine
  • Refunds recorded at the actually-paid amount
05

Issue permits

Recurring parking as governed rights, not spreadsheets.

  • Permit products per place with eligibility rules
  • Customer self-service purchase and renewal
  • Permit visibility in the customer account
  • Same money rails as every other charge
06

Know the customer

Verified identity and vehicles, national-grade.

  • Nafath step-up verification for high-trust actions
  • Yakeen-verified vehicle ownership and attributes
  • Admin-managed customer eligibility groups
  • Eligibility-aware pricing driven by the verified vehicle
07

Enforce fairly

From observation to citation with policy, not improvisation.

  • ANPR, patrol and chalk observations ingested at the edge
  • Rule-based assessment with per-place contravention policies
  • Citations with lifecycle, reference codes and appeals
  • Plate-indexed valid-right checks in real time
08

Run the operation

Portals and permissions that match how cities actually work.

  • Operator and admin portals with scoped access
  • Place-scoped roles — each operator sees only their estate
  • Organisation onboarding with Keycloak-backed users
  • Integration API keys for machine-to-machine access
09

Integrate & observe

A platform you can build on, not a black box.

  • Versioned REST APIs with a standard envelope
  • Signed webhooks with replay-safe idempotency
  • Bilingual data model — Arabic and English everywhere
  • Provider-neutral billing port — the engine is swappable
How it lands

One estate, many operators.

The authority owns the model; operators run their scope. Every role sees exactly the places, tariffs and money it is responsible for — nothing else.

  • Authority-level oversight across the whole estate
  • Operator portals confined to assigned places
  • Auditable trails on every commercial change
Getting on the platform

Bring your city online.

Onboarding starts with your estate and your tariffs — both are data, so a pilot zone can be live in days, not quarters.

  • Estate import from your existing inventory
  • Tariff modelling workshops with the platform team
  • Pilot on real streets, expand zone by zone
See it running in Riyadh →