Mendix Reviews

My company is a service consulting company that works for different customers across the globe. When my company proposes Mendix for a low-code/no-code platform to any customer, or if the customer chooses Mendix, the license will be procured by the customer, and my company will take care of service implementation.

I use Mendix as a solution architect. I'm a low-code/no-code platform solution architect. Whenever a requirement comes to me, particularly one which demands low-code/no-code platform implementation, I use Mendix. For any B2C or B2B mobile app, or B2B or B2C web portal, any sort of headless commerce integration, or any cloud modernization, or SAP ecosystem within a customer, and the customer would like to implement a B2C mobile app, Mendix is an automatic choice because Mendix and Siemens have a very good tie-up or partnership, and it's not only from a business perspective but a technical perspective. Mendix is very much compatible with SAP. When my company sees that there is an opportunity to implement low-code/no-code, it proposes Mendix over other low-code platforms.

What I found most valuable in Mendix is that it's very much suitable for mobile apps such as native Android or IOS supported mobile apps. The multiple features of the platform are very, very attractive and very popular. Mendix has technical features such as microflows and nanoflows. You can also access data models in the platform. These are the features that are very, very strong in Mendix. I got my hands dirty on other low-code platforms, but I have not seen such strong features in them compared to the microflows, nanoflows, and data model access that are in Mendix, including creating and integration. The platform has out-of-the-box adapters or out-of-the-box-connectors that you can integrate with different interface applications such as SAP, Salesforce, Oracle EBS, etc.

Another valuable feature of Mendix is that if you want to connect with any legacy applications, you can write custom Java code because Mendix supports Java, the universal language. My company can write custom code and connect to any legacy or home grown applications for any enterprise ecosystem or IT ecosystem. 

These are the strong benefits I see in Mendix.

I found some issues in Mendix. The platform still has many areas for improvement. If I compare apples to apples, the PWA features of Mendix could be improved, for example, I wouldn't recommend creating a B2C or B2B marketplace or web portals on Mendix, but there's a tendency for people to still do it through the systems provided by my company, particularly implement B2B or B2C marketplace, versus using eBay or Shopify. On the web portal front, Mendix still needs to improve.

Additional features I'd like to see in the next release of Mendix are better BPM modeling and workflow modeling, because their competitor Appian is very, very strong in workflow modeling. Workflow features could still be improved.

RPA features or automation features also need to be added to Mendix. Process Mining and AI email are also additional features that would make the platform better. All these features are offered by Appian, which is a complete package, low-code tool that's a competitor of Mendix. Adding all these features to Mendix would make it more competitive, not just over Appian, but over other similar tools as well.

I have been using Mendix for the last three years.

Mendix is a stable platform. In terms of stability, I'm rating it eight out of ten.

Mendix is a scalable platform. You can scale it up anytime. The platform provides you with much flexibility, and my rating for it in terms of scalability is nine out of ten.

As a premium partner of Mendix, my company is constantly in touch with technical support, plus the Alliance team of Mendix. I am very well connected with the Mendix Alliance team. I find the technical support for Mendix very, very helpful and supportive. Whenever I reach out to the different Alliance people from any geography, I get prompt responses and I find the team very, very helpful.

We are working with different low-code/no-code products, not just Mendix. We have in our practice multiple low-code platforms. We are not only working with Mendix. We are working with our systems such as Hancock and Appian.

The initial setup for Mendix was straightforward. You just have to download Mendix Studio Pro if you are using a desktop computer, and you can create your app very easily. If you are using the cloud version, for example, Mendix cloud or any other cloud, especially as any other cloud is hosting Mendix, it's really easy to access the developer. All partners develop the portal access where Studio and Studio Pro are enabled for my company, so my team can work on any cloud-based application. Setting up Mendix was very easy.

The deployment of Mendix was done in-house. Deployment was not complicated compared to any other local platform. Deployment was very easy. Mendix has cloud architecture for different clouds such as  GCP, AWS, Microsoft Azure, and even SAP Cloud. You just need to follow and you can deploy your Mendix components on cloud-native architecture.

