Laravel Support & Upgrades
for Australian businesses.

Laravel releases a new major version annually. Each major version receives 2 years of bug fixes and 3 years of security fixes. Laravel 9 security support ended February 2024. Laravel 10 bug fixes ended August 2025. If you are on Laravel 8 or earlier, you are already past security support.

We upgrade Laravel applications through each major version: 5.x → 6, 6 → 7, 7 → 8, 8 → 9, 9 → 10, 10 → 11, 11 → 12. Each jump has breaking changes: deprecated methods, renamed classes, changed configuration, and package compatibility. We handle every one.

The PHP version often needs upgrading alongside Laravel. Laravel 11 requires PHP 8.2+. Laravel 10 requires PHP 8.1+. If your server is running PHP 7.4 or 8.0, the PHP upgrade happens first.

Composer packages with known CVEs. Outdated dependencies that no longer receive patches. Insecure authentication configuration. Missing CSRF protection. SQL injection through raw queries. XSS through unescaped Blade output.

We run `composer audit` to identify vulnerable packages, review authentication and authorisation logic, check for common Laravel security mistakes, and fix everything. Dependencies updated to patched versions.

For applications on end-of-life Laravel versions, the most critical security fix is the version upgrade itself. Running Laravel 7 or 8 means no security patches from the framework. Any vulnerability discovered in those versions will not be fixed.

Monthly support plans for Laravel applications. Composer dependency updates, security monitoring, bug fixes, performance optimisation, and small feature requests. A developer who knows your codebase.

Proactive monitoring: uptime checks, error tracking (Sentry or Flare), queue health, scheduled task monitoring, and dependency vulnerability scanning. Monthly reports on application health and any issues resolved.

Previous developer left? We take over Laravel codebases. Audit the application structure, review the routes, models, and services, set up proper CI/CD (GitHub Actions, GitLab CI, or Laravel Forge), and resume development.

Slow Laravel application. Pages loading in 3+ seconds. API responses taking too long. Queue workers falling behind. Database queries mounting up. The N+1 problem is the most common performance issue in Laravel.

We profile the application using Laravel Telescope, Debugbar, or Clockwork. Identify the bottlenecks: N+1 queries (eager loading fixes), missing database indexes, unoptimised Eloquent queries, cache not configured, and slow queue processing.

Common fixes: eager loading relationships, database query optimisation, Redis caching for frequently accessed data, route caching, config caching, view caching, and queue tuning. The result is sub-second response times for most pages.

Composer packages that are abandoned, archived, or no longer maintained. Popular packages that broke compatibility with newer Laravel versions. Custom fork dependencies that nobody wants to maintain.

Common migrations: Laravel Passport → Sanctum, Entrust/Sentinel → Spatie Permissions, Intervention Image updates, Maatwebsite Excel major version jumps, abandoned payment integrations replaced with Cashier or direct Stripe SDK.

We identify every deprecated or abandoned package, find the modern replacement, migrate the code, update tests, and verify the application works correctly. No more "abandoned package" warnings in your Composer output.