Compute
Private Cloud
Your own quota, your own gateway and your own identity provider.
Private Cloud Platform Deployment
Bring compute, storage and networking together on one platform in your own data center, without your data ever leaving the building
Compute, storage and networking come together as one platform in your own data center, managed from one console on a single release plan. The team that runs the Nesnet cloud every day installs it, keeps it current and, if you wish, operates it for you.
Why now
Your data can’t leave the building
Regulation, contracts or internal policy keep data on your premises. Public cloud is off the table — yet your teams still want cloud speed.
A new server takes weeks
Every server request travels between the storage, network and virtualization teams. The project waits until the infrastructure is ready.
Three layers, three patch calendars
Virtualization, storage and network gear are patched separately, and maintenance nights grow longer so one layer’s upgrade doesn’t break another.
A hardware refresh is due
With warranties running out, the same budget that would buy another classic virtualization stack could build a cloud platform instead.
What changes
| Today | With Nesnet |
|---|---|
| Project teams file a request for a server and wait for days. | With compute, storage and networking on one platform, one team prepares a new server from one console. |
| Storage, virtualization and network are upgraded separately, and every maintenance window risks a mismatch. | Every layer moves forward together on a single plan of compatible releases. |
| Running out of capacity means a separate storage expansion project. | Add a server and the CPU, memory and storage pools grow together. |
| Incidents bounce between three vendors’ support desks. | One team looks at the whole platform and owns the problem end to end. |
| Only one or two people really know the platform. | Everything is documented and your team is trained; you run it yourself or leave it to Nesnet. |
From today to live: how it works
- 1
Discovery
Your hardware, network, workloads and growth plans are mapped together, along with the order in which applications move onto the platform.
- 2
Design and sizing
Compute, storage and network needs are sized from measurements; redundancy, identity integration and connectivity go into a written design.
- 3
Installation
Virtualization, storage, networking and management are installed as one whole, following the written design.
- 4
First workloads
A non-critical application goes first so your team learns the platform on real work; the rest follow in planned windows.
- 5
Handover or operations
Take the platform over with documentation and training, or leave upgrades, capacity and incident handling to Nesnet.
What you get
A written design
Compute, storage and network needs are sized from measurements, and redundancy, identity integration and connectivity are set out in one design document.
Compute, storage and networking on one platform
Storage is built from the servers’ own disks, networking is defined in the virtualization layer, and everything is managed from one screen.
Built alongside what runs today
The new platform goes in next to your current environment, and workloads move only after validation, in planned windows.
One compatible release chain
All layers are upgraded together with compatible releases, in planned maintenance windows.
Failover and high availability
If a physical host fails, its workloads restart on the remaining hosts.
Documentation and training
Design, installation and operating procedures are handed over in writing, and your team is trained to run the platform on its own.
Why Nesnet
The team that installs it is the team that runs the Nesnet cloud every day; upgrade, capacity and hardware decisions are made there, on measurements.
Example scenarios
A financial institution whose data must stay on site
Situation
Application teams complain that server requests take two weeks, and regulation keeps data inside the building.
Outcome
The platform is installed in the institution’s own data center; one team prepares compute, storage and networking, so requests no longer travel between teams.
A virtualization estate at end of warranty
Situation
Servers and storage go out of warranty in the same year, and the budget is earmarked for a like-for-like hardware refresh.
Outcome
The budget goes to a cloud platform in the company’s own data center instead; Nesnet runs it for the first year while the team prepares to take over.
An IT team juggling three patch calendars
Situation
Virtualization, storage and network gear are patched separately, and every maintenance night runs long so one layer’s upgrade doesn’t break another.
Outcome
All three layers sit on one platform and are upgraded together, with compatible releases and a single maintenance plan.
Who does what
| Nesnet | You |
|---|---|
| Discovery, design and sizing | Data center space, power and connectivity |
| Installing and validating the platform | Hardware or a hardware budget (on Nesnet’s recommendation) |
| Upgrades, patches and compatibility (operations model) | Your applications and data |
| Capacity and incident handling (operations model) | Permissions and internal approvals |
| Documentation and team training | Day-to-day operations in the handover model |
Related products
Compute
Virtual Servers
Linux and Windows servers, live in minutes and self-healing after failures.
Storage
Object Storage
S3-compatible object storage on an S3 server of your own.
Questions to ask before you decide
- Who buys the hardware — can we reuse our existing servers?
- Your current hardware is assessed during discovery. If it fits, it is reused; if not, Nesnet recommends hardware based on the sizing, and you keep the purchase in house.
- Will our running systems be disrupted during installation?
- The new platform is built alongside your current environment and tested empty first. Systems move only after validation, in planned windows, with a rollback step ready.
- Can we run the platform ourselves later?
- Yes. In the handover model the platform passes to your team with documentation and training, and Nesnet can stay on for upgrades only.
- How long will it take our team to learn it?
- Virtual machines, virtual networks and firewall rules are concepts your team already knows; what changes is managing all three layers from one console. Training is part of the installation, and the first workloads move with your team.
- How is this different from the Nesnet cloud?
- The Nesnet cloud is a shared service in the Equinix Istanbul (Dudullu) and Türk Telekom Ankara data centers, with a self-service portal and separate organization spaces. This service installs compute, storage and networking as one platform in your own data center, used only by your organization; the portal and organization spaces are not part of it.
- How is it priced?
- Installation is priced as a project, by scale and scope; operations, if you choose them, are a separate monthly line. You receive a written quote after the discovery call.
Plan your platform in one discovery call
We go through your data center, your workloads and the operating model together, then send a written design and quote.