Comment by Mandatum

As a consultant, I love this.

As an employee however; nobody on my team, nor my projects, nor my wider organisation will spend the time to keep these updated.

We can barely keep public-facing API documentation up-to-date. Diagrams like this are an order of magnitude harder to keep up-to-date, and Solution Architects will refuse to go to this level of detail, as they'd actually have to think through the problem and do some actual system design.

But as a consultant, I'm going to use this in my kick-off projects and my proof-of-concepts, and it's going to dazzle everyone. But maybe 5% of my clients would pay me to do detailed diagrams or documentation like this.

EDIT: OK, unfortunately the initial onboarding is overwhelming and underwhelming at the same time. I'm used to ArchiMate, I'm used to draw.io, I'm used to Visio, I'm used to plantUML. You've taken some of the existing design patterns but made them different enough it feels uncomfortable.

The initial onboarding needs significantly more work. Dumb down the default, initial view. I don't need "Start Trial", I don't need "Help", I don't need "Invite", I don't need "Embed", I don't need whatever the fuck "Landscape recommendations" is, I don't need wait what the fuck is "Link to reality" and how is it different to the "Share" part of "Embed and Share"? Why is there some sort of animal I can't make out with a party hat on it next to it? Oh Link to reality is a "fun" play on syncing with a backend repo.