Your hardware, our brain.
A cloud dedicated to a single tenant, fully isolated. Whether on hardware dedicated to you in the Tres data center or with the orchestrator installed on your own devices — the panel, API and AI are the same everywhere, and your data stays under your control.
You choose where the hardware lives
In both models, the same panel · same API · same AI. The only difference is where the hardware sits.
Hosted Private Cloud
Single-tenant hardware dedicated to you in the Tres data center. Setup, operation and hardware maintenance are on us; you simply use it.
On Your Own Hardware
We install the orchestrator on the devices in your own data center or office. We manage the virtualization; the data physically stays with you.
A turnkey installation project
Not an off-the-shelf product, but a project shaped around your needs. In the first meeting we work out the scope and cost range together.
We map out the workload, capacity, network and compliance requirements, then design the architecture.
We prepare the hardware, install the virtualization layer and the orchestrator, and configure network/security.
We bring the management panel, API/Terraform and MCP access online, and train your team.
Monitoring, backup and updates; 24/7 support and SLA per agreement.
Isolation and sovereignty, by design
A private cloud means you decide where your data sits and who can access it. The right foundation for regulated workloads.
Regulated-industry solutions →Resources are yours alone; no noisy-neighbor effect.
Data stays in the location you choose; in on-prem mode, in your own facility.
Undeletable, off-site disaster recovery with Object Lock (WORM).
Every action is logged; access and changes are traceable.
When control has to stay in your hands
Organizations with data-residency and audit obligations.
Those who want to keep sensitive patient data in their own facility.
Those who want to run existing hardware with a modern cloud panel.
Workloads within KVKK/industry compliance scope.
Those who want self-service via API/Terraform in an isolated environment.
Those who want to manage public cloud + private cloud from a single panel.
In regulated industries such as public sector, finance and healthcare — or in any organization where data sovereignty is critical — the same question comes up: “Exactly where does my data sit, and who can access it?” A private cloud answers that need: a cloud infrastructure fully dedicated to a single organization, isolated and controlled by that organization.
What Is a Private Cloud?
A private cloud is a cloud infrastructure in which all server, storage and network resources are allocated to a single organization — not shared with other tenants, isolated and managed specifically for that organization. In a public cloud, resources are shared among many customers, whereas in a private cloud the hardware is yours alone; there is no “noisy neighbor” effect, resources are guaranteed, and security/access policies are entirely controlled by the organization.
Internationally this model is known as a private cloud. It has two core variants: one hosted in the organization’s own data center (on-premise), and one dedicated to a single tenant in a third-party provider’s data center (hosted). Tres offers both variants on the same management platform.
How Does a Private Cloud Work?
A private cloud is built on virtualization and orchestration technologies. Physical hardware is turned into isolated virtual resources through a virtualization layer and the orchestrator that manages it. The organization manages these resources with a panel, API or automation tools; server creation, scaling, network configuration and backup all happen in this single-tenant environment.
In the Tres private cloud, instead of the third-party hypervisors most competitors use, our own orchestrator and virtualization engine run. The practical result: license cost is not passed through to prices, and the exact same management experience as the public cloud (panel, API, AI/MCP) is delivered in the private cloud too.
The Difference Between Private Cloud, Public Cloud and Hybrid Cloud
The essence of the difference between private cloud and public cloud is who owns the resources and where the data sits.
| Criterion | Private Cloud | Public Cloud | Hybrid Cloud |
|---|---|---|---|
| Resource allocation | Single tenant, dedicated | Multi-tenant, shared | A combination of both |
| Isolation | Full | Logical | Mixed |
| Data-location control | High (with the organization) | With the provider | Mixed |
| Cost model | Dedicated-resource fee | Pay-as-you-go | Mixed |
| Compliance | Ideal for regulation | General-purpose | Flexible |
| Typical use | Regulated/sensitive workloads | Variable, general load | Critical + flexible together |
A hybrid cloud is a model that uses private cloud and public cloud together: critical and regulated workloads run in the private cloud, variable and flexible loads in the public cloud; both are managed from a single panel. Because Tres offers private and public cloud on the same platform, hybrid scenarios can be built naturally.
Tip: “Private cloud or public cloud?” is not an either-or choice. Most mature organizations use both together: personal data and regulated workloads in the private cloud (for data sovereignty), campaign traffic or test environments in the public cloud (for flexibility). The real gain is being able to manage both with the same panel and API.
Regulated Industries: Fintech, Banking, Insurance and Public Sector
In some industries, using a shared (multi-tenant) cloud is not merely a security preference — it is restricted or impossible due to regulation. Financial institutions, payment and electronic-money institutions, insurance companies and public agencies are subject to strict rules on where data is kept, who accesses it and how it is audited.
- Fintech, payment and e-money institutions: standards such as PCI DSS require card data and payment transactions to be processed in segregated, auditable, single-tenant environments. A private cloud’s single-tenant isolation and audit trail make these requirements easier to meet.
- Banking and financial institutions: in Turkey, financial institutions are subject to obligations such as keeping primary/secondary systems within the country under the BDDK’s information-systems regulations. A private cloud on your own hardware, or hosted in a Turkey location, meets the data-residency requirement.
- Insurance companies: industry regulations and the protection of personal/financial data require a segregated and auditable infrastructure. A private cloud lets this data be processed in an unshared environment.
- Public sector and municipalities: to keep data within the country and under audit as required by KVKK and data-residency rules, a domestic private cloud is preferred.
Tip: Infrastructure compliance is not the whole of compliance. Compliance with PCI DSS, BDDK or industry regulations is achieved by assessing all of an organization’s processes, policies and controls as a whole. A private cloud provides the infrastructure foundation that makes this compliance easier (isolation, data residency, auditability). During the compliance process, you can design the infrastructure side together with Tres engineers.
A Full Service Catalog: Not Just Virtual Machines
What sets the Tres private cloud apart is that it offers not just virtual machines but a full cloud service catalog. The orchestrator also manages managed databases (DBaaS — MySQL, PostgreSQL, MongoDB, Valkey), Kubernetes, block/object storage and network services. So even in a private cloud installed on your own hardware, you do not lose the richness of services available in the public cloud — databases and Kubernetes clusters are set up and managed from the same platform too.
Frequently asked questions about private cloud
A private cloud is an isolated cloud infrastructure in which all server, storage and network resources are allocated to a single organization and not shared with other tenants. Resources are guaranteed, and security and access policies are entirely controlled by the organization.
In a public cloud, resources are shared among many customers and offered pay-as-you-go; in a private cloud, the hardware is dedicated to a single tenant, providing full isolation and high control over data location. A private cloud is preferred for regulated and sensitive workloads.
In the hosted model, the hardware sits dedicated to you in the Tres data center and Tres maintains it. In the on-your-own-hardware model, the orchestrator is installed on your devices and the data physically stays with you. In both, panel, API and AI management are the same.
In the hosted model, in the Tres location you choose (Istanbul/KVKK, Sofia, Frankfurt); in the on-your-own-hardware model, in your own facility. Data residency and sovereignty are ensured this way.
Yes. With single-tenant isolation, data residency and an audit trail, a private cloud is a suitable foundation for meeting KVKK and data-residency requirements. In the on-your-own-hardware model, data physically stays inside the organization.
Yes. For fintech, payment and electronic-money institutions, a private cloud — with single-tenant isolation, an audit trail and data residency — makes it easier to meet the need for the segregated, auditable environment required by PCI DSS and financial regulations. The infrastructure foundation is provided; full compliance is completed by auditing the processes of the organization.
Financial institutions and insurance companies are subject to regulatory obligations such as keeping data within the country and processing it in a segregated environment. A shared cloud cannot meet these requirements in most scenarios; the single-tenant isolation and data sovereignty of a private cloud offer a suitable foundation for these organizations.
A private cloud is a turnkey project; the timeline varies with workload, capacity and architecture. A precise timeline and cost range are worked out after the initial discovery and design meeting.
Yes. In the on-your-own-hardware model, the orchestrator is installed on your existing servers; your hardware investment gains new value and is operated with a modern cloud panel.
Not just virtual machines; managed databases (DBaaS), Kubernetes, block and object storage, and network services are all set up and managed through the same orchestrator. Even on your own hardware, you get the full service catalog.
Yes. Because Tres offers private and public cloud on the same platform, you can build a hybrid architecture that runs critical workloads in the private cloud and flexible loads in the public cloud, managing both from a single panel.
Immutable backups with Object Lock (WORM) and off-site disaster recovery are provided; this delivers resilience against threats such as ransomware. Backup and DR policies are designed to your needs.
It is managed with the panel, REST API, Terraform and AI/MCP. The management experience is exactly the same as the public cloud; you can manage the infrastructure with code or in natural language. Every action is written to the audit trail.
It suits public sector and finance organizations with data-residency and audit obligations, healthcare organizations processing sensitive data, enterprise IT teams that want to operate existing hardware with a modern panel, regulated workloads, and organizations that want hybrid scenarios.
Let's build a cloud just for you
Hosted or on your own hardware — let's clarify what you need together. In the first meeting we produce an architecture outline and a cost range.