İçeriğe geç
Tres Teknoloji
Services / Managed Cloud

We build, monitor and operate your infrastructure

You don't have to manage the infrastructure yourself. Tres engineers take on setup, monitoring, patching, backup and incident response under contractual service levels; your team gets back to its product.

Schedule a scoping call Sample SLA document
The burden we take on
Setup, hardening and initial configuration
24/7 monitoring and automatic alerting
Security patches and version upgrades
Backup, restore testing and DR drills
Incident response and root cause report

Self-service or managed?

The same infrastructure, two different responsibility models. You can also mix them — production managed, test self-service.

Model 1 Self-service

You create and manage the resource yourself from the panel. Tres is responsible for keeping the infrastructure up; the operating system and above are on you.

Companies with their own DevOps team Fast experimentation and test environments No additional management fee
Model 2 Managed cloud

We set up, monitor, patch and back up the resource. When something breaks, monitoring catches it and our team steps in; the incident report follows afterward.

Companies without a DevOps team or with a growing workload Regulated production environments Measurable SLA and a single point of contact

Packages and service levels

The price is determined by the number of managed resources. Select a card to compare the responsibility matrix and response times below.

Incident priority · first response time Essential Advanced Critical
Critical (P1) Service completely down
1 hour 30 minutes 15 minutes
High (P2) Serious performance degradation
4 hours 1 hour 30 minutes
Medium (P3) Partial impact, still operational
1 business day 4 hours 2 hours
Low (P4) Questions and requests
2 business days 1 business day 4 hours
Responsibility Essential Advanced Critical
Infrastructure and hardware Tres Tres Tres
Operating system setup Tres Tres Tres
Security patches Tres Tres Tres
Monitoring and alerting setup Tres Tres Tres
Backup and restore testing Tres Tres Tres
Incident response You Tres Tres
Capacity planning Shared Tres Tres
Application deployment (CI/CD) You Shared Shared
Application code and database schema You You You
Tres = fully on us · Shared = handled together · You = stays with you

What happens when an alarm goes off?

The process is written down and auditable. A time-stamped record is kept for every incident, and for critical incidents a root cause report is sent within 48 hours.

00:00
Alarm raised The monitoring system catches a metric crossing its threshold and an incident record is opened automatically.
+2 min
Team notified The incident record lands in the team channel and is assigned to the relevant engineer.
+15 min
Response begins The engineer connects to the system and applies an initial diagnosis and temporary fix. A status notification is sent to you.
+1 hr
Escalation If it cannot be resolved, the team lead and, if needed, vendor support step in.
+48 hr
Root cause report For critical incidents, a written analysis and an action plan to prevent recurrence are shared.

Which services do we manage?

Cloud server Bare metal Kubernetes PostgreSQL / MySQL Redis OpenSearch Kafka Nginx / Apache Load balancer Firewall VPN Backup DRaaS Windows Server Zimbra SAP infrastructure
Let us take over your existing infrastructure Even if it's at another provider or in your own data center: inventory assessment, migration plan and transition are on us. The first month runs in parallel.
Schedule a scoping call
S.S.S.

Frequently asked questions about managed cloud

With self-service, keeping the infrastructure up is on us, while the operating system and above are on you. With managed cloud we also take on setup, monitoring, patching, backup and incident response; you focus on your application.

The fee is determined by the number of managed resources and the package you choose (Essential, Advanced, Critical). The Essential package, for up to 10 resources, starts at $140 per month; for critical environments a dedicated-team quote is prepared.

For critical (P1) incidents, first response drops to as little as 15 minutes depending on the package. Times for high, medium and low priority requests are defined in the SLA document and are measured.

Yes. Even if you are on another provider or in your own data center, we handle the inventory assessment, migration plan and transition; the first month runs in parallel.

The moment an alarm is raised, the monitoring system automatically opens an incident record and our team steps in; it applies the initial diagnosis and temporary fix and sends you a status notification. For critical incidents, a written root cause report is shared within 48 hours.

We manage a broad range, including cloud servers, bare metal, Kubernetes, PostgreSQL/MySQL, Redis, OpenSearch, Kafka, load balancers, firewalls, VPN, backup and DRaaS.

For each package we provide a written responsibility matrix (RACI); it clearly defines that infrastructure, operating system, security patching and backup are on us, while the application code and schema are on you.

Customer reviews

What customers who chose managed cloud say

“They took over the monitoring, patching and backup burden entirely; our team now works on the product rather than the infrastructure. The monthly review meetings are very useful to us as well.”
AY Aylin Yücel Director of Engineering · Pusula Ödeme
“They took over our infrastructure from another provider along with its inventory and ran the first month in parallel. We did not experience a single outage during the migration.”
MC Mert Coşkun IT Manager · Deniz Lojistik
“Seeing SLA response times as measurable gave management confidence. The 15-minute response promise in the Critical package held up in the field, too.”
ŞA Şebnem Ak COO · Ege Sağlık Bilişim