GoldenrozBook a call

IT infrastructure services for server, virtualization and migration projects with a tested rollback

IT infrastructure services cover the design, build and migration of the servers, virtualization, storage, networks and backup an organization runs on. Goldenroz delivers them as projects for mid-size and large organizations: on-premises, in the cloud or hybrid. Shai, our CTO, scopes and leads each project and is accountable for it, and senior infrastructure engineers he works with do hands-on work alongside him. Every project starts with an assessment. Projects start at $25,000 at a fixed price per phase, and larger programs run $100,000 and up.

From $25,000, fixed price per phase

Updated 2026-11-13. By Shai Goldenberg

Who this is for

  • Organizations whose servers, storage or virtualization cluster are near end of support, or whose hypervisor licence renewal is a reason to reconsider the platform.
  • Companies moving a server room or data center to a new site, to colocation or to the cloud.
  • IT managers who have backups running and have never restored a full system from them.
  • Leadership teams weighing on-premises against cloud and wanting an answer based on their own workloads and costs.
  • Organizations in Israel and abroad that want one named person accountable for a multi-vendor project.

Who it is not for

  • Day-to-day support, help desk and monitoring. That is managed IT services, a separate service.
  • Buyers who need a vendor with published infrastructure case studies or vendor partner status. We have neither to show yet.
  • Hardware or licence resale. We write the specification and you buy from the vendor or distributor you choose.
  • Small offices with one server, and budgets under $25,000.

What is included

  • Infrastructure assessment
    An inventory of servers, virtual machines, storage, network equipment, licences and backups, with the dependencies between them and a ranked list of risks.
  • Target design
    A written architecture for compute, storage, network and backup, with sizing, a bill of materials and at least two options compared on cost and risk.
  • Server virtualization
    Design and build of hypervisor clusters with shared storage, high availability and capacity headroom. Platforms such as VMware, Hyper-V and Proxmox are evaluated in the assessment.
  • Physical servers and storage
    On-prem servers, racks, power, cooling requirements and storage arrays, specified for the workload and installed with documented cabling and labelling.
  • Network infrastructure
    Switching, routing, segmentation, firewall rules, site-to-site links and remote access, designed so that a single failed device does not stop the business.
  • Backup and disaster recovery
    Backup design with recovery targets agreed per system, an off-site or cloud copy, and a restore test that is run and recorded before handover.
  • Migration and cutover
    Server, data center and on-premise to cloud migrations run in waves, with a pilot, a cutover runbook and a rollback step for each wave.
  • Documentation and handover
    Diagrams, configuration records, admin credentials handed to you, runbooks and a working session with your IT team.

How the work runs

  1. Scoping call

    Before the project

    A free one-hour call with Shai about what you run today, what is driving the change and what cannot go down.

  2. Assessment

    First phase

    Inventory, dependency mapping and risk review on site or remotely. You get a written report and a fixed price for the next phase.

  3. Design and plan

    Second phase

    Target architecture, vendor and platform choice, bill of materials, migration waves and the rollback plan. You approve it before anything is bought.

  4. Build and pilot

    Third phase

    The new environment is built and tested, then a small group of low-risk systems moves first to prove the method.

  5. Migration and handover

    Final phases

    The remaining waves move in agreed maintenance windows. The project ends with a restore test, documentation and a session with your team.

Virtual servers or physical servers: when each makes sense

Most business workloads belong on virtual servers. A virtualization cluster lets a few physical hosts run many systems, moves a workload when a host fails and makes backup and recovery simpler. For file services, application servers, internal tools and most databases, this is the default we start from.

Physical servers still make sense in specific cases: databases with heavy disk or memory demands, software licensed per physical core, GPU workloads, systems tied to hardware devices and equipment a vendor only supports on bare metal. A typical result is a virtual cluster for most systems and a small number of dedicated machines for the exceptions.

Server virtualization services and virtualization consulting start with the platform question. Many organizations are reviewing their hypervisor after recent licensing changes. We evaluate VMware, Hyper-V, Proxmox and other options against your workloads, skills and licence costs in the assessment.

Server and data center migration services: how a migration runs

A migration fails when something nobody listed turns out to matter. The work therefore starts with an inventory of every server, virtual machine, database, scheduled job, integration, certificate and IP address, and a map of which systems depend on which.

From that map we group systems into waves. A pilot wave of low-risk systems goes first and tests the method, the tooling and the timing. Each later wave has a runbook with named owners, a maintenance window, checks that must pass and a point of no return.

Every wave has a rollback step that is tested before the cutover. The old environment stays intact until the new one has run in production for an agreed period. This applies equally to server migration services inside one site, a data center move and an on-premise to cloud migration. For continuous IT infrastructure management after the project, see managed IT services. For release pipelines on the new environment, see DevOps consulting.

Backup and disaster recovery that has been restored at least once

A backup that has never been restored is an assumption. For each system we agree two numbers with the business: how much data it can afford to lose and how long it can be down. Those numbers decide the backup frequency, the storage and the cost.

