Informatica

Matillion Appoints Girish Pancha as CEO

Matillion announced on 2026-08-05 that veteran enterprise data executive Girish Pancha has been appointed Chief Executive Officer and that Sanjay Krishnamurthi has joined as Chief Development Officer. The hires are positioned to accelerate Matillion’s Maia AI Data Automation platform, advancing product, engineering and go-to-market execution as the company expands its presence in Silicon Valley. Pancha brings experience from Oracle, Informatica and as founder/CEO of StreamSets (acquired by Software AG, later sold to IBM). Krishnamurthi’s background includes leadership roles at Informatica, Microsoft (Azure Data Factory and Purview) and Google (Data Integration and Governance). Former CEO Matthew Scullion will remain on Matillion’s board during the transition. Battery Ventures’ Dharmesh Thakker, a Matillion investor, praised the new leadership team.

Governed RAG: Data, Context & Lineage for Enterprise AI

The article describes risks introduced by Retrieval-Augmented Generation (RAG) when enterprise data is exposed to vector search pipelines and proposes a three-part Governed RAG architecture: (1) ingestion with cryptographic embedding lineage and metadata, (2) query-time contextual Attribute-Based Access Control (ABAC) embedded into vector search queries, and (3) outbound payload sanitization (PII/PHI masking, indirect injection removal, and context length minimization). It argues that enterprises must enforce retrieval-time access controls, maintain graph-based data lineage, and implement real-time index freshness/eviction to prevent privilege escalation, prompt-injection attacks, stale-context hallucinations, and to meet compliance requirements.

Microsoft Fabric Apps: Distribution Channel, Not Marketplace

The article argues Microsoft Fabric custom workloads (built with the Fabric Workload Dev Kit) should be treated as a distribution channel rather than a traditional app marketplace listing. Fabric workloads render inside the Fabric shell, operate on OneLake Delta tables, and authenticate via Microsoft Entra ID while backend compute remains on the vendor's infrastructure. That proximity to customer data can materially reduce procurement friction for data-adjacent ISVs, but introduces risks: entanglement with Microsoft's capacity-unit (CU) pricing and potential commoditization by first‑party Microsoft features. The author provides a 90-day, three-step evaluation framework (prototype, CU economics modeling, design‑partner validation) and recommends building on Fabric only when a product's value compounds by sitting next to customer OneLake data.