Tech Weekly

After years of developing with Laravel, I noticed a frustrating pattern. No matter how unique a project seemed, the foundation remained the same: Authentication, Dashboards, Tables, Forms, and Permissions. I found myself rebuilding these structures over and over. Sometimes I did it faster, sometimes cleaner—but I was still rebuilding. Eventually,.

For years, working with Eloquent models in Laravel meant relying heavily on configuration arrays like $fillable and $casts. They worked, and they became part of how most developers approached model design. But if we’re honest, they always felt a bit disconnected from the language itself. They weren’t really code. They.

TL;DR: Kumix.cloud is a multi-tenant SaaS dashboard built with Laravel and React that lets DevOps engineers, system administrators, and hosting providers manage VPS instances, SSH credentials, and server health from a single, real-time interface. Here’s how I built it. The Problem Managing multiple VPS servers across different providers is a fragmented nightmare. You bounce between: I needed one.

Recently, I ran into a problem that looked simple at first, but quickly turned into a performance bottleneck. I needed to fetch a directory of cities and branches from a third-party delivery service for an ecommerce checkout page. Since the store supports multiple languages, the same dataset had to be.

Over the years, I’ve deployed a lot of projects. Small client websites, Laravel apps, WordPress installs, internal tools… and almost every time, the process looked similar. Spin up a VPS, install a stack, configure domains, set up backups, tweak security, and repeat. It worked, but it was never smooth. Every.