Mendix is not open source, but its license cost is cheap, particularly when compared to the Appian license. The license model would depend on how many users you have and how many applications you are creating. If you are creating a single app, you just need to have a single app license, so it's free. If you want a multiple app license to cover two thousand or three thousand users, for example, internal users or external users, then you need to pay for the license. There's also a license model for above three thousand or four thousand, or five thousand internal and external users. Internal users are the developers who will create different applications using Mendix, while external users are the customers.

Currently, I'm using Mendix. I'm heading the factories of my company low-code/no-code, and my company has Mendix as a local platform in the portfolio, apart from other platforms such as Appian, Hancock, etc. I'm using the latest version of Mendix, but I started with the basic version of Mendix when the platform was newly rolled out, particularly when it was just being offered to partners.

My company has a premier partnership with Mendix, so it has access to the Mendix private cloud. The solution is deployed on a private cloud.

My company has two hundred low-code practitioners using Mendix.

Before advising other people looking into using Mendix, I would check first if he or she is a single developer or a pro developer. A single developer is a business user. Mendix as a tool is very, very suitable for a single developer, for business users who have very little knowledge of programming language, so a single developer can create a quick app out of Mendix.

For a pro developer, or someone already hands-on in terms of different programming languages such as Java, .NET, etc., Mendix could be a piece of cake. For a small shop that needs a small application, the business user or single developer can create small applications, but for a midsize organization or a large enterprise organization, you need pro developers who are hands-on with different programming languages, so a single developer cannot build the app for an enterprise or a midsize organization.

If it's a first-timer pro developer using Mendix, it's a low-code/no-code tool, so he or she doesn't have to bother about the programming language. Mendix provides a visual ID or a visual model, so the pro-developer can just drag and drop based on the programming concept. Through Mendix, the pro developer can also work on the front end, UI forms, and also configure the microflows and nanoflows, and also configure out-of-the-box connectors to connect with different enterprise applications. Mendix is a very easy platform for pro developers.

My rating for Mendix is nine out of ten. It's a pure-play low-code platform, so ideally a low-code platform has some fundamental features, and Mendix has that. It's very much suitable for creating a mobile app, for example, a B2B or B2C mobile app. I recommend it to any customer for their B2C or B2B mobile applications. Any enterprise customer that has a SAP India ecosystem and seeking low-code/no-code platform implementation should go for Mendix.

For the past four months, I have been using Mendix low-code platform, and my main use case involves building standardized business applications.

My experience has been very positive. Mendix stands out for its speed and efficiency, especially for standardized business applications, and its integration with Java and JavaScript allows extending functionality beyond typical low-code limitations.

One of its biggest strengths is strong security, which gives confidence when working on enterprise solutions. For repetitive processes or common business needs, Mendix speeds up delivery without sacrificing reliability.

Customization is limited compared to traditional coding, and UI adjustments can feel restrictive. Native development is not very strong, and some developer tools are missing, such as shortcuts to edit multiple variables. This can make long processes slower and more complex.

I have been using Mendix low-code platform for the past four months.

My name is Gabriel and I work as a freelancer. Mendix does its main job effectively, enabling fast and secure enterprise application development. There is room for improvement in customization and developer tools, but the platform has strong value and growth potential.

I can provide a specific example of a project I have built using Mendix that highlights how it helped me with speed or integration.

I used the solution to develop an application for a parking system. It manages everything from parking cards, payments, eGates, tickets, and more.

The most valuable features of the product are its ease of use and speed. My friend and I find it helpful as a team of just two developers.

One area for improvement is its integration capabilities. Creating a pluggable widget or integrating it with other systems is challenging.

In terms of features, it would be great to see advancements such as AI services and the integration of third-party services. Additionally, connecting external devices to the application requires multiple steps. Improving this will make it easier for the developers.

I have been using the solution for the past three years.

The product is stable and powerful.

