Maintenance and security.
Launch is not the end, it is the beginning. I take over the server, the backups, the monitoring and the updates, and you get a response time guaranteed in the contract - and one person to call when something happens.
Diagnosis
An unattended site breaks quietly.
The risk grows in the background and stays invisible right up to the moment it lands - usually in the worst week of the year.
An outage at the worst possible moment
The site goes down in the middle of a campaign or at the peak of the season. Without someone who reacts immediately, you lose traffic and enquiries - hour after hour, before you even notice.
A backup nobody ever checked
A backup that exists only in theory is worth exactly as much as no backup at all. Rebuilding a site from zero takes weeks and costs many times more than regular copies.
You have no time for any of it
Updates, monitoring, certificates, server configuration. Each of these needs attention and knowledge, and the time for it comes out of your business.
Process
What taking over the care looks like.
You sign the contract and stop thinking about the technicalities. I remember them for you.
Project review
I check the technical state: package versions, server configuration, backups and security holes. You get an honest list of what needs attention.
The SLA
We agree the scope and the guaranteed response time - 24 hours on business days. You know exactly when I act and what falls outside the scope.
Ongoing care
I monitor, I update and I keep an eye on the backups. When something needs your decision, I ask. When it does not, I do it and tell you afterwards.
Contact without a hotline
You write to me directly. No ticket system and no first line of support that forwards your question to somebody else.
What you get
Peace of mind at a predictable price.
Concrete work, not "technical support" understood as a promise with nothing behind it.
A response within 24 hours
Guaranteed by contract, on business days. You write to me and the reply comes from the same person who knows your code, not a consultant reading a script.
Updates without the risk
I raise Next.js and React packages before they turn into a security hole. Every update goes through tests before it reaches production.
Backups and restores
Regular backups and a restore path that has actually been tested, back to the last working state. A backup nobody has tested is not a backup.
Monitoring and the server
I watch availability, certificates and performance. I learn about an outage from the monitoring, not from your customer.
Comparison
Unattended, or looked after.
The same site, two different scenarios on the day something falls over.
An unattended site
A site under care
You hear about the outage from a customer
I hear about the outage from the monitoring
You look for a developer once it is already burning
A response within 24 h, guaranteed by contract
Packages age along with their vulnerabilities
Updates tested before they go live
A backup - assuming there is one at all
Regular backups and a tested restore
The cost of an outage is unpredictable
A fixed, predictable monthly fee
Pricing
What peace of mind costs.
A fixed monthly fee instead of a bill after the outage. I look after projects I know - an existing site I take on after a technical review.
Maintenance and hosting (SLA)
Server, monitoring, backups, updates and a response within 24 h on business days.
fromPLN 300
monthlyTechnical review of an existing site
A check of the packages, the server, the backups and the security holes. You get a list of concrete fixes - even if somebody else built it.
On request
FAQ
Before you ask.
The scope of the care, the costs, code ownership and editing content yourself.
A website is an investment - make sure it keeps working.
Write to me and I will review your project and tell you plainly what needs attention and what can safely wait.