PlateSiPlateSi Login
ANPR · MMR · Middle East

Every plate. Every make. Every model.

PlateSi reads the licence plate and recognises the make, model, type and colour of the vehicle in a single call. Use it as a cloud API, or install the same engine at your site and read with no internet.

Drop-in compatible request and response Cloud or on-site Specially dedicated to the Middle East Arabic and Latin plates
Dubai · private
// POST /vehicle/me
{
  "plate":  { "found": true, "unicodeText": "DD 15311",
              "country": "ARE", "confidence": 97.4 },
  "mmr":    { "found": true, "make": "…", "model": "…",
              "category": "…", "color": { "r":… } }
}
One region, done properly

Dedicated to the Middle East

PlateSi is specially dedicated to the Middle East. It is trained, tested and released on traffic from the region, so it is tuned for the plates and vehicles you actually see on Gulf roads.

  • Plate designs of the UAE and Saudi Arabia first, then the rest of the GCC and India
  • Arabic and Latin characters, emirate and region designs, letter codes, plate colours and categories
  • Vehicle make, model and colour for the vehicles driven in the region
  • One region code, me: nothing to choose, nothing to get wrong

What we do, and what we don't

We doWe don't
Read plates from a still image (ANPR)Process video streams
Recognise make, model, type, colour (MMR)Containers, rail wagons, hazard signs
Middle East plates, dedicated modelsOther world regions
Cloud API or on-site engineID document reading

A focused scope on purpose: a smaller surface to integrate, and models that keep getting better at the job they were built for.

What it does

One call, a complete vehicle record

Send a still image from a camera, a gate or a phone. The reply carries the plate, the vehicle, and how sure the engine is about each part.

A

Plate reading (ANPR)

Plate text with regional and special characters, plate colour and category, the plate's position in the frame, and the country and emirate or state.

M

Vehicle recognition (MMR)

Make, model, type, category and colour of the vehicle, each with its own confidence value.

⇄

Drop-in API

Same path, same header, same multipart fields and the same response body as the API you may already use. Change the address, keep your code.

⌂

Cloud or on-site

The same engine runs as this service or installed on a machine at your site, reading with no connectivity. Choose per site.

◎

Console

Sites, API keys, usage, plans, invoices and users in one place, with roles that give each person only what they need.

↻

Learns from the field

Frames the engine could not read are kept for the next training run, so accuracy on the roads you actually cover keeps improving.

Integrate in minutes

From a key to a reading in three steps

  1. Get a company accountYou receive an invitation by email, set your details and choose your login. You start on the Free plan.
  2. Create a site and an API keyOne site per camera location or system. Each site has its own keys and its own usage.
  3. Post an imageA single multipart request. The reading comes back in the same response.
# replace YOUR-API and KEY
curl -X POST https://YOUR-API/vehicle/me \
  -H "X-Api-Key: KEY" \
  -F "image=@plate.jpg" \
  -F "service=anpr,mmr"
1call returns plate and vehicle
2,500lookups on the Free plan
USDsimple, usage-based billing
Built for the region

Trained on Gulf roads, not borrowed from elsewhere

Plates in the UAE and Saudi Arabia mix Arabic and Latin characters, emirate designs, letter codes and colours. The engine is trained on traffic from the region, then measured against its own failures before every release.

Region first

UAE and Saudi Arabia first, then the rest of the GCC and India.

Measured releases

A new model replaces the old one only if it reads at least as many plates as the model it replaces.

Same bytes everywhere

Cloud and on-site engines are published together and carry a version file with a hash per model, so the same version means the same reading.

Ready to read your first plate?

Talk to us about a company account, or sign in if you already have one.

Platform

One engine, three ways to use it

Everything runs on the same trained models. What differs is where the image is read, and who looks after the machine.

Cloud API

Post images to /vehicle/me from cameras, servers or apps. Nothing to install, one place to update, and every unrecognised frame feeds the next training run.

  • Company accounts, sites and keys
  • Plans, usage and invoices
  • Console with roles