The tool is scalable. We had a single application in development, and there were two developers with 15 end users.

Six or seven months ago, I interacted with the technical support team, but since then, they haven't reached out to me. I tried to get in touch with them by asking some questions, and they mentioned that someone would contact me, but unfortunately, no one has reached out yet.

I run my businesses and develop applications. My friends and I are a small group of developers. In the past, we worked with technologies like C# and React. However, we are now looking to take the next step using local platforms.

I switched to this solution because of its database handling. You can create and draw your structure. The UI has powerful microflow, workflow, and nanoflow capabilities. It has great speed. It is suitable for developers with varying levels of experience. You can achieve tasks with minimal coding. The CSS and paging capabilities are great.

The initial setup is not complex. The deployment process took two to three weeks.

I set up the solution on my own.

I would not recommend the solution to small and medium-sized businesses because it’s expensive. It’s great for big organizations. I rate the pricing as a three out of ten.

We have used React.js, JavaScript, C#, and Oracle Siebel. However, we strive to move to the next level for future projects.

Overall, I rate Mendix a six out of ten.

We are using Mendix as a low code or no code solution for creating POC origins for clients.

The most valuable features of Mendix are the drag and drop functions, the data entities, domain models, and all the related features.

Mendix could improve by allowing the customization of different programming languages, such as Python and C++.

In a feature release of Mendix, they should add 3D augmentations or other 3D visualizations, such as images. Additionally, more customizations would be a benefit.

I have been using Mendix for a couple of years.

Mendix is stable and is very good. I have used multiple no code/no code platforms and Mendix is one of the best platforms I have used.

The scalability of Mendix is good. However, whenever we deploy the application, it's heavily weighted on the server. It is not a light solution.

We have approximately 100 people using this solution in my organization.

I have not used the support from Mendix.

The initial setup of Mendix is straightforward.

There is a license required to use Mendix. The solution's price is high, but it is best suited for enterprise companies that have the budget. It is not for small or medium-sized businesses.

There are not any hidden fees but there is a cost for every user that uses the solution. The pricing model can be confusing whether it is user or application based.

Mendix provides an academic course, which is free and I would advise people to take the course. If they take it, then it will be easy for new users to run through the Mendix development.

I rate Mendix an eight out of ten.

I did the certification in Mendix and it was nice and easy to learn first.  Everybody can learn it easily with available resources. Everything is documented properly, from version to version, and is easy to learn. My area of expertise is with enterprise and I sell to clients which are enterprise companies.  

I recommend this solution to others.

I built prototypes with it.

We did not really deploy anything for real clients. We only build prototypes in our local environment, and so far, we do not have any engagements with this platform. It was only for proof of concept projects, and we are still trying to gather engagements to work on if there are existing clients that would provide us with something to use.

The ability to model data and relationships between entities is easy, and the ability to write microflows and nanoflows is great. By that, I mean flows, in general, that achieve something which will function. Those are things I really like. On top of that, they are fast to learn and put into practice after a bit of experience. 

Overall the platform is really good. I like it. I wish I was better at it, as there are plenty of things to learn, especially on the front-end side. I like the fact that you can integrate react widgets. It's really cool. The integration is really good.

The debugger is perfect. It's the best I've ever seen. 

Technical support is great.

You can scale the solution.

It's easy to maintain. 

In the beginning, it is difficult to learn and work with. I have to say it was difficult in the beginning to understand best practices.

Once I got the best practices for the back end part, for manipulating data, it was easier to use. For the front end, it was a bit more difficult. For the front end part, I don't like that it's not fully drag and drop there, and I have to know a bit of CSS, which I don't really know.

It would be cool if it could be completely drag and drop, and you could do it like other products, like PowerApps. With PowerApps, you can move it pixel by pixel. It's like PowerPoint.

I've experienced a few bugs. Sometimes it was really tiny things - not something big. There are issues with the versioning systems, et cetera.

It had errors deploying in the public cloud to publish a solution just for the sake of testing it. 

