"Creating easy to maintain and easy to consume API and event documentation that is always up to date has been one of the most consistent challenges of my career. EventCatalog has become the keystone tool to finally make it possible"

"EventCatalog is my go to solution when I introduce EDA to an audience."

"When I started to work with EDA 4 years ago, I always wondering how to document events across the organization with easy access and useful for all stakeholders, recently I discovered Event Catalog which has been amazing because it automated the creation of EventBridge event powered by the plugging you created, big thanks!"

"For anyone building Event-Driven Architectures, using EventCatalog is essential. One of the biggest challenges and risks of EDA is the critical lack of discoverability and governance. EventCatalog, together with AsyncAPI and other specs, makes sure your EDA stays controlled, preventing it from spiraling into chaos. Go try now and thank him later."

"I have been working on event-driven architectures and the results have been fantastic, and this was only possible due to strong documentation and event design work. For documentation I highly recommend EventCatalog. EventCatalog is designed exclusively to manage information about events. The platform is very easy to use and clean."

"EventCatalog unlocked the power to visualise events and flows. It simplifies event documentation, providing a clear and comprehensive view of all our events, producers, and consumers. It's the essential tool that was missing in my documentation process."

"EventCatalog does a tremendous job in bringing transparency to our landscape. With it's visualisation features it's easy to identify stakeholders for event changes"

"EventCatalog helps to bridge the gap between a PO's business view and an Engineer's technical view"

"At my current project we have a large event driven architecture setup with more then 100 events in different domains and owned multiple teams. By introducing EventCatalog we can now get a clear view on all the events and schema's and more import who to reach out to if we want to consume data."