You can now write fitness functions using @event_catalog for your architecture. Specify architecture rules against your catalog and verify the rules.

You can now export any part of your architecture documentation into a single page. Useful for teams that need to export information for partners or integrations teams. Document with @event_catalog then choose which parts to expose.

What if we could have a Stripe docs experience with an OpenAPI docs look and feel... but for your whole architecture? I've build a new export type for @event_catalog called: Architecture Reference. One single page that contains all your domains, systems, messages, entities, schemas and much more. Document your architecture with EventCatalog, and every build will generate a new reference for you. Perfect for your teams and agents and also personally I think this looks great 🤩 Quick demo 👇 (demo link below) Let me know what you think!

Introducing EventCatalog Studio (v2) A free to use, open source tool to help teams design and plan software architecture. 🎨 Design diagrams with three levels of info 🌎 Collaborate with your team or agents 🔗 Run in your agent (with MCP extension support) ✅ Save offline, export images 💙 Free to use First release of many, coming to EventCatalog Hope it's helpful, (Link below)

This is so fun 🤩 I'm working on improving @event_catalog visualizer, with new layout engines, and ability to drill down into levels (domains, subdomains, services and messages).

Some things I learnt whilst bootstrapping @event_catalog : • Learn and dive deep into your ICP • Focus on value not features • Focus on outcomes not features • Pricing is hard but don't undersell • Distribution is the key • Having an audience helps • Document things for future self + agents + team • Retention > New customers • Obsess on metrics, but not too much • Your gut is often right • Content > Features • Kill features that don't work • Group ICP into buckets, then pricing brackets • You and your business have separate identities (although it never feels like it) • Talk to users over everything else • Focus on simplifying and DX/UX I'm sure there is more, but this shit is the most fun I had and the most stress at the same time 🙃

A nice refresh of vision and direction for @event_catalog ❤️

I'm happy to announce custom pages and APIs for @event_catalog . Every team documents their architecture differently, and I want EventCatalog to flex to the way you work, not the other way around. That's what this release is about: making your catalog more flexible to your needs. You can now create your own pages, widgets, components, navigation, whatever you need, right inside your catalog. Everything has full access to your catalog data, and you're not limited to it either. Your pages can fetch information from anywhere, so you can pull data from your internal systems straight into your catalog. Build dashboards, reports, onboarding journeys, even JSON APIs your internal tools can call. Here's a platform health dashboard built as a custom page, powered entirely by catalog data (image below). Blog and docs linked below, hope it helps those that are exploring EventCatalog!

Worked on a new agent, and working great so far! 1. Reviews code in PR and looks for schemas 2. Works out if schemas are breaking changes 3. Models schemas to producers/consumers with @event_catalog 4. Tells users they will break something if match found 5. Writes breaking change, diagram and list back. This is so much fun 🤩

Been working on pulling real-time data into @event_catalog You can now create custom components, that can pull/sync information from anywhere. Here I pull data from my observability platform and render them into my docs.

C4 diagrams now supported in @event_catalog ❤️

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