A database that keeps changing hands
Rocket Software announced in February 2026 that it would acquire Vertica, the enterprise analytics database platform, from OpenText, and completed the purchase in May 2026 in a deal funded from Rocket's own balance sheet. Financial terms were not disclosed. Rocket inherits more than 600 global customers and 170 employees who build and support the platform, along with a product that has quietly become a case study in how often enterprise infrastructure can be bought and sold without its end users having much say in the matter.
Vertica's lineage is the real story here. It began as a columnar analytics database built for high performance queries, was acquired by Hewlett Packard, spun out as part of Micro Focus, absorbed into OpenText when Micro Focus was acquired in 2023, and has now landed at Rocket Software. Four owners in a bit more than a decade is an unusual amount of corporate turbulence for infrastructure that enterprises typically expect to run quietly in the background for years at a time.
What Rocket says it is building
Milan Shetti, Rocket Software's president and CEO, described the acquisition as a way to deliver a truly end to end modernization experience, pairing Vertica's analytics and generative AI capabilities with Rocket's existing data and content products, DataEdge and ContentEdge. The pitch is coherent on paper: enterprises running legacy mainframe and midrange systems, which is Rocket's core customer base, get a modern analytics layer that can run directly on their trusted core data without a separate migration project.
Devin Pratt, research director for data management at IDC, offered a more measured outside view, saying Vertica strengthens Rocket's ability to support enterprises working to modernize their core systems. That is a reasonable assessment of strategic fit. It is also, notably, the only third party voice in the announcement. Neither Rocket nor OpenText put forward a customer quote describing what this transition means for day to day operations, support continuity, or roadmap priorities.
The pattern underneath the deal
Vertica is not an isolated case. Analytics databases and data warehouse technologies have become attractive acquisition targets precisely because they generate durable, sticky revenue from customers who are expensive to migrate away from once years of queries, pipelines, and dashboards are built on top of them. That stickiness makes them valuable chips in portfolio reshuffling for serial acquirers like OpenText and consolidation specialists like Rocket, even in cases where the underlying technology itself is not the acquirer's primary growth engine or strategic focus going forward.
For OpenText, divesting Vertica fits a broader pattern of trimming non-core assets after a string of its own acquisitions, including its 2023 purchase of Micro Focus, the company that owned Vertica at the time. For Rocket, which has built its entire business on acquiring and stabilizing legacy enterprise software that larger vendors no longer want to carry on their own books, Vertica is a logical and well rehearsed fit. Neither motivation is secret or improper on its face. But it does mean Vertica's product roadmap has been shaped more by successive owners' portfolio strategy than by sustained, independent investment chosen on the product's own merits.
What 600 customers are actually weighing
Enterprises running Vertica today are being asked, for the fourth time, to trust a new parent company's support commitments, pricing, and long term roadmap. Rocket's history of acquiring and stabilizing orphaned enterprise software, rather than acquiring and gutting it for parts, is a genuine point in its favor relative to some private equity consolidators. Rocket's prior 2024 integration of OpenText's Application Modernization and Connectivity business also suggests it has practiced playbooks for absorbing products like this without immediately breaking them.
That track record does not eliminate the underlying risk. Every ownership change resets the clock on whether a vendor will keep investing in a platform at the pace its customers need, especially against competitors like Snowflake and Databricks that are shipping new AI and lakehouse capabilities on a near monthly cadence. Vertica customers now have to decide whether Rocket's stability narrative is durable enough to justify staying, or whether four owners in ten years is itself the signal to start planning a migration on their own timeline rather than someone else's.
Why this matters beyond Vertica
The lesson generalizes well past one columnar database. Analytics and data warehouse platforms are infrastructure decisions meant to last five to ten years, which is exactly the window in which software consolidation plays out. A platform that looks stable and well supported at the time of purchase can change owners two or three times before a single contract renewal cycle completes, and each change carries real risk to support quality, pricing, and feature velocity even when the new owner says the right things publicly.
This is not an argument against ever buying from a vendor that could plausibly be acquired, which by now realistically describes most of the enterprise software market, including the largest and most established names in data infrastructure. It is an argument for pricing that acquisition risk explicitly into procurement and architecture decisions from the outset, building in contractual protections and portability where possible, rather than discovering the risk only after the fact, when a routine status update email announces that your database vendor has a new corporate parent and a new set of priorities to match.
The decision for the reader's roadmap
Before standardizing on any analytics database or data platform, ask the ownership history question directly: how many parent companies has this product had, and what happened to its roadmap and support quality at each transition. A vendor with a clean, stable ownership history deserves a premium in evaluation scoring over one with Vertica's résumé, all else being equal, because that stability is itself a form of reliability that engineering teams depend on just as much as uptime numbers.
If you are already running Vertica, use this transition as a forcing function rather than a background event. Get explicit, written commitments from Rocket on support SLAs, pricing stability, and roadmap priorities before your next renewal, and keep a live option on the shelf in case those commitments do not hold. Infrastructure that has changed hands four times has earned the right to a more skeptical renewal conversation than infrastructure that has not.
