Skip to content
By Role

IT & Systems

Where is my data, and will this system burn me one day?

The answer is not in a contract but in the architecture: you choose where your data lives, it does not cross the border, and an outage is a design assumption, not a fault.

  • Operational Resilience Platform
  • Network-Independent Communications
  • Real-Time Crisis Management
  • Powered by Türkiye's first underground data centre infrastructure
  • Backed by the Ministry of Industry and Technology

That moment, on your screen

Below is what you did not do on the night of the crisis. Each one is the result of an architectural decision.

  1. Outage

    Nobody called you to bring the system back up.

    The architecture is offline-first: when the system cannot reach the cloud, the field keeps working. An outage is not a fault; it is the state the design assumes.

  2. Line

    You did not have to explain traffic without a network.

    Devices talk through one another, and the traffic is end-to-end encrypted: a relaying device cannot read the content.

  3. Data

    You did not go looking for where the data went.

    Your data is hosted inside Türkiye, under your own jurisdiction; you chose where it lives at setup. Sovereignty is not handed over.

  4. Record

    You did not guess who did what.

    Audit logs record events as they happen. Nothing is collected after the crisis: it is already there.

  5. After

    You did not write a separate recovery plan.

    When the connection returns, the waiting data settles into place. Recovery is not a task; it is the architecture continuing.

What changes

  • You do not step in when the network drops.

  • You do not go looking for where the data went.

  • You do not have to trust the relaying device.

  • You do not guess who did what.

What matters from where you sit

This page asks the question; the depth of the answer is below.

Let's talk about your organisation's resilience.

See E-Afet applied to your own scenario in a 30-minute demo.