Laravel applications for businesses in Limburg: built, put into production and maintained by one developer based in Vaals.
For an application a business will use for years, I usually pick Laravel. The framework sets out how code is organised and where the database and background jobs live. That means any PHP developer who joins later can read the project. The community is large and the documentation is kept up to date. The code is open source under a permissive licence and runs on an ordinary server. So you are not tied to a vendor, and not to me either.
What I build with Laravel almost always starts with a work process that currently runs across separate systems and manual steps. The application takes that process over: orders that come in and need processing, a customer portal connected to the accounts, documents that have to be checked before they move on, and the link between all of it. Often it is an API between systems that don't talk to each other, with a dashboard on top so you can see what is happening. For a manufacturing company, for example, I built a Laravel API that processed incoming orders and generated cutting lines for a machine that had been standing idle. Where AI fits into the process, say a language model that reads documents, I build it in, with Laravel as the layer that holds everything together. I work from Vaals for businesses across Limburg.
A project starts with looking at how the work really runs today, including the exceptions nobody writes down. Then I build a small first version you can use straight away and continue from there in sprints of a week or two. Each sprint delivers a working piece. I handle the go-live myself, in Docker on a server we choose together. Documentation is part of the delivery, and after that I stay available for maintenance and further development.
If you already have a Laravel application, or a pilot that never quite goes live, it does not need to be rebuilt. I start by reading the code and the environment: which Laravel version, how it is deployed, where the tests are and what breaks when you touch something. Then we make a list of what is needed to get it into production or back up to date, and I pick that up alongside the people already working on it. Replacing is a last resort, not the starting point.
CVTailor is a product of my own with a Laravel backend and a React frontend. The application reads CVs in PDF and DOCX and matches the competencies in them against CompetentNL, live against the official CompetentNL SPARQL endpoint and using the official CompetentNL to ESCO mapping. It runs bilingual (Dutch and English) in Docker and is in use.
Custom web applications, API development and full-stack platforms. I build scalable solutions with modern technologies.
The cutting machine is finally in daily use. A permanent employee was hired to operate it. The boss's son was freed from manual cutting work, editing cutting lines and order management. The workflow went from a day to 20 minutes.
View the caseYes. That starts with reading the code and getting the application running locally before I change anything. Then we discuss what comes first: an upgrade, or the feature that has been on the list for months. You keep your existing application, I build on it.
That depends on what is already there and who will maintain it later. If your business runs on PHP, or you have people who know it, Laravel is the obvious choice. For some applications Next.js or NestJS fits better, and I build those too. I pick what will last longest in your situation.
Yes. Kerris ICT is based in Vaals, in South Limburg. For an introduction or a working session I come to Maastricht, Heerlen and the rest of the province. The building itself I mostly do remotely, with a short check-in each sprint.
Got an idea, a problem or a project? I'm happy to help. No obligations, just a good conversation.