VeltoPHP v2 Released — Now with HMVC, CLI, and Better Stability
We’re proud to announce the release of VeltoPHP v2 — a simple, fast, and lightweight PHP framework built for rapid development and a better developer experience.
Why VeltoPHP?
VeltoPHP was created for developers who want a minimal yet powerful PHP framework without the bloat. Whether you're building a small prototype or a modular enterprise-grade system, VeltoPHP offers a clean and organized structure with modern tools to accelerate development.
What’s New in v2?
VeltoPHP v2 is a complete rewrite that brings major architectural improvements and usability enhancements:
✅ Modular HMVC architecture
✅ Built-in Axion Dashboard with Auth
✅ Built-in CLI for scaffolding & development
✅ Clean routing system with middleware support
✅ Model with query chaining (ORM-like)
✅ Built-in flash messages and alert system
✅ Easy migrations
✅ Middleware available
✅ Lightweight and customizable
Thank You to the Community
A huge thank you to everyone who supported, used, and gave feedback on VeltoPHP v1.
Your ideas, suggestions, bug reports, and even your criticisms helped shape what is now VeltoPHP v2 — a more robust, modular, and developer-friendly framework.
This release wouldn’t be possible without your input and passion for clean, fast PHP development.
We truly appreciate every one of you. Let’s keep building together. 💙
Feedback & Bug Reports Welcome!
This is just the beginning. While VeltoPHP v2 is considered stable for production, we welcome all bug reports, suggestions, or feature requests from the community. If you spot anything or want to contribute, feel free to open an issue or pull request on GitHub.
Your feedback helps shape the direction of VeltoPHP — together, we can build something great.
❤️ Credits
Developed by veltophp
Follow us on Instagram: @veltophp
Developer contact: dev@veltophp.com
Source code: github.com/veltophp
Top comments (4)
Wow HMVC, that takes me back to my Kohana days. That pattern never took off. I think the modularity was good, but It was too template focused.
I'm not sure why the framework needs two source directories, modules and app? I assume it has to do with the HMVC pattern.
Hi David, thanks for the comment!
Yes, Kohana was actually one of our inspirations — we wanted to bring back the modularity of HMVC, but with a simpler and cleaner approach.
The modules/ and app/ separation is just to help organize global vs. feature-specific code. You're right, it's part of how we apply the HMVC idea here.
Appreciate your thoughts — feedback like this helps us improve! 🙌
Congrats on v2! Love seeing more frameworks go modular - HMVC plus CLI is a big upgrade. How do you find the learning curve compares to something like Slim or CodeIgniter?
Hi, Dotallio
Thanks so much, really appreciate it! 🙌
We’ve aimed to keep the learning curve as minimal as possible — closer to CodeIgniter in terms of simplicity, but with modern touches like the CLI, flash system, and routing.
If you're used to Slim or CI, getting started with VeltoPHP should feel pretty familiar — but more structured once you dive into the modular side.
Would love to hear your thoughts if you give it a try!