I had an issue with a message definition. When you create a message definition and save it, and then close the project and open it again, the message definition did not save. I had to do it again. This has happened a lot.

I've used the solution for one year. I used it until last week. 

The solution is stable. 

If you establish best practices at the beginning, it's good. There were some bugs here and there I had to deal with. However, they were small. 

It's a scalable product.

I didn't really build something big by myself on it. I've seen with some applications if you respect good practices, if you don't overwhelm, if you put 100 entities in a module or something, and if you separate things properly, you can scale.

Technical support is great. They are very helpful and responsive. 

Positive

I did previously use the Microsoft Power Apps Platform. That's more like a system of services. It's not an on-in-one product.

The initial setup is more complex. I've also noticed that people that have a first-time interaction with it find it more difficult to grasp. It is very difficult to do in the beginning. You need three to six months to start building something which is not breaking.

Of course, that's way better than trying to program, since that's even more difficult.

My previous experience with some automotive company. They had real-world projects that they were using, and they were deploying to the cloud. I don't know exactly how long it took to set up for them. I remember that the deployment was really fast, like a few minutes. They had a medium type of setup. 

Maintenance and bug fixing is really easy. One person can handle it.

I am able to deploy the solution myself. I did not use any consultants or integrators. 

I'm not in charge of licensing costs. 

That said, my understanding is the product is very expensive, and Microsoft's offering is much cheaper. 

We build solutions and sell them to clients. We are intermediaries. We use this tool to deliver products. 

I only use it for web applications and very rarely for the hybrid web. I never use it for the hybrid web. Mostly, I use it only on desktop web.

I would recommend this solution and encourage people to learn it. 

I'd rate the solution nine out of ten. It's very top-notch as a product. It's one of the best.

We are using it, but it is not super integrated yet. Our early use cases are dashboards and SharePoint replacement.

Dashboards are valuable. It is easier to visualize data.

It is low code, where the developers can still develop in Java. That to us is very appealing.

The cost model could be better. It is expensive.

There should be more integration with engineering applications and tighter integration for user authentication, such as single sign-on, etc. They have some of that. It just could be stronger.

I have been working with Mendix for two years.

It is very stable.

I would keep it a medium on scalability. With small numbers of users, it is very nimble and operates fast, but when you get a whole lot of users in there, transaction speed goes down.

The number of users is relatively low. It is probably in the ballpark of under a hundred. It is currently for small cases for us. It is for small SharePoint replacements and small dashboards, but there are a lot of viewers of what's happening live with the system, whether things are up or down, and what they are doing for health monitoring of equipment, etc. We probably will increase its usage.

That's very good. They have a lot of ambassadors. They really try to drive success.

We used SharePoint and Power Apps. We switched mostly because of the tight integration with Siemens.

It is easy, but you have to have a governance model. You can't just drop it in and hope it works. It involves going in and making sure that you are controlling it.

The actual deployment was pretty fast. It only took a couple of days, but it took probably nine months of planning. There were lots of talks related to what is a governance model and what happens when it goes live. All the planning around what it means to have it live took about nine months, but the actual deployment was over a weekend.

It can be done in-house. We did it ourselves.

For deployment and maintenance purposes, there are about five people. You need someone who can handle the database. You need someone who can handle the middleware and servers, and then you need someone for architecture and then some type of analyst. You also need someone for operations support.

Its cost is higher than competitors. The cost mostly includes licensing.

It is charged per user. The cost model could be better. When you have a big company, what does per user mean? If I have a company where I have 40,000 people who will go to access it but only 200 do, how do you license it and who do you pay for? If they hit it once, do you pay for it? The licensing is complex for a big company. It is easy for us to buy all we can eat, get an enterprise license agreement, and call it good.

We evaluated Power Apps and OutSystems. It was the Siemens integrations that made us go for it.

It is interesting because it is low code, but the developers can still develop in Java. You still need some developers. It is not only an engineering tool. You have engineers and developers working in collaboration. Our Java developers have been key to our success.

