Red Hat OpenShift in Princeton North, NJ

No — and an estate that tries usually regrets it. OpenShift runs virtual machines natively alongside containers, which is precisely what makes staged adoption possible: each workload is sentenced on its evidence. Containerise where conversion pays (developed, changing, scaling applications); re-host as a VM where the application is stable, vendor-bound or simply not worth re-engineering; retire what the business has already abandoned. The audit typically sentences a minority to true containerisation in the early waves — and that restraint is the method, not a compromise of it: the platform’s value is one governed ground for both worlds, not a conversion quota.

The renewal is the audit’s deadline and usually its funding: the business case is written against the renewal’s real numbers, and the wave plan is sequenced so the estate’s dependence ends before the renewal’s signature is required — with the honest staging caveat that the platform and ambassadors must be proven before the weight moves, so starting early is the entire game. Where a renewal cannot be fully escaped in the first cycle, the audit says so plainly and prices the partial-bridge options; what it will not do is promise a migration winter the estate cannot survive to make a sales quarter. Bring the renewal date to the first conversation; it organises everything.

They are the re-host verdict’s natural citizens: moved as virtual machines onto the same platform, vendor support intact, their ground modernised without their nature being argued with. This is the consolidation the single-platform strategy actually means — the estate’s management, monitoring, security policy and operations unified — distinguished carefully from the containerisation question, which is per-workload and often rightly answered ‘not this one’. Over years, some of these applications are replaced by platform-native successors on their own merits; the platform accommodates that evolution without forcing its calendar.

Ideally, increasingly, you do — with the reliance structured honestly in the meantime. Day-2 operations (upgrades, patching, capacity, health) are carried as a standing service from launch, while the enablement curve runs in parallel: your people paired on the real waves, trained against your platform’s actual configuration, and graduated to the operations they are ready to own, at the pace they actually demonstrate. Some organisations keep the operated model for years by choice; others take the platform fully in-house. Both are designed outcomes — what is refused is the third pattern, dependence discovered at the first upgrade after an abrupt goodbye.

As code, from the first day: image provenance enforced at admission (nothing runs whose origin is unaccounted), access by identity with the estate’s roles mapped, network segmentation expressed as policy rather than as firewall folklore, and the platform’s own configuration held to benchmarked standards continuously. The compliance dividend is structural — the audit file is generated by the platform’s ordinary operation (who deployed what, from which approved image, under which policy), so the evidence the diligence file needs is a report, not a reconstruction. For regulated estates this is frequently the adoption’s second business case, and it is designed into the platform’s build rather than audited onto it afterwards.

Yes — one platform operated identically across the grounds the estate occupies is a standard shape: the same deployment model, the same pipelines, the same policy-as-code, with placement decided per workload by its data, latency and economics rather than by which team owns which ground. The operational gain is the one that matters at 3 a.m.: an incident is one discipline, not two dialects. The design phase maps your actual grounds honestly, including the connectivity and data-gravity constraints that decide what belongs where, and the wave plan treats placement as a per-workload verdict with the same audit discipline as conversion.

In three honest parts: the audit and design (a defined engagement priced from the estate’s scope), the platform build and waves (priced per wave against the audit’s verdicts, so the organisation funds progress it has watched succeed), and day-2 operation (a standing service priced to the platform’s scale). Set against the comparison that usually funds it: the renewal trajectory of the incumbent platform, priced over the same decade, plus the governance cost of the shadow alternative. No licence figures are quoted before the audit sizes the real estate — a platform priced before it is profiled is the monument pattern again, and the audit document is where the honest numbers live.