The following slides are from OpenMetadata’s Aug 2026 Community Meetup, held on Wednesday, Aug 26, 2026 @ 9:00 AM PST.
Catch the next OpenMetadata Community Meetup @
https://luma.com/collate
These slides showcase Collate 2.0 and OpenMetadata 2.0's newest features and growth over the years
Star us onGitHub
https://github.com/open-metadata/OpenMetadata
Join our Slack
https://slack.open-metadata.org/
Subscribe on Youtube
https://www.youtube.com/@OpenMetadataChannel
Discover Collate SaaS
https://www.getcollate.io/
3.
Agenda
●Welcome to theOpenMetadata & Collate 2.0 Showcase
●Journey from 1.0 to 2.0; Aug metrics
●Ingestion tweaks and UI improvements and new connectors
●metrics UI, metrics hierarchies, and Context Center
●Search UI, user/agent search improvements, search rankings
●MCP improvements and latest tools
●Q&A
3
How far we'vecome
From a metadata catalog at 1.0 to an open context layer for AI at 2.0 — built by the community, in the open.
476
contributors
from 160+ at 1.0
14,800+
GitHub stars
goal 15k almost!
14,000+
Slack community
from 2,800 ·
130+
connectors
from 60+
13+
Major Version Changes
v1.1 v1.13, then v2.0
→
300+
Merged PRs / Month
Sustained over 3 years!
6.
CATALOG GOVERNANCE INTELLIGENCE
→→
The journey: 1.0 2.0
→
v1.0
May 2023
Catalog foundation
v1.3
Feb 2024
Domains & Data Products
v1.5
Aug 2024
Governance & scale
v1.7
Apr 2025
Lineage UI & impact
v1.8
Jun 2025
MCP server, first-class
v1.10
Oct 2025
Data Contracts + SLAs
v1.13
Jun 2026
Semantic search + graph
v2.0
Aug 2026
Open context layer for AI
7.
Thank You!
The journey:1.0 2.0
→
To every contributor, every question asked, every star
given. Now let's see 2.0!
New Community Connectors
10
RoshanKumar
@itsroshanharry
Michael OURCH
@Michae94
How to Contribute
1. Use the repository skills to
leverage coding agents to
build
2. Assert quality by testing
locally
3. Push your contribution and
we will review it
MCP New Features:
16
●7 new tools - all about context so that LLM answers with richer context
● get_user_context: who is calling: teams, roles, domains, owned assets,
governance gaps.
● get_asset_context: one call: schema, keys, join hints, glossary, articles, metrics,
lineage, DQ
● find_context: ask a business question, get the definitions and the assets they point
to
● search_company_context: semantic search over your own runbooks, FAQs and
policies
● create_context_memory: agents remember preferences and instructions across
conversations
● get_knowledge_content: progressive disclosure: excerpts by default, full text on
demand
17.
MCP Improvement &fixes:
17
● root_cause_analysis now returns 3-5 times smaller payload, after we stopped
embedding raw vectors in lineage nodes
● Lineage graphs are an order of magnitude smaller. Nodes fold into edges, duplicates
collapse, column lineage is opt-in
● Oversized results return fewer whole items and cursor, so content is never truncated
● Wide tables fully supported: get_entity_details pages through columns and returns
descriptions and DDL in full.
● Per-entity permissions enforced on reads: tag, owner and domain based Deny rules
now apply to get_entity_details.
● Stricter write authorization: overwriting an existing entity through a create_* tool now
requires EDIT_ALL, not just create rights.
● Clearer search behavior: semantic_search reports unsupported filters as errors, and
metric results include their expression.
#5 Slide 1 — the hype open. Land the numbers; this is a thank-you to the room.
Stats (gtmos + live GitHub, Aug 2026 vs. the 1.0 'Journey So Far' blog, May 2023): 476 contributors (from 160+, ~3x; goal 500, 24 to go) · 14,800+ stars (goal 15k, met) · 13,500+ Slack (from 2,800, ~5x) · 130+ connectors (from 60+, 2x+) · 13 feature release lines since 1.0 then the v2.0 leap · 557 PRs merged in a single four-week sprint, our peak this year · 50M+ Docker pulls · 300+ PRs/month sustained since before 1.0.
Say: "Before we get to 2.0, look how far this community has come. Since 1.0 in 2023: contributors roughly tripled to 476. Slack grew about five times to over 13,500. Connectors more than doubled to 130-plus. Nearly 15,000 stars. Thirteen feature release lines, and in one four-week sprint this year we merged 557 pull requests. If you've contributed anything — this is you."
Honesty: cumulative total PRs merged and issues closed since 1.0 are still being pulled from the GitHub API — flagged on-slide as [pulling from GitHub API]. Don't quote a made-up cumulative number.
#6 Slide 2 — the dated timeline. Walk it left to right; every date checks out against the OpenMetadata GitHub releases / product-updates log.
Milestones: v1.0 (25 May 2023) catalog foundation · v1.3 (7 Feb 2024) Domains & Data Products · v1.5 (26 Aug 2024) governance & scale · v1.7 (15 Apr 2025) lineage UI & impact · v1.8 (22 Jun 2025) MCP server, first-class — the hinge · v1.10 (8 Oct 2025) Data Contracts with SLAs · v1.13 (8 Jun 2026) semantic search + Knowledge Graph · v2.0 (24 Aug 2026) the open context layer for AI.
Say: "Here's the actual journey. Catalog in 2023. Domains and data products in early 2024. MCP as a first-class service in mid-2025 — that's the hinge from catalog to context. Data contracts with SLAs that autumn. Semantic search and the knowledge graph this June. And 2.0 last week. Three arcs: catalog, governance, intelligence."
Assumption: features are pinned to the release where each landed; v1.5 is a representative 'governance & scale' label for that window. The strongly-sourced anchors are 1.0, 1.3, 1.8, 1.10, 1.13, 2.0.