The design keeps several copies on separate media, with one off site or in the cloud and one that ransomware cannot change or delete. Disaster recovery adds a place to run the systems if the main site is lost, which can be a second site, a colocation facility or a cloud region.

Before handover we run a restore test of the systems you choose and record how long it took. We do not publish uptime guarantees. The recovery targets in your design are the commitment, and the test shows whether the design meets them.

Cloud, on-premises or hybrid: honest guidance

Cloud suits workloads that change in size, new applications, teams spread across locations and organizations that do not want to own a server room. On-premises suits steady, predictable workloads, large data volumes that are costly to move, low-latency links to local equipment and data that must stay in a specific place.

Most mid-size and large organizations end up hybrid: some systems stay on-prem, some move to the cloud, and backup or disaster recovery often sits in the cloud. The assessment compares the options over several years, including licences, hardware refresh, data transfer and the staff time each one needs.

We are direct about the evidence. We have no published infrastructure case studies yet, and we do not claim a record of completed migrations onto AWS, Azure or Google Cloud. For a large move onto one of those platforms, we scope the part we can deliver well and say where a specialist partner should lead.

What backs this up

  • One accountable lead
    Shai scopes, leads and answers for each project. Senior infrastructure engineers he works with do hands-on work alongside him.
  • Clear limits
    We have no published infrastructure case studies yet and hold no VMware, Microsoft or Cisco partner status. Vendor choice is made in the assessment.
  • Production systems run by Shai
    Shai runs a production platform of about 237,000 lines of code with 10 CI workflows, and his MCP gateway product installs on-prem at the customer with Docker Compose.
  • Published pricing
    From $25,000 at a fixed price per phase, and $100,000 and up for larger programs. See pricing.
  • You own everything
    Hardware, licences, cloud accounts, credentials and documentation are in your name. You pay vendors directly.

What it costs

Every project starts with an assessment. Each phase after it has a fixed scope and price. Hardware, licences and hosting are paid directly by you to the vendor.

See full pricing

  • Infrastructure project
    Fixed price per phase, starting with the assessment
    From $25,000
  • Larger infrastructure programs
    Data center migrations and multi-site programs over several phases
    $100,000 and up
  • Hardware, licences and hosting
    Bought directly from the vendor or distributor you choose
    Paid by you
  • Scoping call
    One hour with Shai
    $0

Who does the work

CTO and technology partner

Shai leads the technology side: business software, SaaS and mobile apps, payments and escrow systems, Postgres security, AI agents built with Claude Code and MCP, and IT and infrastructure projects with senior infrastructure engineers.

Questions buyers ask

What do IT infrastructure services include?

At Goldenroz they include an assessment of the current environment, a target design, and the build and migration of servers, virtualization, storage, networks, backup and disaster recovery. The work is delivered as a project with a fixed price per phase and ends with documentation and a handover. Ongoing support is a separate service.

How much does an IT infrastructure project cost?

Projects start at $25,000 at a fixed price per phase, beginning with the assessment. Larger programs such as data center migrations run $100,000 and up. Hardware, licences and hosting are not included and are paid directly by you.

Who does the work?

Shai, the CTO of Goldenroz, scopes and leads each project and is accountable for the result. Senior infrastructure engineers he works with do hands-on build and migration work alongside him. You are told who is on the project before it starts.

Do you have infrastructure case studies?

Not yet. We have no published infrastructure case studies and we do not claim vendor certifications. What we can show is the method, the named people on the project, the fixed price and Shai's record running production software systems.

Do you offer VMware consulting, or do you recommend moving off VMware?

We review VMware environments and compare staying against alternatives such as Hyper-V and Proxmox. The recommendation depends on your workloads, licence terms and the skills of your team, and it is made in the assessment. We hold no partner status with any vendor.

How long does a data center migration take?

It depends on the number of systems and how tightly they depend on each other. A migration of a few dozen servers is usually planned in months, and a full data center move can take longer. Each phase has its own timeline, stated with its fixed price.

Should we move from on premise to cloud?

It depends on the workload. Systems that change in size or serve distributed teams usually fit the cloud, and steady workloads with large data volumes often cost less on-prem. Most mid-size and large organizations end up with a hybrid setup, and the assessment compares the options with your numbers.

Do you provide ongoing server management services?

This page covers projects: design, build and migration. Ongoing server management, monitoring and support are offered separately under managed IT services. Many organizations need a project first and steady management afterward.

Guides on this topic

Related services

  • Monthly IT retainer: servers, networks, backups, monitoring, patching, identity and incident support.
  • CI/CD, release engineering, staging and production separation, observability and Docker.
  • A code and database security audit for apps built fast on Supabase and Postgres, with fixes as PRs.
  • Custom software, SaaS, mobile apps, AI and payments, built by a named senior engineer.

Talk to the person who will do the work

One hour, no sales team. You talk to Shai Goldenberg, the CTO, about your systems or your product, and you leave with a clear next step and a price range.

Or send the details

Book a 1-hour consultationWhatsApp us