Map what actually matters.
Codebase, database, deployment, queues, integrations and the business logic nobody properly wrote down.
APPLICATION TAKEOVER / PHP + LARAVEL
Your software still runs.
Your software still runs.
Someone needs to own it.
NoRewrite is a specialist service for existing PHP and Laravel applications that have lost technical ownership. We learn the system that already runs your business, stabilize what matters, and become accountable for what happens next.
Talk directly with the engineer responsible for the work.
No repository access required for the first call.
No rewrite-first sales pitch.
WHY TRUST / THE DISTINCTION
NoRewrite is new. The engineering experience behind it is not. The work shown here comes from real production engineering experience with inherited PHP applications; identifying employer and client details are removed where required.
BUILT FOR / PRODUCTION SYSTEMS
Not a greenfield pitch disguised as maintenance.
Existing systems have users, undocumented behavior, awkward integrations and real consequences when changes go wrong. That is the environment NoRewrite is designed for.
PHP & Laravel
MySQL-heavy applications
REST APIs & webhooks
Queues & scheduled jobs
Linux / Nginx / deployment
Legacy business logic
Performance investigation
Direct senior involvement
THE WORK / THREE MOVES
Understand. Stabilize. Own.
The objective is not to make an old system look fashionable. It is to reduce uncertainty, remove dangerous bottlenecks and make future change safer.
Fix risk in the right order.
Broken workflows, slow queries, brittle integrations, unsafe releases and the parts everyone is afraid to touch.
Keep context after the emergency.
Ongoing technical ownership, modernization and a clear answer to who is responsible when the application changes.
WHY / NO REWRITE
Preserve the business value. Replace the uncertainty.
A rewrite throws away working behavior before the replacement has proven itself. Sometimes replacement is justified; often the safer move is to isolate the real problem and improve the system in place.
See performance work /→GOOD FIT / SITUATIONS
Usually called when something changed.
The previous developer left. The system became slow. Nobody trusts a deployment. A key integration is brittle. Or a codebase built quickly now needs proper ownership.
01
Laravel takeover
Take responsibility for an existing Laravel application without pretending it is a blank slate.
02Legacy PHP modernization
Untangle and modernize older PHP systems incrementally, preserving business behavior.
03Performance remediation
Profile first, then fix the data path, query, caching or application behavior actually causing the delay.
04NoRewrite Care
Ongoing senior ownership when the application needs context preserved month after month.
05Independent technical review
A second pair of senior eyes before a major change, handover or investment decision.
06AI-assisted code review
Review code produced with AI against architecture, security, maintainability and actual application behavior.
EVIDENCE / SELECTED ENGINEERING WORK
Measured problems, concrete implementation detail.
These examples are based on real production engineering work performed before and alongside the creation of NoRewrite. Identifying details are removed; technical method, code shape and measured outcomes are retained.
GRID PERFORMANCE~17s → ~1s
Replacing a view-heavy retrieval path while preserving filters, sorting and the existing workflow.
MYSQL QUERY300ms → 133msUsing EXPLAIN ANALYZE to expose row multiplication and unnecessary deduplication.
LEGACY REFACTORRULES → ONE HOMEExtracting business logic without forcing a simultaneous screen rewrite.
TAKEOVERBLACK BOX → MAPTurning runtime, deployment and business dependencies into an explicit ownership map.
OPEN SOURCE / PUBLIC ENGINEERING
Some of the engineering is public.
NoRewrite maintains public Laravel tooling around application diagnostics and performance. The repository is available to inspect: implementation, tests, release history and maintenance decisions rather than a marketing-only code sample.
FEATURED / LARAVEL PACKAGE
laravel-unused-eager-loads
Runtime diagnostics for identifying eager-loaded Eloquent relationships that are loaded but not meaningfully used.
ACCOUNTABILITY / HOW TRUST IS EARNED
Direct technical contact. Written evidence. Controlled change.
NoRewrite stays close to the engineering work without turning the homepage into a biography. The operating standard is visible in how problems are investigated, documented and changed in production.
Technical context stays attached.
The person discussing the system remains connected to assessment, implementation decisions and delivery.
Findings are inspectable.
Important conclusions are backed by code paths, query plans, measurements, architecture maps or written risk notes where appropriate.
Production change is deliberate.
Scope, access, recovery and verification are considered before material changes reach a live system.
FIRST ENGAGEMENT / WHAT HAPPENS
No mystery between first contact and production access.
The exact depth depends on the application, but the sequence is intentionally conservative: context first, access second, changes only after the system and recovery path are understood.
Explain the business context, current problem and desired outcome. No repository access required.
Agree NDA/security requirements and provide the least access needed for the next step.
Map the relevant code, data, runtime and operational risks. Produce written priorities.
Agree what should be fixed now, what can wait, and how production changes will be controlled.
Implement the agreed work, verify the result, document material decisions and preserve context.
COMMERCIAL / CLEAR ENTRY POINTS
Standard packages first. Custom engineering when needed.
The standard path stays simple: a free consultation, a focused Analysis & Assessment, or ongoing Care. Larger modernization programs are scoped separately around the application, business risk and delivery requirements.
01Free consultationFree / chat, email or meeting
02Analysis & Assessment€490
03Ongoing CareFrom €950/month
04Custom Engineering EngagementIndividually scoped / no public price
COMMON QUESTIONS / BEFORE WE TALK
Clear boundaries make the first conversation easier.
What happens in the free consultation?
We talk through the application, why you are looking for help, what changed, what is urgent and what a good outcome would look like. Repository access is not required.
Is the free consultation the technical assessment?
No. The assessment is paid technical work and produces a written, prioritized view of the agreed application area. The consultation is context, fit and next-step decision.
Who actually works on the application?
NoRewrite is deliberately small and technically led. The engineer discussing the system stays connected to assessment, technical decisions and delivery rather than handing the work from sales to an anonymous junior team. Specialist help can be added when a problem genuinely requires it.
Do you only work with Laravel?
Laravel is the primary modern framework focus, but NoRewrite also works with legacy PHP, MySQL-heavy systems, integrations and PHP applications that need stabilization before modernization.
Does “NoRewrite” mean you never recommend a rewrite?
No. It means a rewrite is not the default answer. If replacement is sensible after understanding existing behavior, migration cost and operational risk, we will say so.
START / FREE CONSULTATION
Chat, email or book a meeting
Tell us what changed.
“The developer left.” “The app is slow.” “Nobody understands billing.” “AI built most of it.” That is enough context for the first conversation.