EhliyetPro

Many rules, scattered records

A driving school runs on rules that are easy to break by hand. An instructor cannot teach two lessons at once, a car with an expired inspection cannot be used, and trainees need their required hours before an exam. The office also keeps sensitive personal data, from identity numbers to health reports, which Turkish data protection law (KVKK) requires it to protect.

EhliyetPro is a rewrite. The earlier generation of the system sat on an unmaintained framework whose security issues could no longer be patched, and its database had no indexes or uniqueness rules.

My role

I developed EhliyetPro: the scope and requirements documents, the per-feature specifications, the screen designs and the code. That covers a .NET API on PostgreSQL, separate web apps for the course office, instructors, trainees and the head office, a marketing site, and the deployment, backup and release setup. The product documents also record pricing and risk decisions.

What exists today

The features below are in the production release. The project keeps a written feature list that separates what works from what is still on the way, and the same line is kept here. Online card payments are written but switched off in production, and the mobile app is not yet in the stores.

• Trainee records and document checks

  Shipped

  Registration with an identity check against the population register, encrypted document storage and barcode checks against e-Devlet.

• Lesson planner with clash checks

  Shipped

  A weekly calendar that refuses clashing lessons and lists every conflict at once: instructor, vehicle, inspection or licence class.

• Exams and mock exams

  Shipped

  Exam scheduling with a readiness check on required hours, results hidden until the school publishes them, and school-written theory mock exams.

• Collections ledger

  Shipped

  Instalment plans, payments by method, corrections as reversal entries, month closing and bank reconciliation.

• Fleet and vehicle documents

  Shipped

  Vehicle records, inspection and insurance periods with expiry reminders, maintenance tracking, and accident and fine records.

• Instructor pay

  Shipped

  Monthly earnings drafts that instructors approve or dispute from their portal, and payments recorded against them.

• Trainee and instructor portals

  Shipped

  Web portals where trainees see lessons, exams and balances, and instructors take attendance and check their pay. Sign-in by SMS code, password or e-mail link.

• Leads, bulk import and supplies marketplace

  Shipped

  Enquiries from the marketing site routed to schools by district, imports of up to 5,000 rows, and a marketplace module in the course panel.

• Online card payments

  In progress

  Built and tested in the payment provider's sandbox. Production stays off until each school can be onboarded as its own sub-merchant.

• Mobile app for trainees and instructors

  In progress

  An iOS and Android app exists in code. It has no store listing yet.

• MEBBİS integration, SMS and WhatsApp notices, e-invoice

  Planned

  Decided or listed on the roadmap, not built.

How it works

One .NET API on PostgreSQL serves every app. Each driving school is a tenant, and tenant isolation is part of the data model rather than a filter written into each query. Personal data such as names, identity numbers and phone numbers is encrypted field by field with a key per school, and the master key is kept out of the database and the backups.

The web apps are static builds hosted on Cloudflare Pages. Their types are generated from the API's contract, so the screens and the server cannot drift apart. Every change runs through continuous integration, where compiler warnings count as errors.

Running it day to day

The office works in the course panel: registering trainees, planning the week, recording payments. Instructors use their portal from the car to take attendance and close lessons. Trainees check their own lessons, exams and balance. A head office panel lets the platform team set up schools and assign incoming leads.

Operations run on one server with Docker and no open ports, behind a Cloudflare tunnel. Encrypted nightly backups are kept for 14 days and checked every six hours, and a restore has been rehearsed.

Decisions behind it

Several decisions are written down with their reasons. The product is free, and the paid tiers were withdrawn rather than shown as coming soon. Live card payments wait for a proper sub-merchant model, because collecting money for schools would mean acting as a payment institution. Two-factor sign-in was left out until it can work properly, since a security feature that only looks active is worse than none.