CakePHP Development, Upgrades and Support
We build CakePHP 4 and 5 applications, take over older CakePHP 2 and 3 code, move it to PHP 8, fix its security gaps and add APIs, for businesses in the US, UK, Europe and the UAE. When a move to Laravel fits better, we say so.
- CakePHP 4 and 5 New applications and features, built the CakePHP way.
- Legacy takeovers CakePHP 2 and 3 apps kept running and cleaned up.
- Upgrades To a current CakePHP and PHP 8, step by step.
Ratings and how to get started
CakePHP development
What we build on CakePHP
The kinds of applications we build and look after on CakePHP, and the work we do on each.
-
Admin panels and back offices
Screens for your team to manage orders, customers, stock and content, with roles that limit who sees what.
-
Customer portals and member areas
Sign-in, profiles, documents and account pages for your customers, built on the Authentication and Authorization plugins.
-
REST APIs for apps
JSON APIs from your CakePHP application for a mobile app or a JavaScript front end, with tokens and validation.
-
Booking, order and invoicing systems
The workflows a business runs on every day: bookings, quotes, orders, invoices and the emails around them.
-
Reports and internal tools
Exports, dashboards and small tools on top of the data your CakePHP application already holds.
-
Older apps brought up to date
CakePHP 2 and 3 applications moved to a current version, with the code made safe to change on the way.
What we do
CakePHP services
From a new CakePHP application to the upgrades, security fixes and care that keep an older one running.
Book a free consultationCommon CakePHP problems we fix
- An application stuck on CakePHP 2 or 3
- Hosting that is dropping the PHP version you run on
- Deprecation warnings filling the error logs
- Plugins that no longer get updates
- No tests, so every change is a risk
- The developers who built it have moved on
-
New applications and features on CakePHP 4 and 5, started with bake and kept to the framework's conventions so the next developer finds their way.
-
Legacy CakePHP takeovers
CakePHP 2 and 3 applications another team wrote: read, documented, kept running and cleaned up, so changes stop breaking other things.
-
Applications moved to a current CakePHP and PHP 8 one version at a time, with deprecations fixed and tests added first.
-
Security fixes
Framework, plugin and Composer package updates, and the CSRF, sign-in and input checks reviewed where an older version left gaps.
-
JSON APIs for mobile and JavaScript front ends, payment gateways, CRMs and outside services connected to your application.
-
Fixes, CakePHP and package updates and new features after launch, one tested change at a time.
Choosing a path
Stay on CakePHP, upgrade, or move to Laravel?
We work in CakePHP and Laravel, so we have no reason to push you either way. This is how we help clients choose.
-
Stay on CakePHP when
- Your application runs on CakePHP 4 or 5 and does its job
- Your team knows its conventions and plugins
- What you need is new features and care, not a rewrite
-
Upgrade first when
- You are on CakePHP 2 or 3, or a PHP version without security fixes
- Your host is dropping the PHP version you run on
- The code works, but every change has grown risky
-
Move to Laravel when
- You are on CakePHP 2, where an upgrade is close to a rewrite anyway
- You need queues, scheduled jobs and many outside packages
- You want code that more PHP developers can pick up later
-
Another app on CodeIgniter?
Many businesses run more than one PHP framework. We look after CodeIgniter applications in the same way: audit, upgrade, then care.
See our CodeIgniter development → -
Or one on Yii?
Yii applications get the same treatment, with the clean-up done before any version move.
See our Yii development →
Not sure which framework your code is on, or is it plain PHP? See our PHP development.
How we work
From first call to CakePHP you can change
Six steps, and the same way of working on every project, new code or old.
Built in from the start
What goes into every CakePHP project
The habits that keep a CakePHP application safe to change and easy to hand over, new or old.
-
Migrations for every schema change
Database changes written as CakePHP migrations, so staging and live always match and a change can be rolled back.
-
Tests before changes
PHPUnit tests around the parts we touch, so an upgrade or a new feature does not quietly break an old one.
-
Composer, kept current
CakePHP, its plugins and every package pinned in composer.lock and updated on staging first.
-
The CakePHP conventions
Table and entity classes, components and plugins used the way the framework means, not worked around.
-
Secrets kept out of the code
Passwords and keys in environment settings or config/app_local.php, separate for staging and live, never in the repo.
-
Logs and alerts
Errors logged and sent to the people who act on them, with debug mode off on the live site.
Why Provis
Why work with Provis on CakePHP
What you can check before you hire us.
-
Yours from day one
Code repo, hosting and domain in your company's name; you can remove our access at any time.
-
Changes tested on staging
Every fix, feature and update reaches a staging copy before it reaches your users.
-
We fix what others left
We take over code other teams wrote, write down what is there and make it safe to change.
-
One project lead
A single point of contact, with a written weekly update and a demo of what was built.
-
Honest framework advice
We work in CakePHP, Laravel, CodeIgniter and Yii, so we recommend what fits your app.
-
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.
Tools and integrations
What we work with around CakePHP
The databases, front ends, payments and tools we connect to CakePHP applications, and the work we build ourselves when nothing ready-made fits.
-
PHP frameworksThe frameworks we build and look after.
- CakePHP
- Laravel
- CodeIgniter
- Yii
-
Databases and cacheWhere your data lives.
- MySQL
- MariaDB
- PostgreSQL
- Redis
-
Front endsWhat your users see and tap.
- Vue.js
- React
- Next.js
-
PaymentsTaking money in your application.
- Stripe
- PayPal
-
Code and deploysHow changes ship.
- Composer
- GitHub Actions
- GitLab
- Docker
-
Hosting and monitoringWhere it runs, and who hears when it stops.
- AWS
- DigitalOcean
- Nginx
- Sentry
Speed, security and care
Fast, safe and kept up to date
A CakePHP application is only as good as its slowest query, its oldest package and its next update. We look after all three, before launch and after it.
-
Fast pages and queries
Slow ORM queries found and tuned, results cached and heavy pages trimmed, so the application answers quickly.
-
Updates without surprises
CakePHP, plugin and Composer updates made on staging first, with the tests run before they go live.
-
Security basics, done
CSRF protection on, validated input, the ORM's bound queries, secrets out of the code and a PHP version that still gets security fixes.
-
Watched after launch
Database backups, error logs and alerts when something on the server stops, with fixes once the app is live.
Cost
What does CakePHP 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 the application is tidy, tested and documented.
-
The version gap
How far CakePHP, PHP and the plugins are behind a current version.
-
Features and user roles
How many screens, workflows and kinds of user the work touches.
-
Integrations
Payment gateways, CRMs, APIs and outside services, and how they connect.
-
Stay, upgrade or move
Work inside CakePHP, a version upgrade, or a move to Laravel.
-
Support after launch
Monitoring, updates, fixes and new features once it is live.
FAQ
CakePHP development questions
Straight answers to what clients ask us most.
How much does CakePHP development cost?
It depends on the state of the code, how far its CakePHP and PHP versions are behind, the features and integrations, and whether you stay on CakePHP or move. 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.
Which CakePHP versions do you work with?
CakePHP 2, 3, 4 and 5. We build new applications on CakePHP 5, add features to CakePHP 4 and 5 applications, and take over and upgrade older CakePHP 2 and 3 code.
Can you upgrade our CakePHP 2 or 3 application?
Yes. From CakePHP 3 the move to 4 and then 5 is done one version at a time: we fix deprecation warnings, run the CakePHP upgrade tool, update the plugins and test each step on staging. CakePHP 2 is different: version 3 changed the ORM and the folder layout, so moving off CakePHP 2 is close to a rewrite of the models and views. We tell you after the code audit whether an upgrade or a move to Laravel costs less.
Our host is dropping our PHP version. What can we do?
Older CakePHP versions do not run on current PHP. We check which CakePHP and PHP versions your code needs, then plan the upgrade so the application runs on a PHP version that still gets security fixes. Until then, we keep the current setup running on staging and live.
Should we stay on CakePHP or move to Laravel?
We work in both, so the answer depends on your application. A CakePHP 4 or 5 application that works is usually worth keeping and upgrading. A CakePHP 2 application needs so much change that a move to Laravel can cost about the same and leaves you with code more PHP developers know. We tell you which fits after the code audit.
Can you take over a CakePHP application another team built?
Yes. We start with a code audit: the CakePHP and PHP versions, the plugins, the Composer packages, the hosting and the risky parts. Then we keep it running with updates and fixes while we tidy it and add tests.
Can you add an API to our CakePHP application?
Yes. CakePHP controllers can answer in JSON, so we add API endpoints with token sign-in, validation and versions for a mobile app or a JavaScript front end, without rebuilding the application behind them.
Do you have CakePHP case studies?
Not on this site yet. Our published PHP work, including a legacy PHP application we maintain, is on the PHP and Laravel pages. On a call we can talk through how we would approach your CakePHP application.
Who owns the code?
You do. The code repo, hosting 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. 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 CakePHP 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.