Clear ownership of problems
Incidents stop bouncing between hosting, plugins, suppliers and the internal team without a clear next action.
Freelance service
General maintenance for websites, applications and backends through one-off work or monthly support.
Problem and outcome
The scope is built around a real problem and a verifiable outcome, not a generic list of tasks.
Problems it solves
The website or application works, but it has accumulated errors, pending updates or changes that nobody fully owns.Technical maintenance keeps a website or application secure, stable and easier to change after launch.
It can start with one incident, a technical tune-up or a monthly agreement. I keep the work visible and make clear what is included, what remains open and what depends on third parties.
Incidents stop bouncing between hosting, plugins, suppliers and the internal team without a clear next action.
I review backups, dependencies, delivery and critical journeys before applying updates or fixes.
We separate urgent work, accumulated risk and optional improvements so the first investment goes where it matters.
Guide price
Three ways to start depending on the size of the need. Prices are indicative and final scope is agreed after the initial assessment.
One-off intervention
A quick review to locate an incident or risk and leave a clear next step.
€90
+ VATWhat is included
Boundary: This is not a full audit and cannot guarantee a fix for third-party failures.
Ask about this interventionTechnical tune-up
The most common optionA complete block to stabilize, update and organize a website or application.
€290
+ VATWhat is included
Boundary: This does not include rewrites, new functional areas or out-of-hours response.
Request a tune-up assessmentMonthly support
A prioritized maintenance and improvement queue with direct follow-up.
€69 /month
+ VATWhat is included
Boundary: This does not include 24/7 availability or immediate response unless agreed separately.
Ask about monthly supportService scope
Final pricing depends on scope, integrations and project state. If it does not fit, I will say so before estimating.
Process
I work from frontend through backend and delivery, so I can follow a problem across several layers.
Collect the symptom, context, access and actual impact.
Separate urgency from accumulated debt and agree the first block.
Apply changes with backups, tests or a rollback path proportionate to the risk.
Close with completed work, open items and the next priority.
Related proof
I write about backend work, tools, automation and practical decisions while building software.
Related project
Recovery and production launch of an Attendize-based ticketing platform with Docker, VPS hosting, HTTPS, Stripe and a registration flow adapted for event managers.
View caseFAQ
Not by default. Monthly support covers agreed capacity and priorities, not 24/7 availability or immediate response.
Yes, provided I can review the codebase, access and current state before committing to a scope. The initial intervention usually provides that context.
Contact
Tell me what you want to build, what you have now and what outcome you need. If it fits, I’ll suggest a clear next step.