Skip to content
+90 850 885 27 43 info@argeict.com

Business applications

Bus ticketing system infrastructure

ARGE ICT builds and operates the server, database, sales office connectivity, backup, and security infrastructure behind bus companies' ticketing systems, in the company's own environment or on ARGE Cloud in Istanbul.

An intercity bus company sells tickets through its sales offices, its website, its mobile app, agencies, and ticket marketplaces at the same time. All of these channels draw on the same trip and seat data, and a seat that has been sold cannot be sold again on another channel. The ticketing server and database at the center therefore have to run both without interruption and consistently. In Turkey this software is usually called "otobüs otomasyonu" or "bilet satış otomasyonu".

Trips and ticket sales rise sharply during public holidays. Planning the infrastructure for that load is the most direct way to avoid lost sales. Whichever vendor's ticketing system you use, we build and operate the infrastructure it runs on.

When you need it

  • Sales screens slow down or lose connection during holiday peaks.
  • The ticketing server runs in a room at head office and its backups are unclear.
  • Sales stop when a sales office loses its internet connection.
  • The website and mobile app are exposed to the internet without protection against attacks.
  • Access to passenger data is not logged.

Rules that shape the infrastructure

Ticket sales involve both passengers' personal data and official notifications. We build the infrastructure around the rules below and check the current text of the regulations with you before installation.

  • Road Transport Regulation: A ticket carries the passenger's Turkish ID number, name, contact details, and seat number. Passenger details are reported to the Transport Electronic Tracking and Inspection System (U-ETDS) before the trip starts, and cancellations are reported shortly after. The ticketing system's external connection has to stay up for these notifications to go out on time.
  • e-Ticket: Under the Revenue Administration's rules, companies holding a D1 authorization certificate have issued e-tickets and e-ticket passenger lists since 2021.
  • KVKK: Passenger details are personal data under KVKK, Turkey's personal data protection law (Law No. 6698); access must be limited and logged.
  • Card payments: PCI DSS is the card industry's security standard for environments that take card payments. The payment page usually runs at the payment provider; our job is to separate the systems that come near card data on the network.

Scope

  • Central server and database. We set up the ticketing application and database servers and patch them on a schedule. We confirm hardware and virtualization requirements in the vendor's documentation before installation.
  • Peak-period capacity. We measure usage during past holiday peaks and plan CPU, memory, and database capacity before the next one. Resources for virtual servers on ARGE Cloud can be increased for these periods.
  • Website and mobile app endpoints. We publish internet-facing endpoints behind a web application firewall (WAF) and a reverse proxy, over TLS; the database is never exposed to the internet. Where needed, we plan DDoS protection.
  • Sales office and agency connectivity. We connect sales offices to the center with IPsec, SD-WAN, or ARGE ZTNA. So that sales continue when the main line drops, we can install a mobile backup line at the office.
  • External connections. We manage the network, firewall rules, and certificates behind connections to U-ETDS, the e-ticket integrator, the payment provider, and ticket marketplaces.
  • Backup and restore testing. We back up the database to the isolated backup area on ARGE Cloud and report each restore test result to you in writing.
  • Access logs and monitoring. We collect server, database, and firewall logs in a central log system (SIEM). We monitor disk, memory, the database service, and external connections; monitoring hours and response scope are written in the contract.

Out of scope and limits

We do not sell ticketing system licenses or provide installation or functional support, and we are not an official partner of ticketing software vendors or ticket marketplaces. The content and timing of U-ETDS and e-ticket notifications are the software's job; we make sure the connection they travel over works. PCI DSS certification is not part of this service.

How we work

  1. We map where the ticketing server runs today, the database, backups, sales office links, and external connections.
  2. We measure usage during past peaks, confirm the vendor's requirements, and propose a design in writing.
  3. We plan the migration outside peak periods and at the hours with the fewest sales, and take a backup and test the restore before moving anything.
  4. After migration, we report backup results and capacity trends and review capacity with you before every peak period.

Service models

  1. On ARGE Cloud: The ticketing servers run in the Istanbul data center, in a VPC dedicated to you; sales offices and internet-facing endpoints reach it over secure connections.
  2. In your environment: We build and operate the server, database, network, and backups in your company's server room.
  3. Combined: The ticketing system runs in your environment while the backup and disaster recovery environment sits on ARGE Cloud.

Where the carrier provides MPLS, head office, terminal sales offices, and city ticket desks reach the center and ARGE Cloud over that private line without touching the internet. Most bus terminal offices have no MPLS; there, an SD-WAN capable firewall uses a fiber line and a mobile line together and keeps sales running on one when the other drops. We compare the options in how head office, branches, and the cloud connect.

Technologies we use: Windows Server · Linux · Microsoft SQL Server · WAF · IPsec · SD-WAN · SSL VPN · ARGE ZTNA · SIEM

Frequently asked questions

The system slows down during holidays. Is it the server or the software? We measure first. By watching CPU, memory, disk, and database wait times during the peak, we report whether the bottleneck is in the infrastructure or the software. If it is the infrastructure, we add capacity before the next peak; if it is the software, we share the findings with the vendor.

Do sales stop if a sales office loses internet? With a mobile backup line at the office, the connection continues over that line when the main line drops. Whether offline sales are possible depends on the ticketing system you use.

Where is passenger data kept? Data for systems running on ARGE Cloud is kept in the Istanbul data center, in a VPC dedicated to you. If you choose to run the servers in your own server room, the data stays inside your company.

Do you set up the connection to ticket marketplaces? Your ticketing vendor and the marketplace build the software side of the connection. We manage the network, firewall rules, and certificates it runs over.

Talk to us about ticketing infrastructure

Tell us which ticketing system you use and how many sales offices you have; we reply within 1 business day.

Request an infrastructure call