Solix: Switch off the software. Keep the memory.

The expensive thing about an old billing system is that somebody may still need one old bill. A company replaces its software, moves its daily work elsewhere, and discovers that the previous application has acquired a second career. It is now a very elaborate filing cabinet. Licenses, servers, support: the cabinet keeps sending invoices of its own.

Solix Technologies, Inc. works in that awkward interval between replacing software and actually being rid of it. The company sells data management software and implementation services, with archiving at the heart of its story. Its proposition is straightforward: keep the information people need without keeping every machine and application that once handled it.

The search that nobody would buy

Founder and CEO Sai Gundavelli came to the problem through enterprise applications. He had worked at Cisco and built a business implementing corporate software. In a 2015 interview with Sramana Mitra, he recalled trying another idea: bringing Google search into enterprises. Prospective customers liked the technology. The purchase order was another matter.

“We don’t even know what data we have.”

Customer response recalled by Sai Gundavelli, 2015

That objection changed the assignment. A search tool assumes an organization knows what it wants to search. Gundavelli’s customers needed help identifying and organizing the underlying information. He moved toward enterprise data management, beginning with archiving. The original pitch had found interest; the revised one found an operational problem tied to spending.

Early traction came from Oracle and PeopleSoft environments, he said. Accumulated history made backups longer and recovery harder. In the same interview series, he described financing Solix with his own money and angel funds. The current company dates its founding to 2002. Its expertise grew around the peculiar contents of enterprise systems: relationships, exceptions, and records that cannot simply be discarded.

A billing screen gets a second life

A Solix utility case study makes the work unusually tangible. The project retired two custom legacy billing applications. Solix and Kyndryl collaborated on delivery, using a private tenant on Google Cloud. Historical information moved into the new environment. Customer service representatives still needed a practical way to look up those old bills.

The answer included a React and Node.js interface that preserved a nearly identical experience to the old mainframe screens. That detail matters. A technically successful extraction can still leave an employee stranded. Here, the access layer respected the routine the employee already knew. The records changed homes without requiring every lookup to become a small investigation.

The PDF estimates savings above $1 million and projects payback in less than a year. Those are business-case figures, not a published customer invoice. For a buyer, the useful calculation includes extraction, validation, replacement access, archive operation, and the spending that genuinely disappears when the original applications close.

The archive has neighbors

Solix’s Common Data Platform, or CDP, provides the foundation for managing structured and unstructured enterprise information. Application retirement is one use. Database archiving addresses another: moving less-active history away from production while the application keeps running. American Tire Distributors appears in a Solix case study whose title reports a 25% reduction in its Oracle EBS database.

The surrounding portfolio includes email and file archiving, Data Lake Plus for data management and analytics, Enterprise Content Services for documents and collaboration, and governance capabilities such as discovery and masking. These products serve related jobs, but buyers should start with the job they actually have. An invoice archive and a document workflow have different tests of success.

The customer pattern is large organizations with complicated histories. Solix displays names including PepsiCo, Citigroup, and Kaiser Permanente. Another vendor case study reports 95 applications retired and more than 75TB archived for an unnamed Fortune 50 food and beverage company. In this market, alternatives include IBM InfoSphere Optim, OpenText InfoArchive, and Informatica Data Archive. Solix’s pitch combines preservation, governance, cloud delivery, and business access.

There is a practical distinction in the sales model, too. Software supplies the controls; services handle the local complications. Solix’s retirement services describe inventory, a cost baseline, validation, user training, and a decommission runbook. A customized ERP system can contain years of decisions that never made it into a manual. Discovering those decisions is part of getting the archive right.

Now ask the archive a question

On July 30, 2026, Solix announced general availability of Data Sense and Data Ask. Data Sense builds semantic context, including an Application Knowledge Graph describing business objects and relationships. Data Ask supplies a natural-language interface across structured records and documents. The announced features include permission-aware access, cited answers, and clarification when a question is ambiguous.

The connection to archiving is sensible. A historical record becomes more useful when a person can ask about it without reconstructing its database schema. But this also raises the standard for preservation. An answer depends on context, permissions, and the relationships between records. A conversational interface still needs the company’s accounting and operational meaning underneath it.

The shutdown is the finish line

SOLIXCloud uses pay-as-you-go monthly subscriptions, alongside enterprise deployments and implementation services. The repeatable lesson is to inventory an application, cost its continued operation, establish what must survive, and test retrieval with the people who use it. Solix’s stated values put customers and collaboration first; retirement projects make those priorities quite literal.

The approach fits applications kept mainly for history. A system still processing necessary transactions needs a migration or replacement before retirement. Missing relationships, untested access, or unresolved retention requirements can also defeat a shutdown plan. The revealing question for any demonstration is ordinary: can the employee find the old bill, with the right permissions, after the original application is gone?