Why work with AgiCAD
Within two business days
We read your message and reply - not a sales queue, not an account manager.
Hour Blocks from $180
Prepaid in Hour Blocks of 6, 12 or 24 hours. No fixed scope, no expiry on unused hours.
PHP in production
We run Laravel products on PHP 8 and take on older apps, including ones on long-unsupported PHP versions.
You own the code
Full documented source in your repository. No lock-in, no recurring licence to us.
What breaks CodeIgniter apps,
and what we do about it.
These apps are usually fine until something underneath them moves - the PHP version, the host, or the last developer.
PHP 8 broke it
Your host upgraded and the app started throwing 500s. The usual culprits are PHP 4-style constructors, each(), curly-brace string offsets, and required-after-optional parameters - all mechanical fixes once you can see the real error log.
CodeIgniter 3 is end-of-life
CI3 no longer receives fixes. The options are an honest security audit plus maintained dependencies, or a staged move to CodeIgniter 4 - and we will tell you which one your app actually justifies.
A CI3 to CI4 migration nobody wants to start
CI4 changes the directory layout, namespaces everything, replaces the model and query-builder conventions, and swaps the routing. It is done module by module, with the app deployable the whole way, not as a big-bang rewrite.
Home-grown authentication
Passwords hashed with MD5 or SHA-1, sessions kept in plain files, no CSRF tokens. Moving to password_hash() with a transparent rehash-on-login keeps every existing user able to log in.
Queries built by string concatenation
Raw SQL glued together from $_POST is the classic CodeIgniter-era injection risk. Query Builder bindings, escaped output and proper CSRF protection close the common holes.
The developer is long gone
No documentation, no repository history, FTP-only deploys. First job is getting the code into git with a staging copy, so the next change is not performed live on production at 2 a.m.
What the hours buy.
One-off jobs or steady monthly maintenance - both drawn from the same prepaid hours.
Bug fixes & incident work
Something is broken now: a 500 on checkout, a form that silently fails, a cron that stopped. Reproduce, read the real log, fix the cause rather than the symptom.
- White screens & fatal errors
- Broken forms, uploads & emails
- Failing cron jobs & queues
- Database & migration errors
- Session and login problems
- A written note on what caused it
Security & compatibility patching
Closing the holes that legacy PHP apps accumulate, and getting the code running on a supported PHP version so your host stops sending warning emails.
- SQL injection & XSS hardening
- CSRF protection & nonce checks
- Modern password hashing with rehash on login
- File-upload validation
- PHP 7.4 to 8.x compatibility fixes
- Dependency and library updates
CodeIgniter 3 to 4 migration
A staged migration rather than a rewrite: routing, namespaces, models and libraries moved across in slices, with the application deployable at every step.
- Upgrade audit & honest effort estimate
- Directory & namespace restructure
- Routing and controller conversion
- Models to CI4 entities & query builder
- Libraries, helpers & third-party code
- Parallel-run and cutover plan
Small features & changes
The changes the business keeps asking for: a new report, an extra field, a second payment method, an export the accountant needs.
- New reports & exports
- Extra fields & admin screens
- Payment & shipping changes
- Third-party API integrations
- Email & notification changes
- Front-end tweaks
Performance & reliability
Old PHP apps rarely need new hardware; they need someone to look at the queries and the request cycle.
- Slow-query profiling & indexes
- N+1 query elimination
- Caching (opcode, query, page)
- Moving slow work into cron or a queue
- Error tracking & log hygiene
- Automated backups with a restore drill
Ongoing maintenance
An Hour Block kept on file, drawn down as things come up - so there is somebody to call before it becomes an emergency.
- Priority response on incidents
- Monthly patch & dependency review
- Uptime and error monitoring
- Small changes without re-negotiating
- Unused hours roll forward
- No long-term contract
Low-risk, even on
an app nobody understands.
The first hours go into understanding what you have - that is the part that makes everything after it cheap.
Tell us what's wrong
What the app does, which CodeIgniter and PHP version it runs on if you know, and what is failing. Rough is fine; we will ask for the error log.
Pick an Hour Block
Prepay a block of hours - 6, 12, or 24. The block is the budget; we work until it's used, or you top up. Hours don't expire.
Read, reproduce, fix
Code into git, a staging copy stood up, the fault reproduced away from production, then fixed - with a short written note on what caused it.
Maintain or migrate
From there it's your call: leave it stable and keep a small Hour Block on file, or start a staged CodeIgniter 4 migration with the app live throughout.
Prepaid in Hour Blocks.
Three block sizes - the same hours whether you need one emergency fix or someone on hand every month.
Starter - 6 hrs
$180
Typically enough for a bug fix, a security patch, a PHP-version break.
Standard - 12 hrs
$360
Typically enough for a small feature, or an upgrade audit with the first fixes applied.
Pro - 24 hrs
$720
Typically enough for a migration slice, or a steady month of maintenance and changes.
Hour Blocks are sold at $30/hr with no discount. Unused hours don't expire - apply them to the same project, or roll them into a top-up Hour Block.
Frequently asked.
What's an Hour Block - and what if our job takes more or fewer hours?
An Hour Block is a prepaid block of hours: Starter (6h, $180), Standard (12h, $360) or Pro (24h, $720). It is a bucket of time, not a fixed-scope deliverable. If the work finishes before the hours are used, the leftover rolls forward to the same project or into a top-up Hour Block - hours do not expire. If the work runs over, you buy another Hour Block.
Do you work on CodeIgniter 2 and 3, or only CodeIgniter 4?
All three. We take on CodeIgniter 2 and 3 applications that are still earning money, including ones on long-unsupported PHP versions, and CodeIgniter 4 work such as new features and migrations.
CodeIgniter 3 is end-of-life. Do we have to migrate to CodeIgniter 4?
Not automatically. Plenty of CI3 apps can be kept safe with a security pass, updated dependencies and a supported PHP version, and that is far cheaper than a migration. We will look at your code and tell you which one your situation justifies, including when the honest answer is to leave it alone.
How does a CodeIgniter 3 to 4 migration actually work?
In slices, not as a big-bang rewrite. First an upgrade audit - what depends on what, and how big the job really is. Then the directory and namespace restructure, then routing and controllers, then models and libraries, module by module, with the application deployable at every step and a planned cutover at the end.
Our host upgraded to PHP 8 and the site broke. Can you fix it?
Usually yes, and usually faster than people expect. The breakages are mostly mechanical: removed functions such as each(), PHP 4-style constructors, curly-brace string offsets, required parameters declared after optional ones, and stricter type handling. The first step is getting at the real error log rather than the generic 500 page.
Do we own the code, and can another developer take over later?
Yes. Everything is delivered in your repository, documented, with no lock-in. Part of the job on neglected apps is putting the code into version control with a staging environment, so the next person - us or anyone else - is not editing production over FTP.
Will you sign an NDA, and will you touch our production server?
Yes to the NDA - send yours or we will use a simple mutual one, and no client or client domain is ever named on this site. On production access: we prefer a staging copy and a git-based deploy, and will help you set that up if it does not exist yet.
Can you be on call for ongoing maintenance?
Yes. Keep an Hour Block on file and draw it down as things come up - patches, small changes, incidents. There is no long-term contract and unused hours roll forward, so it costs nothing to have somebody available.
related
Tell us about the app.
What it does, which CodeIgniter and PHP version it runs on if you know, and what is going wrong. We read every message and reply within two business days with an honest take and which Hour Block fits.
Prefer email?
[email protected]