We have been using Mermaid for around 11 months in our CargoX logistics platform work, mainly to create and maintain diagrams that explain complex business and technical processes. What I like most is that we can create diagrams directly from text-based code instead of manually drawing every element.

For CargoX, this has been particularly useful for mapping the complete shipment lifecycle, from creating a shipment request and receiving offers from shipping providers to selecting an offer, processing the payment, assigning a driver, pickup, loading, transportation, delivery, proof of delivery, and provider payout.

We also use it to document different flows such as payment flows, driver workflows, order states, integrations, and system processes. Because the diagrams are code-based, updating a process is much faster than rebuilding a diagram manually. It also makes it easier for our team to keep diagrams consistent and include them alongside technical documentation and project files.

Another thing I appreciate is how quickly a rough process can be turned into a readable diagram. For complex logistics workflows with many steps and decision points, this saves a significant amount of documentation time. Review collected by and hosted on G2.com.

The main limitation we have encountered is that large diagrams can become difficult to manage visually. As our CargoX workflows became more detailed, a single diagram could contain many nodes, decision points, integrations, and different actors, which sometimes makes the final diagram crowded.

It also takes some time to get comfortable with Mermaid syntax. Small syntax mistakes can prevent the diagram from rendering, so when working on a large diagram, troubleshooting the exact line causing the problem can be a little frustrating.

For highly detailed diagrams, I sometimes prefer splitting one large workflow into several smaller diagrams rather than trying to represent the entire process in one view. Review collected by and hosted on G2.com.