I discovered Melis Platform about a year ago through LinkedIn and got interested in it since it’s promoted as an all-in-one platform. I decided to learn it and ended up using it in real projects.
Since it’s not as widely discussed as other frameworks, I wanted to share honest feedback based on hands-on experience, what worked well, what didn’t, and whether I’d recommend it.
🚀 What is Melis Platform?
Melis Platform is a modular CMS and development framework built on top of Laminas (formerly Zend Framework). It focuses on enterprise-level applications with a strong emphasis on modular architecture and back-office management.
✅ Pros of Melis Platform
1. Modular Architecture
One of the biggest strengths of Melis is its module-based structure.
Each feature can live in its own module, making the application easier to scale and maintain.
👉 This is especially useful for:
- Large teams
- Enterprise applications
- Long-term projects
2. Built-in Back Office
Melis provides a powerful admin interface out of the box, which saves a lot of development time.
- No need to build an admin panel from scratch
- Structured content management
- Permission handling
3. Flexibility with Laminas
Since it's built on Laminas, you get:
- Strong MVC architecture
- Dependency injection
- Mature ecosystem
This makes it suitable for developers already familiar with Zend/Laminas.
4. Enterprise-Oriented Features
Melis shines in structured environments:
- Multi-site management
- Multi-language support
5. Development Speed (in some cases)
For small to medium projects, Melis can feel light and fast to start.
Since it comes with many prebuilt features, it can easily save weeks (or even a month) of development time, especially for admin-related functionalities.
❌ Cons of Melis Platform
1. Steep Learning Curve
Let’s be honest, getting started is not easy.
⛔ Documentation is limited (the new website even removed it)
⛔ Concepts are not always intuitive
⛔ Requires strong understanding of Laminas
Compared to Laravel, onboarding is significantly slower.
If I hadn’t taken it as a personal challenge, I probably wouldn’t have spent that much time learning it. In many cases, I had to go through the vendor code just to understand the basics.
2. Smaller Community
Unlike Laravel or Symfony:
- Zero tutorials
- Zero StackOverflow answers
- Zero community support
Even though it’s open source, resources are hard to find. This can slow you down a lot when facing issues.
3. Debugging Can Be Painful
Because of its layered architecture:
- Tracing bugs is sometimes complex
- Error messages are not always clear
- You may encounter white screens on DB connection issues or fatal errors
4. Minimal Modules (in Practice)
Even though Melis is marketed as “all-in-one,” in real projects, many modules are not sufficient out of the box.
In almost every project, I had to modify modules to meet even basic requirements.
👉 Personally, I think Melis should focus more on improving the quality of existing modules rather than adding new ones.
5. CMS Limitations
As a developer, working with a CMS is great because it gives control to clients over the front-end.
However, with Melis:
- Almost everything still needs to be coded
- Even small UI changes (like button colors) require developer intervention
In practice, the CMS feels more like a text editor than a full content management system.
6. Open Source Experience
At first, the open-source aspect seems like a big advantage.
But in reality:
- No proper changelog
- Very limited documentation
- No tutorials
The only way to learn is often by digging into the code and commit history.
In many cases, even the commit messages don’t help much, you’ll often see vague messages like "updated" or "fix", which makes it hard to understand what actually changed.
Additionally, some modules get releases where only their dependencies are updated, with no actual code changes. For example, many modules are not even compatible with PHP 8.1 (which the platform itself runs on) yet still list it as a requirement in composer.json.
Also, the code quality can be inconsistent, which makes the experience harder than expected.
7. Community Version Limitations
Other platforms like WordPress, Drupal, or Odoo offer solid features in their community versions.
With Melis:
- Some basic features (like Roles Management or Media Library) are paid This can feel frustrating, especially for developers trying to explore or adopt the platform.
8. Version Stability
One of the most concerning issues is stability:
- Multiple releases can happen within a very short time (sometimes hours)
- Updates are not always stable
- A simple update can break production
👉 Tracking changes and updates becomes very difficult.
9. Security
Melis mainly relies on the baseline security provided by Laminas.
- No clear or frequent security updates
- Lack of communication around security fixes
- No strong visibility on security practices
This can be concerning, especially for enterprise projects where security should be a top priority.
10. Deprecation
Laminas MVC has been deprecated since June 6, 2025, yet there has been no clear update or migration path from Melis.
- No official communication about the impact
- No roadmap for moving away from deprecated components
- Uncertainty for long-term maintenance
This raises concerns about the future of the platform and its ability to keep up with modern standards.
11. Performance
Even though Melis doesn’t include advanced performance features in the community edition, there are basic performance expectations that any platform should meet.
From my experience, Melis does not run efficiently on standard servers. A server that could typically handle five WordPress production sites struggled just to run the Melis skeleton properly.
In one project I worked on, performance became a critical issue. Even with a robust server (4 CPU, 8GB RAM):
- The back office became slow as the number of users increased
- Around 100 users, the user management module became unusable
- The platform would freeze and sometimes crash completely
This raises serious concerns about scalability and performance optimization, especially for enterprise use cases.
12. Dead modules
Some modules, like melis-platform-framework-laravel, no longer receive updates and do not work at all with current versions of the platform.
- Deprecated modules create maintenance headaches
- Dependence on dead modules can block development
- Forces developers to rewrite or replace functionality
This further complicates long-term use of Melis in active projects.
💡 Final Thoughts
Melis Platform is powerful and has strong architectural ideas, especially for enterprise use.
However, in my experience, it comes with significant trade-offs:
- High complexity
- Lack of resources
- Time-consuming debugging and customization
It’s a tool that has high potential but is still not fully exploited.
In my opinion, Melis should focus more on the developer community, improving workflows, and making the platform easier to adopt and maintain.
It can work well in the right context, but today it’s definitely not for everyone.
🤝 Let’s Discuss
Have you worked with Melis Platform?
I’d love to hear your thoughts and experiences.
Top comments (0)