On-site engine

A Windows installation of the same engine with a single-page upload screen and JSON download. CPU only, no GPU, and it works with no internet.

  • Reads offline
  • Same response shape as the cloud
  • Models updated from the training release

Capture tool

A local application that connects to cameras, takes still images when a vehicle is present and asks the cloud or on-site engine for the reading. The engines themselves read still images only.

  • Still images from cameras
  • Portable, no-install Windows folder
  • Works with either engine

What is in a reading

GroupFields
Platefound, text (Unicode and separated), characters, country, state or emirate, plate type and category, background and accent colour, position, confidence
Vehiclefound, make, model, category, colour (RGB), heading, each with a confidence value
Metaengine version, processing time, which half of the engine was run

Choose what to run with service=anpr, service=mmr or service=anpr,mmr. The part you did not ask for is returned empty, in the same shape as "not found".

The console

The browser console is where an account is run: who can do what, which sites exist, how much has been read and what has been billed.

  • Dashboard of readings by site and key
  • Demo Test: try an image against your own key
  • Keys: create, disable, set an expiry, rotate with a grace period
  • Usage by day and by site
  • Account: company and billing details, plan, invoices
  • Users and roles, one privilege per menu, tab and button
Login to the console

Your data

Images are read and answered. Only frames the engine could not read confidently are kept, as training material for the next release. Contact us for details about retention for your account.

Use cases

Wherever a vehicle needs to be identified

The same reading serves very different jobs. Pick the one closest to yours.

Parking management

Open barriers, bill by duration, and match the vehicle's make and colour to the plate to catch swapped plates.

Access control and communities

Admit residents and visitors by plate. Log every entry with the image and the reading.

Traffic analysis

Count vehicles by type and colour, measure flows and dwell times on roads and at junctions.

Law enforcement and security

Check plates against alert lists and confirm the vehicle description matches the registration.

Car washes and service lanes

Recognise returning customers on arrival and start the right package without a card or a ticket.

Drive-through

Identify the vehicle at the order point and personalise the service.

Tolling and congestion charging

Charge by plate and vehicle class, with a reading for each lane.

Fleet and logistics

Log arrivals and departures at depots and gates automatically.

Plans

Pay for the lookups you use

Each company has one monthly allowance shared by all its sites. Start on Free and change plan from the console at any time.

How billing works

Dubai calendar months

An invoice is made for each company on the 1st for the month just ended, due on the 10th.

Mid-month start

A company that starts mid-month pays the plan fee for the days left and receives the allowance for those days.

Plan changes

A plan change or cancellation starts on the 1st of next month. A cancellation can be taken back until it starts.

Unpaid invoices

If an invoice is unpaid after the 10th, the company's sites are refused until it is marked paid. Console logins keep working.

Plan questions

What happens if I use more than my plan allows?

Nothing stops. Your sites keep reading, and the extra lookups are charged on your next invoice at $1.10 for every started 1,000 lookups. This is the same on every plan, the Free plan included.

A lookup is one detection call made with a valid key. The allowance is counted across all the keys of all of your company's sites together, so it does not matter which site made the call. Calls that are refused (for example a missing or disabled key) are not lookups and are not counted.

"Started" means each block of 1,000 is charged in full as soon as it begins: going over by 1 lookup costs $1.10, going over by 1,001 costs $2.20.

You can see how far into your allowance you are at any time in the console, and you can move to a bigger plan from Account. A plan change starts on the 1st of next month.

Do the free lookups renew?

The Free plan has a monthly allowance of 2,500 lookups, and the same features as the paid plans.

What if your billing system is unavailable?

Detections are allowed. A billing outage never stops a camera.

Is VAT included?

Amounts are in US dollars and shown without VAT unless VAT is applied to your account.

Contact

Let's get you reading plates

Tell us what you need. This opens a message in your email program, addressed to our team.

Accounts and billing

accounts@secureaai.com

Already a customer?

Sign in to the console to manage sites, keys and invoices.


Login