What we have built on site

A ten-thousand square metre plant with a live production line. At this scale, computers stop being office equipment: production itself depends on them.

The server room was designed from scratch around a single requirement — production does not stop. The network backbone was installed and taken into managed operation. Servers were consolidated onto a virtualisation platform, an IP telephony system was commissioned, and a backup and disaster recovery architecture was designed alongside it.

The project did not end at go-live. It continued as ongoing operational support.

Another ten-thousand square metre production site, but this project turned on security architecture. Every point where production data or the network reached the outside world was part of the design.

The server room was engineered and the network was rolled out. The firewall architecture was designed together with the site's network topology — not bolted on afterwards as a device, but built in as part of the structure.

A backup and disaster recovery platform followed. Where data is held, how often it is captured, and how long it takes to come back after an incident were all defined at the outset rather than discovered during one.

A thousand square metre head office. In construction, the data is project files coming in from site: large, constantly changing, and impossible to recreate once lost. The server room had to both host that data and protect it.

The server room was designed and built. Servers were moved onto a virtualisation platform, which cut the hardware count while increasing redundancy. A backup routine was established and a firewall was brought into service.

A thousand square metre facility with production and offices under one roof.

Here the network was treated as part of a single design together with the server room. In most businesses the two are built at different times and in isolation from each other — and that is precisely where most of the resulting problems originate.

The server room was designed and engineered. The network, the virtualisation platform, the backup routine and the firewall were all put in place together.

A four-hundred square metre facility — small, but data-heavy. At this scale, "we have a server" is not an answer. The real question is how many hours the business stops when that server does.

The server room was built and the servers were virtualised. The backup and disaster recovery platform was sized for the facility: nothing over-engineered, but genuinely recoverable.

Businesses with more than one location keep running into the same question: how does someone at a branch reach a file at head office securely, without opening the network to the outside?

Site-to-site network security topologies were designed and operated on FortiGate and MikroTik hardware. Three technologies were used depending on what each site needed: IPsec for the widely supported, conventional branch-to-head-office tunnel, SSL VPN for individual remote access from the field, and WireGuard where faster and simpler configuration was the better fit.

Rather than committing to one technology, the right fit was chosen for each organisation's hardware and requirements.

In most businesses, compliance with KVKK — Türkiye's Personal Data Protection Law, Law No. 6698 — starts as a legal document and stays there. What an audit actually asks about is technical: where the data sits, who can reach it, whether that access is logged, and whether the data is encrypted.

A data inventory was produced, establishing what is held where and for how long. Access control was reviewed: who can reach what was defined explicitly, and anything surplus was removed. Logging was implemented so that access can be traced after the fact. An encryption review followed.

Together these four steps form the technical groundwork behind a VERBİS registration — the national data controllers' registry — and make sure the declarations on the registration form are backed by something real.