Alam Al-Munawara
A bilingual booking platform built around the operation behind every tour
Read the case study: Alam Al-Munawara
Our Services
PHP Upgrades & Application Modernisation
We bring ageing PHP applications up to date in one of two ways: upgrade PHP and the framework in place with an app-like front end built on htmx and Alpine.js, or move the product to React or Next.js. Either way, the data and workflows your business depends on come with it.
What’s included
The parts of this service that make the difference in practice.
PHP version upgrades
Moving your application to a currently supported PHP version and fixing what the new version breaks: removed functions, deprecated behaviour, stricter type handling and libraries that are no longer maintained.
Framework and dependency upgrades
Bringing CodeIgniter, Laravel and third-party packages up to date, or replacing the ones that have been abandoned, so security fixes keep arriving.
An app-like front end without a rewrite
htmx and Alpine.js let a server-rendered PHP application update parts of a page, open dialogs and respond to input without full page reloads. It feels like a React front end while staying a single codebase.
Migration to React or Next.js
When the old stack itself is holding the product back, we rebuild it in React or Next.js and migrate the existing records with the relationships between them intact, rather than asking your team to re-enter anything.
Tested before the switch-over
The upgraded version is built and tested on a separate copy of the application, and the live site only moves across once it has been checked.
Best for: Applications on an unsupported PHP version, ageing CodeIgniter or Laravel projects, and products that have outgrown their original stack.
Case Studies
Related case studies
Both routes in practice: a CodeIgniter 3 platform running on PHP 8.4 with an htmx and Alpine.js front end, and a 2015 CodeIgniter platform rebuilt in Next.js with its data migrated.
Kyoto Daily Tours
A decade-old Kyoto tour platform rebuilt with Next.js
Read the case study: Kyoto Daily ToursHow we run this work
The same four steps apply to every project we take on, whatever its size.
Understand your goals
We learn how your business works and what success looks like before proposing anything.
Plan the scope
We agree the scope, priorities and timeline up front, so there are no surprises later.
Build and iterate
We build in stages and share progress as we go, so you can steer while it is still cheap to change.
Test, launch and support
We test properly before launch, then stay available for support and improvements afterwards.
Frequently asked questions
Should we upgrade our PHP application or rebuild it?
It depends on what is holding the application back. If the code is sound and the problem is an outdated PHP version or framework, upgrading in place is usually faster and cheaper. If the structure itself makes every change slow, or the product needs things the old stack handles poorly, a rebuild can cost less over time. Alam Al-Munawara took the first route and Kyoto Daily Tours the second. Which one we recommend comes out of scoping, weighed against your goals, budget and timeline.
Why does an old PHP version matter if the site still works?
Each PHP release only receives security fixes for a limited period. After that, newly discovered vulnerabilities stay unpatched, hosting providers start withdrawing support, and current libraries stop installing. Upgrading before that point is far easier than doing it in a hurry after a forced hosting change or a security incident.
Can an older CodeIgniter application be modernised without a rewrite?
Yes. The Alam Al-Munawara platform is built on CodeIgniter 3 and runs on PHP 8.4. Its front end uses htmx and Alpine.js, so pages update in place and respond the way people expect from a React application, without a separate front-end codebase to maintain.
Can you move our application to React or Next.js?
Yes. Kyoto Daily Tours is one example: the CodeIgniter platform we built in 2015 was rebuilt in Next.js, with its tours, bookings, customers and content migrated into the new data model rather than re-entered. Where it suits the project, the move can be made in stages rather than all at once.
Will the website go offline during the upgrade?
It should not need to. The upgraded version is built and tested on a separate copy of the application, and the live site only moves across once it has been checked.
Related services
Technical Support & Maintenance
Ongoing technical support including DevOps, server setup, migrations, performance optimization, and system maintenance.
Learn More about Technical Support & MaintenanceCustom Web Applications
Tailored online platforms and internal systems designed to support complex workflows, integrations, and scalable operations.
Learn More about Custom Web ApplicationsBusiness Websites
Clear, fast, and easy-to-manage business websites built to support real business goals and daily operations.
Learn More about Business WebsitesTalk through your project
Tell us what you are trying to build or fix, and we will tell you honestly whether we are the right fit and what the sensible next step is.
No obligation. We usually respond within 24 hours.