I would rate it an eight out of ten.

The one big use case for one of the clients was to do a legacy organization. If they were on Java, we were trying to move to Mendix.

Use cases for PO approval, invoice approval, creating a better user experience for the user, or digital decoupling would be covered. Where you try to keep your core systems like SAP or PDM, PLM system as the core, you don't want to bring too much change in those for the use cases. 

The user experience is great. Creating the user experience is fast and the development speed is excellent.

I struggle with solutions like Mendix in terms of creating enterprise solutions. When I say enterprise solutions I mean enterprise-grade solutions. Let's say if I create an application on Mendix and I want to roll it out to multiple countries, that kind of thing I can do with Mendix. I'll have to copy it. That's hard to do at an enterprise level which can be quite sizeable. I'm not sure how well it scales. 

The setup itself can be complex and difficult. 

The UX capacity is lacking.

I'm not sure how well the workflow capabilities will hold up. 

I've used the solution for probably about a year. 

I have not had that kind of experience where I can make a statement on the stability of the platform. I don't know whether it is stable or not, as I did not work very deep on the platform in a live setting.

Looking at the architecture, scalability is going to be a challenge. I was part of the program, which I could not finish as I left the company. Yeah. Scalability-wise, I do see the technical approach that platform offers. Scalability will always be a question mark for me. I don't have data to prove whether it is not scalable. However, I am aware that it will be a challenge to scale. 

There are two types of scalability we're talking about. One is putting more and more and more and more processes on top of Mendix. That should not be a challenge. However, taking one process, taking one application, and scaling it to multiple countries, is where I see this platform struggling. However, with the cloud version, scaling may be simpler. 

I have no experience with the technical support I cannot speak to how helpful they would be. 

My portfolio had Mendix, OutSystems, Pega, Appian, Bizagi, and on the RPA side, UiPath, Blue Prism, and Automation Anywhere, and all the cognitive technologies like AI and ML. My responsibility was to create solutions and take them to the client. And then, the team will take care of technical design and implementation.

The solution can be complex to set up. Design-wise, I wouldn't say it is hard. However, you do have a lot of work to do. When you create a solution that needs to be rolled out to many countries, it gets complex. 

I have no visibility in terms of the cost of the solution. 

We are at the initial stages of setting up a partnership with Mendix. 

I was not involved in the technical part. I was leading as a principal architect. My responsibility was to come up with a strategic technical design, and we handed it over to the team, depending on which platform a customer would take. 

I'd advise potential new users to look at the UX capability. They promise too much. Therefore, be careful with the UX capability, as generally, all these platforms struggle in that area. Look at what they offer and what you need. 

Be careful with the workflow capability, as it's new, so it will have its own challenges, and look out for the scalability of the platform.

I'd rate the solution seven out of ten.

I am currently evaluating the product.

I enjoy the low-code nature of the product.

It's user-friendly and very easy to handle.

The product was easy to set up.

It is stable.

The stability is good.

I'm still in the evaluation phase. I have not fully vetted the entire product yet.

It is expensive.

I've been evaluating the solution for three months. Before I evaluated Mendix, I evaluated OutSystems for six months.

The stability has been good. There are no bugs or glitches and it doesn't crash or freeze. it's reliable. 

The product can scale and expand if you need it to.

We're planning to use it for 100 people.

At the moment, I can't communicate with technical support. It's expensive. I've never dealt with them directly.

I have using the OutSystems and now use Mendix.

It's an easy, straightforward setup. It's not overly complex or difficult at all. Setting it up shouldn't be an issue. 

The solution has been very expensive overall. It was not cheap.

At the moment, I'm looking for a solution for low code, so I am evaluating any product or solution with low code as an option. We already tried OutSystems. Microsoft Power Apps is another solution that may be an option.

I'd rate the solution eight out of ten. I can recommend it as a scalable option. It is easy to use and the evaluation is not expensive. The support is for the moment is good but expensive. 

I'm just a partner and an end-user.