Harsha Chintalapani

🚀Excited to share how @CollateData 's $10M Series A accelerates @open_metadata open source mission → Faster release velocity → More Product Development and community support → Renewed investment in open core Read more in the OpenMetadata blog: blog.open-metadata.org/collate-raises…

Supply chain attacks and OSS sustainability go hand in hand. I've semi-seriously joked for years that OSS upstreams should periodically purposely inject full vulns into their code and let downstreams fuck around and find out. Downstreams can pay to get the non-FAFO version. The not joke part is simply that OSS maintainers aren't a supply chain. OSS maintainers are not responsible for monitoring CVEs (because, they are not a supply chain). OSS maintainers are not at fault when bad shit happens to downstreams, because basically every OSS license (MIT, Apache, GPL, etc.) literally says: the software is provided "as-is, without warranty." You get what you pay for (that is to say: absolutely nothing!) Now, the joke part is that I do believe there is an ethical obligation to try to prevent harm downstream. But "try" is the key word. So, this isn't a serious proposal. But, if you're using OSS code and you're not paying for a license with a contract that promises some kind of warranty, you have no supply chain. You (the downstream user of an OSS lib) ARE the supply chain. To use a metaphor: physical goods have a real supply chain. Car manufacturers, chips, clothes, toys, etc. You have a signed commercial agreement with all your suppliers that promises quantity AND quality and blowback if either are missed. Thats a supply chain. If someone puts some chips on the side of the road with a "FREE" sign, then you integrate those into a product, then find out those chips are hacking customers, its your fault, not the person who dropped them on the side of the road.

Bragging about how much software you’re shipping with AI is like holding down the shutter button and bragging about how many photos you took.

@Scout24 runs @Collatedata, built on @open_metadata, in production and calls it a "context catalog." AWS, Starburst, Collate. MCPs for GitHub + Confluence. AI-generated docs, human-certified. PII tags propagate from Collate to the query engine for agent-level governance. Angelita Frozza Sanches presents the full build at Collate Summit, June 10. Free: buff.ly/HcxGymJ #OpenMetadata #DataEngineering #AIAgents #ContextLayer

"Data catalog" became a bad word at @Scout24 after their legacy catalog failed. After modernizing with @CollateData, Head of Data Infrastructure and Governance, Angelita Frozza Sanches implemented their "context catalog" The goal: give AI agents and people shared meaning, ownership, and trust signals for every data interaction. She presents the full build at Collate Summit, June 10. Free: getcollate.io/summit2026 #DataGovernance #ContextLayer #AIAgents

Lukas Patzke, Analytics Architect @Airbus is sharing his knowledge on an expert panel at Collate Summit on June 10. "Governance in an AI-First World" Experts will discuss trends in data and AI governance as self-service analytics and self-service AI scales at organizations. June 10. Free. 🔗 buff.ly/HcxGymJ #DataEngineering #DataGovernance #AIGovernance #AIAnalytics #CollateSummit

Lukas Patzke, Analytics Architect @Airbus is sharing his knowledge on an expert panel at Collate Summit on June 10. "Governance in an AI-First World" Experts will discuss trends in data and AI governance as self-service analytics and self-service AI scales at organizations. June 10. Free. 🔗 buff.ly/HcxGymJ #DataEngineering #DataGovernance #AIGovernance #AIAnalytics

Context isn’t optional for enterprise AI. It’s the difference between answers and accurate, trustworthy decisions. This new white paper from industry expert, @mikeferguson1, explores how leading organizations are building AI-ready data foundations with unified semantics and governance 👇 What you’ll learn: → How a unified knowledge graph eliminates semantic chaos and gives AI consistent context → Why AI-powered governance is key to enforcing quality, security, and policies at scale → How to build reusable, AI-ready data products faster with metadata-driven workflows → What a semantic system of record looks like - and why it acts as persistent memory for AI If you’re serious about reducing hallucinations and scaling AI responsibly, this is a must-read. Download here👇 🔗buff.ly/CKxXNq6 #DataGovernance #AI #Metadata #KnowledgeGraph #AIAgents #DataEngineering #SemanticLayer

Most governance failures mean audit findings. In clinical genetics, the stakes are higher. Dan Kostecki from @AmbryGenetics at Collate Summit '26: governed data product lifecycle, PHI-free production environment, CAP/CLIA + HIPAA + FDA Part 11 compliant. June 10 | Virtual | Free getcollate.io/summit2026 #CollateSummit #DataGovernance #DataQuality #DataEngineering #AIinProduction

Before you deploy an AI agent, ask yourself one question: Does your data have an agreed-upon meaning that a machine can actually read? If the answer is no, the agent will guess. Every time. Semantic intelligence is the trust layer that fixes this. It turns metadata into machine-readable context that both humans and AI can rely on. At @CollateData Summit, we're going deep on how to build it. June 10. Free. 🔗 buff.ly/HcxGymJ #SemanticIntelligence #AI #DataGovernance

This Wednesday at 11 AM PDT, our CEO & Co-Founder @suresh_m_s is on stage with @DataSciConnect. The question on the table: as enterprises push AI into production, how do you ensure outputs reflect the right data, tone, and constraints, every time? It's a context architecture question. And the answer is becoming foundational to trustworthy AI. Free. One hour. Worth it. Register here 👉️ buff.ly/7qGVSx3 #ContextLayerAI #DataScienceConnect #SemanticIntelligence #RAG #GenerativeAI #AIAgents #DataGovernance #OpenMetadata

