Summary

  • Fresche's anniversary statement frames a broader data and AI business; the Microsoft expansion began with acquired capability in 2025, not a new deal this September.
  • Application knowledge can support a longer customer relationship, but rule extraction, data lineage and authorized AI answers are different things to verify.

A familiar business number can become unfamiliar when it changes systems. A sales total may look convincing in a new dashboard while carrying a different definition of a completed order. That is the commercial opening in Fresche Solutions' latest strategy: the knowledge needed to modernize an old application may remain valuable long after its interface or code has changed.

In its September 10 anniversary announcement, Fresche, founded in 1976, placed data, analytics and AI alongside its IBM i modernization business. The important development is the breadth of the relationship it wants to sell. The company describes customers moving from an initial modernization project into managed services, cloud, security and analytics. It provides no retention percentage or recurring-revenue figure with which to measure that progression.

Nor is the Microsoft capability newly acquired. The announcement dates the OmniData acquisition to 2025. An official June 2025 article already described Fresche Analytics as an early-2025 launch combining IBM i experience with Microsoft analytics and cloud expertise. This week's statement packages that earlier expansion into a longer-term strategy; it does not establish a fresh transaction.

Knowledge before a new answer

The two ends of the proposition do different work. X-Analysis is described as tracing application dependencies, extracting business rules and documenting IBM i systems, including RPG, COBOL and Synon. The Fresche Analytics MCP Connector, by contrast, builds on Microsoft Fabric to make governed business data available to AI assistants. Fresche says it carries Entra and role-based controls into an experience deployed inside the customer's Azure tenant, complementing Fabric and Power BI.

Those descriptions identify useful control points. They do not establish an automatic path from an extracted legacy rule to a correct conversational answer. Knowing where a value came from, deciding who may see it and agreeing what it means are separate responsibilities. Customer-tenant deployment also does not, by itself, prove that no data can leave, that every interaction is read-only or that an answer cannot be wrong.

Microsoft's documentation makes the scope of one relevant tool explicit. Fabric's lineage view displays workspace items and external upstream connections one level away. Workspace Viewers can see the view but not its data sources. Microsoft also limits its guarantee of correct lineage display between semantic models and dataflows to connections created through Get Data using the Dataflows connector; manually created Mashup queries do not have that guarantee. This is a display limitation, not evidence of corrupt data or a defect in a Fresche deployment.

A portfolio with different clocks

Availability matters as much as breadth. The release says the MCP Connector has already been introduced. It places OpsIQ and the X-Modernize AI Web App in an autumn lineup; the current product catalog still labels OpsIQ as forthcoming. The underlying X-Modernize AI platform dates to November 2025. Treating the platform, a planned web app and an operator assistant as one newly delivered product would overstate the news.

Fresche reports more than 2,200 organizations, more than 800 modernization projects and more than 1,000 roadmaps. These accumulated, company-supplied counts describe scale, not annual growth or a measured conversion rate into AI customers. The market case is plausible without turning those populations into a financial result: knowledge of an existing application creates a reason to stay involved in how its data is later used.

Sources: September 10 company release; 2025 analytics chronology; X-Analysis; current product catalog; MCP service description; Microsoft's lineage scope and limitations.