Your custom PHP software runs – and should keep running. Updates, security, monitoring, bug fixing and small changes with a fixed point of contact.
Maintenance & Support for PHP Applications
Custom software has no update team in the background. When PHP gets a new version, a library reports a security issue or the hosting provider changes the server, someone has to take care of it – someone who knows the application. I maintain PHP and Symfony applications on an ongoing basis: inventory systems, integrations, portals, back-office tools and company websites.
What maintenance covers
Updates and security patches
Keep PHP version, framework, Composer dependencies, CMS core and extensions current – tested on staging, then deployed to production.
Monitoring and bug fixing
Error logs under watch, notification on outages, analysis and fixing of bugs before they disturb daily business.
Small enhancements
A new field, a changed export, an adjustment to an integration: short requests are implemented from the monthly allowance, without needing a quote for every little thing.
Server and deployment questions
Coordination with the hosting provider, PHP migrations, cron jobs, backups, staging environment, reproducible deployments.
Documentation and handover
What changed is recorded in the project – in the repository and in a short, current documentation. No knowledge that lives only with me.
Taking over applications from other developers
The previous developer is no longer reachable? I take over after a short assessment and secure the application first, before anything new is built.
How the collaboration works
- Assessment: Code, server, dependencies, open risks – you get an honest evaluation and a prioritised list.
- Securing: Urgent items first (security, backups, updates), then ongoing operation.
- Ongoing support: Monthly allowance or time and material, agreed response times, one point of contact.
How I work
Three principles that apply in every project
Understand before building
First the short technical assessment: what is the actual problem, where is the lever, what makes economic sense? Then the implementation.
Build instead of forwarding
You talk to the developer who does the work – no handover chain, no black box, clear status updates and early warning about risks.
Hand over instead of holding on
Code in your repository, tests, documentation and a deployment process your team understands. No vendor lock-in – your system does not depend on me afterwards.
Background
Experience at a glance
- Today
- Senior freelancer in ongoing Shopware projects of several agencies and merchants – at home in foreign repos, processes and deadlines.
- Since 2021
- Self-employed as Stefan Pilz Ltd. – remote for merchants and agencies: Shopware 5 and 6, Symfony, migrations, maintenance.
- 2015 – 2020
- E-commerce backends: inventory, PIM and Amazon/eBay integrations for around 3.5 million products, then the Drillisch mobile-carrier web stores.
- Since 2012
- Full-time web developer – first at an agency: websites and stores with Joomla, xt-Commerce and Shopware.
- 2002
- Completed vocational training as a software developer (C/C++). First own PHP websites from 2004.
See current and completed projects Career and stack in the CV
Good fit
Works well when...
- you have a concrete business requirement that standard software does not cover cleanly.
- you need an experienced PHP/Symfony developer who implements directly instead of forwarding tickets.
- you run existing systems, stores or integrations that have to work together.