EventCatalog

The open source documentation tool to bring discoverability to your architecture.

[David Boyne 🚀 @boyney123]

I built a new thing for EventCatalog.

A local editor to help you write your event-driven architecture documentation. Slash commands, flow editor and more.

Hopefully can help folks using @event_catalog

[Yuri Melo (El Yosemite) @theyurimelo]

The most useful tool in Software Architecture is @event_catalog from @boyney123

Are you suing in your project?

[EventCatalog @event_catalog]

Your documentation is starting to serve two audiences.

We added more components to help you write architecture documentation for your team and your AI agents.

https://t.co/rZwHkQ01V8

[David Boyne 🚀 @boyney123]

The TipTap editor is so much fun to play with!

It can provide so much flexibility. Here I'm creating custom slash commands for mermaid and node diagrams for users, so they can embed them directly into their docs. Combine this with MDX and it feels like super powers!

This editor will focus on software architecture primitives and let you document your architecture on @event_catalog and publish them too.

[David Boyne 🚀 @boyney123]

What if you could see which properties of your events are actually being consumed/used by downstream consumers?

This is something I'm playing with at the moment.

1. Specify your producers/consumers
2. Allow consumers to document important properties of schema
3. Bi-directional with Code <> Documentation with Schema Agent

Quick demo below.

[David Boyne 🚀 @boyney123]

Got an AsyncAPI or OpenAPI file?

I created a quick tool that let's you see what @event_catalog can do. Visualize and document your architecture.

Open source and local first ❤️

(link below).

[EventCatalog @event_catalog]

Focus mode now live 🚀

Click on any node in the visualizer, to see the inputs and outputs. Then traverse through them to understand the bigger picture.

[EventCatalog @event_catalog]

You can now embed @ice_panel into EventCatalog ❤️

https://t.co/kp5faGvczW

[EventCatalog @event_catalog]

You can now reference any resource using bracket syntax (e.g [[service|OrderService]]).

Just add this in your markdown, and your teams can hover over these items to quickly see information about that resource (e.g Schemas, Summary, links to docs, visualizer).

[EventCatalog @event_catalog]

@astrodotbuild Congrats on 2025 Astro!

We moved away from NextJS to Astro in 2024 and have not looked back.

What a great project and community you have.

Here is to 2026 ❤️

[EventCatalog @event_catalog]

https://t.co/nlO0yz776s

[EventCatalog @event_catalog]

You can now bring your own diagrams to EventCatalog.

Version them and compare them.

Any diagram support (mermaid, plantuml, IcePanel etc).

Copy to clipboard for LLMS.

Link below 🐱

[EventCatalog @event_catalog]

Embed and version your architecture diagrams, compare them side by side.

New idea 💡

[EventCatalog @event_catalog]

EventCatalog v3 is now out 🚀

https://t.co/2eYmEDzcp7

[David Boyne 🚀 @boyney123]

Wow, some great performance improvements coming to @event_catalog v3 🤩

You can already try out v3 in the latest beta version, also a link below to test it out 💪

Build with @astrodotbuild the GOAT 🐐

[David Boyne 🚀 @boyney123]

Slightly late, but here is what's new in EventCatalog for October

tl;dr

⭐️ We added the schema explorer to help teams save time
⭐️ Data stores were added to EventCatalog (e.g Databases)
⭐️ Fetch OpenAPI, AsyncAPI and GraphQL specs from remote urls
⭐️ Get access to your specifications/schemas using the MCP Server
⭐️ Transform your event storm into EventCatalog using the MCP Server

https://t.co/k7IEMABUzl

[David Boyne 🚀 @boyney123]

This thing is now live.

You can sync your Azure schemas with your docs, useful if you want to get more value from your schemas sat in Azure

https://t.co/NZ3guFPjMB

[David Boyne 🚀 @boyney123]

EventCatalog supports any schema format (e.g Proto, Avro, JSON, OpenAPI, AsyncAPI, GraphQL), and I wanted people to get more value from documenting their schemas.

I'm building a new "Schema Registry" feature to EventCatalog which will let you:

🔎 Quickly find any schema in your architecture
✅ View diffs between all versions of your schemas
📦 Quickly find producers/consumers of your schemas
👨🏼‍💻 Get access to your schema through API
📔 Schemas.txt URL for your LLMs to find schemas they need
🤖 New MCP tools to get schemas in your architecture

Here is a quick demo so far, and hopefully out this week👇

[David Boyne 🚀 @boyney123]

The past 12 months of @event_catalog has been an emotional journey.

November 2024 I decided to go full time on an open source project and try to turn it into a business..., with no business model, and to be honest no idea of how to do any of this...learn on the fly.

I acquired my first paying customer in November (the first is always an amazing feeling), pushing me to about £80 MMR 😅, continued to dig into savings to try and make all this work.... (for the next 6 months)

Plenty of highs and lows, but something in my gut told me to keep going... it's a shit show out there with architecture documentation.... and I'm glad I did.

I'm super happy to share the project now has almost 30 paying customers, which is an amazing feeling. 30 companies putting their trust into my vision and product and helping their organizations ❤️

For large companies 30 customers is a small number... but for me as a bootstrapped founder, it's means everything.

I'm sharing this with you all, as I enjoy learning and sharing in public, and hopefully somewhere out there it inspire others to also make a jump, trust yourself and your gut. It's amazing what can be done if you just believe in yourself and your vision.

Heres to the next 30 customers ❤️🙌

[EventCatalog @event_catalog]

You can now add Data Stores to EventCatalog.

This let's you document your database, caches, indexes and much more.

Visualize how data flows in your architecture, and what services read/write to it.

https://t.co/FVGtr0chLx