AI and automation

What are data residency and on-premise?

Data residency refers to which server and in which country data is kept, and on-premise means running software on the company's own server.

A workplace related to Data residency and on-premise
In short

In a cloud setup, the software runs in the company's own cloud account. In both cases data stays under the company's control without leaving for a third party's system. A Panda agent is set up on the customer's own server or cloud account; it connects to ERP only with the access granted.

What you need to know about Data residency and on-premise

Data residency and on-premise: Why does data residency matter?

Why does data residency matter?

Accounting, customer, production and price information is a company's sensitive data. Where data sits determines who can access it, which legal regulation it falls under and how it will be audited if a problem arises. For personal data, KVKK (Turkey's data protection law) requirements also concern transfer abroad. That is why many businesses prefer to run AI and automation tools in their own infrastructure. This is one of the first questions to ask when choosing an AI solution, especially when working with sensitive information such as accounting and customer data.

Data residency and on-premise: On-premise and cloud options

On-premise and cloud options

In an on-premise setup, software runs on the company's own server; maintenance, backup and security are the company's responsibility. In a setup in your own cloud account, the software runs in the company's subscription account and the infrastructure is left to the cloud provider, but access and data stay with the company. The choice depends on budget, the IT team, internet infrastructure and sector rules. Panda's agent and flow solutions are installed on the customer's server or on their own cloud account. In a cloud account setup, access keys and network rules are under the company's control; responsibility for backup and monitoring should be written clearly in the contract.

Data residency and on-premise: What to watch out for

What to watch out for

Before setup, classify the data: which tables and documents are open to the agent for reading. Define read and write authorities separately. Appoint a person responsible for backup, updates and access logs. If any components use external services, ask in writing which part of the data goes out. For KVKK and sector regulations, get the opinion of your legal and information security teams. Put in writing in the contract who is responsible for updates, backup and monitoring after setup; ambiguity costs time when a problem occurs.

See how Data residency and on-premise would work in your business

Tell us briefly about your process and we will walk through the screens with your own example.

  • Reply the same business day
  • 15+ years of experience
  • 90 client businesses

What does Panda AI do here?

Panda AI runs on your server or in your cloud account and connects to ERP only with the access granted. Data does not leave the company.

Frequently asked questions about Data residency and on-premise

What is the basic difference between on-premise and cloud?

On-premise software runs on the company's own server. In the cloud, software runs on a cloud provider's infrastructure. A Panda agent setup can be done under the customer's control in both.

Is data residency related to KVKK?

Yes. Where personal data is stored and whether it is transferred abroad are assessed under KVKK. Consult your legal adviser for your own situation.

See Data residency and on-premise with your own data

Describe your process in a few sentences and we will show you the modules that fit.

  • 15+ years of enterprise software experience
  • In the cloud or on your own server
  • Processes compliant with KVKK (Turkey's data protection law)