Technologies · Software-Defined Data Center

Run your infrastructure from one platform, with one team

Compute, storage and networking stop being separate worlds, so making room for a new workload no longer waits on three teams.

Classic data centerServersOwn management consoleOwn patch calendarOwn specialistStorage systemOwn management consoleOwn patch calendarOwn specialistNetwork devicesOwn management consoleOwn patch calendarOwn specialistManagement in one placeIntegrated platform · one body of softwareServersCPU · memoryStorageThe servers’ own disksNetworkDefined in the virtualization layerOne patch chainMutually compatibleversion bundlesAdding capacityA new server growsCPU, memory andstorage together

What it means for you

  • Servers ready sooner

    Compute, storage and networking for a new application are allocated from one management console, instead of travelling through three teams’ queues.

  • Fewer maintenance nights

    Every layer is updated with compatible bundles, so maintenance stops dragging on because of version mismatches.

  • One team to call

    When something goes wrong, nobody bounces between three vendors’ support desks; one team looks at the whole platform.

How it works, at a glance

  1. 01Adding capacity becomes rack work.
  2. 02Patching moves as one chain.
  3. 03Fault isolation gets shorter.

A classic data center holds three separate worlds: servers, a storage system and network devices. Each has its own management console, its own patch calendar and its own specialist. Making room for a new workload means working through all three worlds separately — and that turns into weeks of effort.

On an integrated cloud platform, those three layers run as a single body of software: storage is the servers’ own disks; the network is defined in the virtualization layer; management sits in one place. In concrete terms:

Adding capacity becomes rack work.

When a new server is slotted in, the CPU, memory and storage pools grow together; there is no separate storage expansion project.

Patching moves as one chain.

Virtualization, storage and network versions are updated as mutually compatible bundles; version-mismatch labor disappears.

Fault isolation gets shorter.

Instead of bouncing between three vendors’ support desks, you look at one platform as a whole.

The Nesnet cloud runs on this architecture — and the same architecture can be installed in the data centers of organizations that want it in-house.

Frequently asked questions

Will I face downtime while my existing servers are moved?
Moves follow a plan: an inventory comes first, a non-critical system is migrated as a pilot, and the real cutover happens in a window you choose. How long a system is offline depends on its size and the migration route. Servers from another virtualisation environment can be uploaded as OVA files, or running servers can be moved with migration tools.
Will I face downtime while moving my existing virtualisation environment?
Migration follows a plan: an inventory comes first, a non-critical system moves as a pilot, and the main cutover happens in a window you choose. Servers can be uploaded as OVA or moved while running with migration tooling. Downtime depends on the size of the system and the route chosen, and the rollback step is written before the cutover.
Will the invoice hold any surprises?
The invoice is made up of vCPU, memory, NVMe storage, gateways, load balancers, public IPs and internet bandwidth, each on its own line. The number of servers you create inside your quota doesn't change the price on its own; the resources you use do. Nesnet's team prepares the actual figures for your needs.

Contact us

Planning a project or a migration, or have a question about a service? Fill in the form or call 0800 606 1071; we respond within the same business day.