CodeIgniter Development, Takeovers and Upgrades
We build on CodeIgniter 4, take over and look after CodeIgniter 3 applications, move them to CodeIgniter 4 and current PHP versions, and tell you when a move to Laravel makes more sense. For businesses in the US, UK, Europe and the UAE.
- CodeIgniter 4 Builds New applications and APIs on the current CodeIgniter.
- Takeovers CodeIgniter 3 apps kept running, cleaned up and made safe to change.
- Upgrades CodeIgniter 3 to 4, and PHP versions, step by step.
Ratings and a first step
Upgrades
From CodeIgniter 3 to 4, part by part
CodeIgniter 4 is a rewrite of the framework, not a drop-in update: the folder layout, namespaces, routing and many libraries changed. So we move your application across one part at a time, on staging, while the current one keeps running.
- Routes
- Controllers
- Models and queries
- Views
- Libraries and helpers
- Sessions and sign-in
- Config and .env
- Scheduled jobs
-
01
Audit the CodeIgniter 3 app
Controllers, models, libraries, helpers, third-party code and the PHP version listed, with the risky parts marked.
-
02
Set up CodeIgniter 4 beside it
A new CodeIgniter 4 project with its config, database connection and environment file, on a staging server.
-
03
Move routes and controllers
Routes written out in app/Config/Routes.php, controllers moved to namespaced classes in app/Controllers.
-
04
Port models, libraries and views
Queries moved to CodeIgniter 4 models and Query Builder, validation, sessions and views rewritten where they changed.
-
05
Test side by side, then switch over
Both versions compared on staging, then the switch. Your CodeIgniter 3 app stays live until then.
What we do
CodeIgniter development services
What we do with CodeIgniter, from a new CodeIgniter 4 build to takeovers, upgrades and the support behind them.
Book a free consultationProblems we often fix
- Errors and deprecation notices after a PHP upgrade
- A CodeIgniter 3 app that nobody on the team wrote
- Slow pages from heavy database queries
- Security updates that were never applied
- No staging copy, so every change goes straight to live
-
New web applications, admin panels and portals on CodeIgniter 4, with the code in your own repo.
-
CodeIgniter 3 takeovers
Code another team wrote, read, kept running and cleaned up, so changes stop breaking other things.
-
Your application ported to CodeIgniter 4 part by part on staging, while the current one keeps running.
-
Deprecated code and old packages fixed so the application runs on a PHP version that still gets security fixes.
-
APIs and integrations
REST APIs for your mobile app or JavaScript front end, and links to payment gateways, CRMs and other services.
-
Fixes, security patches, framework and package updates and new features after launch, one change at a time.
Choosing a path
Stay on CodeIgniter, upgrade to CodeIgniter 4, or move to Laravel?
We work with all of them, so we have no reason to push you either way. This is how we help clients choose.
-
Stay on CodeIgniter 3 for now if
- The application works and changes rarely
- It runs on a PHP version that still gets security fixes
- You need a few fixes or features before a bigger move
-
Upgrade to CodeIgniter 4 when
- Your team knows CodeIgniter and wants to keep its light, simple style
- You need a current PHP version and newer framework features
- The application is worth keeping, but its CodeIgniter 3 base is holding it back
-
Move to Laravel when
- The application is growing: accounts, roles, payments and background jobs
- A CodeIgniter 4 upgrade would mean rewriting most of it anyway
- You want packages and developers that are easy to find later
On another PHP framework? We look after those too: Yii development and CakePHP development.
How we work
From first call to code you can change
The same way of working on every project, a new CodeIgniter 4 build or an older CodeIgniter 3 app.
CodeIgniter development
What we build on CodeIgniter
New CodeIgniter 4 work, and the work that keeps an older CodeIgniter application fast, safe and easy to change.
-
Admin panels and back offices
Screens for orders, stock, bookings or reports, with roles so each person sees only their part.
-
Customer and partner portals
Sign-in areas where customers see their orders, invoices and documents, and send requests.
-
REST APIs for apps
APIs that your mobile app or JavaScript front end calls, with sign-in tokens, validation and versions.
-
CodeIgniter 3 to 4 rebuilds
An older application ported to CodeIgniter 4, part by part, with its data and features kept.
-
Payments and integrations
Payment gateways, email, SMS, CRMs and accounting tools connected through their APIs and webhooks.
-
Speed and security fixes
Slow queries tuned, caching added, security patches applied and old PHP code brought up to date.
Why Provis
Why work with Provis on CodeIgniter
What you can check before you hire us.
-
Clean-up before upgrades
We tidy and test the code first, so a CodeIgniter or PHP move does not break what works.
-
Advice that is not one-sided
We build on Laravel and look after CodeIgniter, Yii and CakePHP, so we gain nothing from pushing a move.
-
Changes on staging first
Every change is tested on a staging copy before it reaches your users.
-
We stay after launch
Monitoring, updates and fixes continue once the work is live, on a plan that suits you.
-
Yours from day one
Code repo, server and domain in your company's name; you can remove our access at any time.
-
Hours that overlap yours
We are on IST: 4.5 to 5.5 hours ahead of London, 9.5 to 10.5 ahead of New York.
Integrations
What a CodeIgniter app connects to
The databases, servers and services a CodeIgniter application usually runs with, the PHP frameworks we work in, and the parts we build ourselves.
-
DatabasesWhere the application keeps its data.
- MySQL
- PostgreSQL
-
Caching and sessionsFaster pages and shared sign-ins.
- Redis
-
Web serversWhat serves the application.
- Apache
- NGINX
-
PaymentsTaking money online.
- Stripe
- PayPal
-
Code and deploysYour repo, reviews and releases.
- Git
- GitHub
-
PHP frameworksThe frameworks we build and look after.
- CodeIgniter
- Laravel
- Yii
- CakePHP
Speed, security and care
Fast, safe and kept up to date.
A CodeIgniter application keeps ageing after it goes live: PHP versions reach the end of their security fixes, the framework and packages move on, and more users and data arrive. We look after the code and the server it runs on.
-
Fast pages and queries
Slow database queries found and tuned, results cached and API responses trimmed, so pages answer quickly.
-
Updates without surprises
CodeIgniter, PHP and Composer package updates made on staging first, with the tests run before they go live.
-
Backups and alerts
Database backups, error logging and alerts when something on the server stops.
-
Security basics, done
CSRF protection on, validated input, bound database queries, escaped output and a PHP version that still gets security fixes.
Cost
What does CodeIgniter work cost?
Every application is different, so we quote after a short call, not from a price list. Within two working days you get an approach, a rough timeline and a rough cost range. No charge, no commitment.
What changes the price
-
The state of the code
How much of an existing application is tidy, tested and documented.
-
The version gap
CodeIgniter 3 or 4, and how far the PHP version and packages are behind.
-
Upgrade or rebuild
Patching what is there, porting it to CodeIgniter 4, or moving it to Laravel.
-
Features and user roles
How many screens, workflows and kinds of user the work touches.
-
Integrations
Payment gateways, CRMs, mobile apps and outside APIs, and how they connect.
-
Support after launch
Monitoring, updates, fixes and new features once it is live.
FAQ
CodeIgniter questions
Straight answers about building, upgrading and looking after CodeIgniter apps.
How much does CodeIgniter development cost?
It depends on the state of any existing code, whether it is on CodeIgniter 3 or 4, how far its PHP version is behind, and the features and integrations involved. We do not sell fixed packages. After a short call, we send an approach, a rough timeline and a rough cost range within two working days, with no charge and no commitment.
Can you upgrade our CodeIgniter 3 application to CodeIgniter 4?
Yes. CodeIgniter 4 is a rewrite of the framework and is not backwards compatible, so the upgrade is a planned port rather than a version bump. We audit the CodeIgniter 3 code, set up CodeIgniter 4 on staging, move the routes, controllers, models, libraries and views part by part, and test both side by side. Your current application stays live until the switch-over.
Does CodeIgniter 3 still work on current PHP versions?
It depends on the exact CodeIgniter 3 release, your own code and the libraries you use. Older releases, and code written for PHP 5 or PHP 7, often show errors or deprecation notices on PHP 8. We check your versions in the code audit, then either fix the application so it runs on a supported PHP version or plan a move to CodeIgniter 4.
Should we upgrade to CodeIgniter 4 or move to Laravel?
We work with both, so the answer depends on your application. CodeIgniter 4 suits a team that knows CodeIgniter and an application worth keeping in that style. Laravel suits an application that is growing into accounts, roles, payments and background jobs, or one that would need rewriting anyway. We tell you which fits after the code audit.
Can you take over a CodeIgniter application another team built?
Yes. We start with a code audit: the CodeIgniter and PHP versions, the libraries and packages, the hosting and the risky parts. Then we keep it running with fixes and updates while we tidy it, and set up a staging copy if there is none.
Do you build new applications on CodeIgniter 4?
Yes, when CodeIgniter fits: a light application, a team that already knows it, or hosting with little more than PHP and a database. For a larger new build with many roles and background jobs we usually suggest Laravel, and say why.
Can you build a REST API with CodeIgniter?
Yes. CodeIgniter 4 has resource routes and controllers for REST APIs. We build APIs for mobile apps and JavaScript front ends, with sign-in tokens, input validation, versioned endpoints and documentation for the developers who call them.
How do you keep a CodeIgniter application secure?
We turn on CSRF protection, validate input, use bound queries through the Query Builder, escape output in views, keep secrets out of the code and run a PHP version that still gets security fixes. Framework, PHP and package updates are tested on staging before they go live.
Who owns the code?
You do. The code repo, server and domain are in your company's name; our team joins as collaborators, and you can remove our access at any time. You see the work on a staging link as it is done.
Do you work with clients outside India?
Yes. Our team is in Jaipur on IST, 4.5 to 5.5 hours ahead of London and 9.5 to 10.5 ahead of New York, and works with clients in the US, the UK, Europe, Australia and the UAE. Our UK company, Provis Global Ltd, is registered in the United Kingdom.
- 1 Project details
- 2 Your details
- 3 Additional info
Tell us about your CodeIgniter project
This helps us understand your application and prepare a relevant reply.
Prefer to talk directly?
We're on IST: 4.5 to 5.5 hours ahead of London, 9.5 to 10.5 ahead of New York.