# EventCatalog Miro App

Copy as Markdown[View as Markdown](/docs/miro/overview.md)

***

The EventCatalog Miro App lets you bring your architecture artifacts you already documented into Miro — drag services, events, commands, and more onto a board to collaboratively design and explore your systems.

![Panel](/img/miro/getting-started/example.png)EventCatalog Miro Application

Beta — we'd love your feedback

The EventCatalog Miro App is currently in beta. We're actively building new features and improving the experience based on real-world usage.

If you run into any issues, have ideas for new features, or want to share how you're using the app, we'd love to hear from you:

* [Join our Discord community](https://eventcatalog.dev/discord) to chat with us and other users
* [Raise a GitHub issue](https://github.com/event-catalog/eventcatalog-miro-app/issues) to report bugs or request features
* [Contribute to the project](https://github.com/event-catalog/eventcatalog-miro-app) — the app is open source and contributions are welcome

### Why use the Miro App?[​](#why-use-the-miro-app "Direct link to Why use the Miro App?")

EventCatalog helps you document your architecture. Many teams already use Miro to help visualize and model new ideas.

The EventCatalog Miro application helps you model and plan what comes next using tools you already use. Model new services, new events, new connections — you need a space to think visually with your team.

The Miro App bridges that gap:

* **Import your real architecture** — bring services, events, commands, queries, channels, and data stores from EventCatalog into Miro
* **Design collaboratively** — drag resources onto the board, draw connections, and model your next iteration as a team
* **Create new resources** — sketch out new services and events directly in the app before they exist in code
* **Stay grounded in reality** — your board is built from real architecture artifacts, not generic boxes and lines

### How it works[​](#how-it-works "Direct link to How it works")

1. **Export** your catalog from your EventCatalog project
2. **Import** the JSON into the Miro App
3. **Drag** resources onto the board to visualize your architecture
4. **Design** what comes next — add new resources, draw connections, and collaborate with your team

### Supported resources[​](#supported-resources "Direct link to Supported resources")

| Resource        | Description                                    |
| --------------- | ---------------------------------------------- |
| **Services**    | Microservices and systems in your architecture |
| **Events**      | Domain events flowing between services         |
| **Commands**    | Command messages handled by services           |
| **Queries**     | Query messages for reading data                |
| **Channels**    | Message brokers and routing channels           |
| **Data Stores** | Databases and storage systems                  |

### Getting in touch[​](#getting-in-touch "Direct link to Getting in touch")

If you have any questions, feedback, or want to get in touch, please join our [Discord community](https://eventcatalog.dev/discord) or [raise a GitHub issue](https://github.com/event-catalog/eventcatalog-miro-app/issues).