2026
- January 7 - Introducing EventCatalog v3
- January 8 - Introducing Themes and Dark Mode
- January 8 - Embed IcePanel Diagrams in EventCatalog
- January 8 - Live data meets architecture documentation
- January 9 - Introducing diagrams as first-class resources
- January 11 - EventCatalog now includes a built-in MCP server
- January 15 - Document events at the domain level
- January 21 - Access your EventCatalog from the command line
- January 21 - Document, visualize and discover your data products
- January 29 - Rearrange and save your visualizer layouts
- January 30 - Click any node to explore its connections in Focus Mode
- February 1 - What's new in EventCatalog - January 2026
- February 16 - See your architecture clearly: Major visualizer improvements
- February 19 - The right documentation, in the right place
- March 5 - Your architecture is changing. Do you know about it?
- March 11 - Document examples with your schemas
- March 17 - Which fields are your consumers actually using?
- March 18 - Describe the workflow, let the agent build the flow
- March 23 - Trace every field across your schemas and architecture
- March 25 - Document who consumes your APIs, not just who owns them
- March 30 - Your documentation is a design artifact, not just a wiki page
- March 31 - Whats new in EventCatalog - March 2026
- April 14 - Model external systems in EventCatalog
- April 15 - Your catalog nodes now show what they actually are
- May 7 - Write docs once, serve both humans and AI agents
- May 11 - Giving your AI agents docs they can actually trust
- May 12 - Full-content search comes to EventCatalog
- May 13 - Flows now support containers and data products
- May 19 - Edit your EventCatalog without opening Markdown
- May 24 - Document and Govern AI Agents in EventCatalog
- May 25 - Let tools find your APIs from one URL
- May 26 - Your architecture decisions belong next to your architecture
- May 27 - Sync users and teams from GitHub into EventCatalog
- May 31 - Whats new in EventCatalog - May 2026
- June 16 - How to turn C4 diagrams into EventCatalog documentation
- June 22 - Bring live data into EventCatalog
- July 2 - Introducing EventCatalog v4
- July 9 - Add custom dashboards, tools, and APIs to EventCatalog
- July 21 - Scope your MCP server to a domain or system
- July 31 - Whats new in EventCatalog - July 2026
- August 27 - Schema registry vs Architecture Catalog
- August 27 - Introducing EventCatalog Federation v2
- August 31 - Whats new in EventCatalog - August 2026
- September 23 - EventCatalog 4.12: schemas your consumers can actually use
- September 24 - Introducing EventCatalog v5: One product, everything included
- October 13 - One diagram, three levels of detail
- October 14 - Your architecture diagrams, inside your agent
- October 15 - See who owns every step of a flow
- October 16 - Introducing EventCatalog Studio (v2): design what comes next, together
- October 17 - Share your architecture with anyone: export your catalog as one HTML file
- October 18 - Introducing Architecture Fitness Functions for EventCatalog