Stability, Code Quality & Structure Issues

[nuxwin]

@andrasbacsai

Hello

Yes, the title says it all, and I believe you understand the concern well.

First, let me acknowledge that this projet is a great project with incredible potential. The idea behind it, providing a self-hostable alternative to platforms like Heroku, Netlify, and Vercel is valuable and much needed in the industry. As an expert in development and DevOps with over 20 years of experience, I see its promise, particularly from an IT operations perspective.

However, after significant usage and analysis, some critical issues have emerged that make it difficult for us (and likely others) to rely on this project for production environments.

1. Code Quality & Structure Issues

• The codebase lacks proper structure, making it harder to maintain and contribute effectively.
• PSR coding standards are not consistently followed, reducing readability and maintainability.
• Many functions/methods exceed 50 lines, which is really bad for software design and makes debugging difficult.
• Command results often lack sufficient runtime testing, making it unclear whether things work as intended or just by chance.
• ...

2. Lack of Focus on Stability & Frequent Regressions

• The relentless push for new features comes at the cost of stability. Each new release introduces regressions rather than improving reliability.

Recent major issues include:

• Transactional emails breaking in a recent update. It is still not working at time I'm writing this message.
• The Docker Compose editor being completely broken, preventing proper configuration. A temporarily fix was provided lately
• GitHub integration errors ("Signing key cannot be empty"), making deployments unreliable.

3. Why This Matters: A Business & Community Concern

We are a company actively using your project in a self-hosted environment. However, the lack of stabilization efforts makes it impossible to rely on.

It's not just us. Many users have reported deployment failures, broken integrations (e.g., Supabase not connecting properly), and a frustrating development experience. The project seems to prioritize new features over fixing core functionality, which is an unsustainable approach.

4. The Real Question: Should We Take Over the Project?

Given these issues, we are seriously considering:

• Forking the project under a new branding and focusing on stability first, rather than endless feature creep.
• Refactoring the codebase to improve maintainability, following industry best practices (e.g., modularization, proper testing, PSR ...).
• Ensuring real-world usability, so that businesses and developers can actually depend on it.

At this point, we need to ask:

• Is there a plan to stabilize the project?
• Is the team willing to shift focus towards fixing core issues?
• If not, is it time for the community to take the lead and make the project what it was meant to be a reliable OSS solution for modern IaaS platforms?

Don't get me wrong. The purpose is not to discredit your work but to help make your project a true success. We recognize the effort and vision behind, and we appreciate what has been built so far.

We want to support you and contribute to improving the project. However, at this stage, we are waiting to see a real commitment to stabilization and code quality before we can confidently rely on it in a production environment.

Thank you.

[maietta]

This smells like a combination of AI generated issue and spam.

That aside, you can always fork it.

[nuxwin]

This smells like a combination of AI generated issue and spam.

That aside, you can always fork it.

Yes, AI was a bit used to make the text clear, without typo ! What's wrong with this ? We are in 2025. Anyway, this doesn't change the overall content which is our opinion. The raised and linked issues were not generated by IA. Where do you see SPAM ? And who are you to just say: "you can always fork it." ? This thread maybe annoy you but that a sad reality ... I edited it again to make it a more human like, without any further reference to my company if that what you're calling SPAM ...

[peaklabs-dev]

@nuxwin I totally understand where you are coming from and you are absolutely right. There are a lot of issues, especially with stability and regression, I totally agree. We are actually in heavy planning for something pretty big (can't announce it yet) that will allow stability with feature testing for all features and also unit testing for critical stuff and of course much better code quality and more strict release rules and much more....

Will probably announce what we have planned on Twitter sometime next week. And a announcement on discord will follow sometime later on in the process of building it.