Founded in Switzerland in 1997, Magnolia is a CMS used to build composable digital experiences. Magnolia helps create fully integrated customer experiences and speeds up digital delivery of content. Magnolia boasts 480 enterprise customers, thousands of Community Edition deployments, and more than 200 certified Magnolia Partners around the world. They further state that their enterprise customers include Sanofi, Generali, the Atlassian, The New York Times, Harley Davidson, and Union…
$3,500
per month
Miro
Score 9.1 out of 10
N/A
Miro is a web-based Collaborative Whiteboard platform that provides teams with an infinite digital canvas for visual planning, diagramming, and workflow mapping. The platform integrates a spatial user interface with automated drawing tools and natural-language processing (NLP) to structure freeform ideas into defined project workflows and database schemas.
$10
per month per user
Pricing
Magnolia
Miro
Editions & Modules
DX Core
$3500
per month
DX Cloud
$6000
per month
1. Free - To discover what Miro can do. Always free
$0
2. Starter - Unlimited and private boards with essential features
$8
per month (billed annually) per user
3. Business - Scales collaboration with advanced features and security
$16
per month (billed annually) per user
4. Enterprise - For work across the entire organization, with support, security and control, to scale
contact sales
annual billing per user
Offerings
Pricing Offerings
Magnolia
Miro
Free Trial
Yes
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
Monthly billing also available at $10 per month for the Starter plan, or $20 for the Business plan.
Magnolia is a very capable DXP, that provides client with lots of flexibility in composing its own stack. While the core of the platform is a content management system, the open architecture of Magnolia DXP allows it to connect to any platform, allowing client to extend the capabilities. One scenario would be a centralized content hub - where through a single platform, content authors can choose which channel to distribute what content. For example, long form content for consumers viewing on a laptop, short form content for those using a mobile browser. This allow the client to personalized the experience based on channels. Another scenarios would be leveraging on GenAI - using Magnolia's built-in connector to ChatGPT. If that is not the service that one desire, you can always connect to another AI service such as Google Gemini. With GenAI, connected, content author can use AI as co-pilot to help them scale up their content production.
We have used it mostly for documenting our solution, roadmap and as a single source of truth.. It has been very helpful for product management, bridging the gap between developers, solution architects, business teams and compliance. I think Miro board is well suited for product documentation and product management. The talk tracks help us transmit information with an additional layer of understanding. Not sure about scenarios where it is less appropriate. Our use cases are well covered.
Speed of development - time to delivery from zero to MVP was excellent
Ease of use - the authoring experience is very easy to build and train
PAAS/SAAS - the managed service platform removed the traditional overhead of running in-house technologies, meaning we could focus on value add, with less time spent keeping the lights on.
Makes internal coordination between admin team and tutors extremely painless. It's like a single place where everyone can drop ideas, get updates and notes without loss of context which usually happens in long email threads.
Versioning and board history are handled very well, which drastically reduces the workload. They help me track how a policy or math guideline has evolved, and also make it easy to revert changes if something doesn't work.
Comments stick exactly where they are meant to, making internal reviews much clearer. Admins don't have to guess which note refers to which rule or section.
Exports are clean, so even non-Miro teammates get it instantly.
The documentation provides samples that are often out of context, and difficult to know where the provided example code should be implemented. More tutorials providing the full project or step-by-step instructions on how to implement subject material would help greatly. Baeldung is a resource I would consider the gold standard in how this is done in other spaces.
The use of JCR and Nodes makes object serialization/deserialization painful. Jackson compatibility or similar would be a welcome enhancement to the developer experience. Maybe leveraging code-gen from light modules to build model classes when possible could help accomplish this.
Modifying the home layout from light modules is frustrating. It seems that any configuration overrides made merge with the default rather than overwriting, which makes for a difficult combination of guess-and-check while referencing the documentation to see what should be in each row/column when making changes.
Including "mark all as read" or "delete all" in the notifications app would be a great quality of life improvement. It seems that by default, users have to individually select messages and operate them.
Miro saves my day. I would spend at least 4x more time on documenting my projects and work without this tool. It support my day to day role and helps me be successful while saving my capacity. It is not only very easy to start working on it without additional training required, but also adapts to any use case that I might need to implement
We've shown it to a number of users both clients and our own team and despite initial apprehensions, they "get it" very quickly. It's intuitive and friendly and quick to perform daily tasks. We once had a client tell us "Using Magnolia makes me smile" which says it all for us.
Overall it is very intuitive and easy to use. We have new members of the team join all the time and they are able to pick it up quickly and learn it very easily, so that is the mark of a good software product. And although it is so freeform, the library of templates give great starting points and help with ideas to build the boards from scratch.
I have not encountered events where Miro is not available. It is quite nice and reliable to be fair, even on my freemium version (startup) I don't have reliability issues. It does have sometimes where the screen refresh or "freezes" or "consumes a lot of data" and we have to rewind windows and the likes, this instances are very less
I gave [it] 7/10 only because of the loading time of pages. Otherwise, I think it deserves an 8. Normally this is not an issue per [se] but considering the rating matrix and as I have been asked to honestly write about it. Yes, the page loading times could be improved.
I took the loading quickly to be related to availability which I commented on before, so ditto with those comment on load time here. Although to reemphasize, Miro doesn't crash or just refuse to load like some other programs. The weak point of Miro for me is integration of files like Word, Excel, or PowerPoint (especially the later two). When you embed these, it gets slow, and complicated to bring them up while you're in the application.
You always get an answer based on your SLA. But you always get a solution. That's the successfactor in this case. To often i was frustrated about people in a company without even a clue what there product is about or how to solve a problem. Magnolia's Support Team does a very good job and try to help you in most of the cases
We have never reached out to or contacted support because Miro's platform has been incredibly intuitive and user-friendly. The comprehensive resources available, such as tutorials, documentation, and community forums, have provided all the guidance we needed. The seamless integration with our existing tools and the reliability of the platform have ensured that we rarely encounter issues that require external assistance. This self-sufficiency has allowed us to focus more on our projects and collaboration without interruptions. Overall, our experience with Miro has been smooth and efficient, eliminating the need for additional support
There was a series of webinars which Miro hosted with our organization that went over the basics, then progressively became more advanced with additional sections. The instructors were knowledgeable, and provided examples throughout the sessions, as well as answered peoples' questions. There was ample time and experience on the calls to cover a range of topics. The instructors were also very friendly and sociable, as well as honest. Of course Miro isn't a "God-tool" that does absolutely everything, but the instructors were aware and emphasized the strengths where Miro had them and sincerely accepted feedback.
Easy to learn, Miro has a series of videos on YouTube that effectively taught this program to my team members and me. The program is drag-and-drop and works excellently. People pick up on how to use it efficiently, and it's great for organizing ideas more freely. This product is more challenging for some older audiences who are not accustomed to using a touchpad, but for most, it was very easy to use.
I've used several CMSs like AEM and EpiServer, and comparatively, they all excel at different things. Magnolia is the best to develop for/against. Episerver has the best/most fluid UI in terms of content editing, and the overall admin experience AEM is just all around sucks.
Some examples of collaboration software we looked into were FigJam, Mural, and Mermaid. While all three of them are excellent at what they do, either collaboration or diagramming, Miro finds the proper compromise between functionality and usability. FigJam is very user-friendly and convenient for collaboration; nevertheless, it lacks the ability to structure. Mural can be used effectively for workshops, but it is not as straightforward as other tools commonly used. Mermaid is great for creating code diagrams, but it cannot be used for team collaboration. This is why Miro was chosen for our use case.
Maybe is possible now so... Could be useful to manage in some way source code for the projects? not to edit so when we make solutions with different components in MIro, maybe each component could redirect to the source code of this component
Magnolia has brought about positive impacts. For instance, we need not outsource web design and marketing services because thanks to this software, we can handle most work inhouse
The software is affordable with no compromises on capabilities and therefore it is gives us value for money.
This is one of those platforms where the entire team needs to be bought into it, or it doesn't function as intended. Once we achieved that, it's been a wonderful tool for brainstorming and project management internally.
Surprisingly, Miro has not allowed us to reduce software; however, it's a worthwhile addition to our tech stack.
Our team has Miro boards bookmarked, and we know exactly where to go when we have ideas or things that we want to add. It's great to know that we will receive notifications when that happens.
