SCNET · Enterprise IT · Ankara, Türkiye

Sanal Çekirdek

We own the architecture and its operation — not a data center.

A managed infrastructure delivery model is a service approach that clearly separates facility, platform, and managed-service responsibilities. Sanal Çekirdek does not claim to own a data-center facility; it selects enterprise-grade third-party facility and platform capacity against workload requirements and remains accountable for the agreed architecture, transition, integration, and managed services.

Facility and physical capacity

Location, power, cooling, physical security, connectivity, racks and access are within the selected facility provider's scope. Sanal Çekirdek defines requirements, evaluates evidence and makes contractual responsibilities clear to the customer.

  • Facility and provider selection
  • Physical access and logistics
  • Connectivity and carrier options
  • Capacity and expansion planning

Platform and cloud layer

Compute, storage, virtualization, networking, security and management components are designed for the target workload. Resource separation, licensing, backup and availability are made explicit in the proposal and design.

  • Virtual servers and private cloud
  • Storage and data protection
  • Network and security zones
  • Identity and administrative access

Managed services

Monitoring, incidents, requests, capacity, configuration, patching, backup and reporting modules are selected according to need. Responsibilities across Sanal Çekirdek, the customer and third parties are documented in a RACI or equivalent matrix.

  • Service hours and communication channels
  • Priority, response and escalation
  • Planned maintenance and change
  • Reporting and service review

Transparent commercial and exit model

Capacity, licensing, facility, connectivity and management are separated commercially wherever practical. Data and configuration handover, migration support, access closure and end-of-service responsibilities are documented contractually.

  • Unit and scope visibility
  • Third-party cost and terms
  • Change and capacity expansion
  • Exit, data handover and secure deletion

How we work

  1. Share the context
  2. Clarify expectations and responsibilities
  3. Build the right expertise model
  4. Set a transparent decision and governance rhythm
  5. Review the outcome together

How success is measured

  • Clarity across facility, platform and service ownership
  • Capacity, performance and backup visibility
  • Supplier escalation and incident resolution
  • Portability and exit evidence

Frequently asked questions

Which data-center provider will be used?

Selection depends on location, capacity, availability, certification, connectivity and commercial terms. The provider and supporting evidence are disclosed in the proposal once validated and included in scope.

Which responsibilities remain with the customer?

Application, data, user, access approval and certain security or patching duties may remain with the customer depending on the service model. These boundaries are explicit in the proposal and responsibility matrix.

How is capacity expanded?

Capacity needs are reported through measurement and forecasting. Additional resources, licensing, connectivity and change plans are approved before implementation. Autoscaling is used only where the architecture supports it.

What happens to data at the end of service?

Contractual handover, retention, backup and secure-deletion conditions are applied. Actions and evidence across third-party layers are coordinated in line with provider terms.

Clarify capacity, management scope and responsibility boundaries in one proposal.

Share your infrastructure requirements