how many times are you guys gonna build this

In this month's Product Demo, Dale Kim and James Nguyen showed how Collate, the enterprise platform built on OpenMetadata, takes you from "I need data" to "here's the data I need, who owns it, and why I can trust it." Your data teams can spend hours hunting for the right datasets, and even longer figuring out if they can trust what they find. You can't succeed with your data initiatives if you're constantly afraid of garbage-in-garbage-out. They covered: * A brief demo of data discovery and trust signals in Collate * Why discovery is only the start, and what else you need to make data usable * A quick walkthrough and discussion of Data Contracts in Collate 👉🎥Watch here: youtu.be/_V1vVyrENDQ #AI #datadiscovery #dataquality #datalineage #datagovernance #dataengineering #datastewards #dateacontracts

AI amplifies ambiguity 100x. "Revenue" means three things across your org. Your agent picks one and returns a confident wrong answer. @suresh_m_s explains why this is an architecture problem, not a model problem: buff.ly/137kQDE #DataGovernance #SemanticLayer #AIAgents #Ontology #ContextLayer

A data steward opened Ontology Explorer for the first time. Two minutes in, she spotted it: Three definitions of Revenue (Finance, Sales, Product) with zero formal relationships between them. Every version was being used downstream, feeding different answers into the same questions. She resolved it on the canvas: → Marked Finance as the authoritative definition → Declared equivalence to the Sales and Product versions → Tagged GDPR governance once at the concept level, which propagated automatically to all 847 implementing assets That's the difference between maintaining a flat glossary and governing an ontology. 🗺️ Collate 1.13 Ontology Explorer is your entire business vocabulary as an interactive graph, with term hierarchies, cross-domain connections, and a Data Mode that traces every term to the data that implements it. Ontology Explorer surfaces coverage gaps instantly. If your catalog has 34 glossary terms with zero relationships, opening the graph makes them visible immediately. Read the details: blog.getcollate.io/ground-your-ai… #Ontology #KnowledgeGraph #SemanticContext #DataGovernance #Collate

OpenAI will share how they built their own internal AI data analyst. Should be a great session!

Hallucinations aren't a model problem. They're a context problem. When AI systems don't have access to the right data, the right tone, and the right constraints at the right time... they guess. Next Wednesday, our Co-Founder & CEO @suresh_m_s is breaking down how leading teams are solving this, with context-aware architecture built for production. The Context Layer: The Emerging Stack for Context-Aware AI 📅 Wed May 13 | 11 AM–12 PM PDT 🎙 @DataSciConnect Joining Suresh: Andreas Blumauer from Graphwise and Donald Spaulding from @Verizon. Free to attend 👇 🔗 buff.ly/7qGVSx3 #ContextLayerAI #DataScienceConnect #SemanticIntelligence #AIAgents #GenerativeAI #DataGovernance #OpenMetadata #AIArchitecture

Hallucinations aren't a model problem. They're a context problem. When AI systems don't have access to the right data, the right tone, and the right constraints at the right time... they guess. Next Wednesday, our Co-Founder & CEO @suresh_m_s is breaking down how leading teams are solving this, with context-aware architecture built for production. The Context Layer: The Emerging Stack for Context-Aware AI 📅 Wed May 13 | 11 AM–12 PM PDT 🎙 @DataSciConnect Joining Suresh: Andreas Blumauer from Graphwise and Donald Spaulding from @Verizon. Free to attend 👇 🔗 buff.ly/7qGVSx3 #ContextLayer #DataScienceConnect #SemanticIntelligence #AIAgents #GenerativeAI #DataGovernance #OpenMetadata #AIArchitecture

Pick any table in your catalog. Try listing, in under a minute, every team that depends on it, every glossary term it maps to, and everything that breaks if the schema changes. Most people can't. That's why we built the new Knowledge Graph visualization. 🔮 OpenMetadata 1.13 renders the full relationship context of any asset in a single interactive view: → Ownership, teams, and domain context → Schema hierarchy, upstream sources, and downstream consumers → Business semantics, plus relationships inferred automatically from your metadata Built on open W3C standards (RDF, OWL, DCAT, DPROD, SKOS, PROV-O, Schema.org) for portability and interoperability. Every AI agent that queries your data, including those through MCP, reasons from the same semantic context graph of ownership, lineage, and glossaries. See your entire data ecosystem in one view instead of digging through spreadsheets and Slack threads. Read the details: buff.ly/EeLgSLB #KnowledgeGraph #SemanticContext #DataGovernance #AIAgents #OpenMetadata

Keynote: "Inside OpenAI's Internal AI Data Agent" @OpenAI built a an AI data agent on @open_metadata's context layer. Tens of thousands of tables, hundreds of petabytes. Any employee: question to insight in minutes. Bonnie Xu (Data Productivity, OpenAI) at Collate Summit '26 | June 10 | Free Register: buff.ly/zRbLuhJ #CollateSummit #DataGovernance #AIAgents #ContextLayer

@OpenAI built their internal data agent on @open_metadata. Bonnie Xu covers the architecture, context layers, and scaling AI-assisted analytics at petabyte scale. Keynote: "Inside OpenAI's Internal AI Data Agent" | Collate Summit '26 | June 10 | Free Register: buff.ly/zRbLuhJ #OpenMetadata #DataEngineering #AIAgents #ContextLayer #DataGovernance