Website Maintenance and Support Services

Tworzenie stron i aplikacji Skalowalne Bezpieczne Wydajność Niezawodne Długoterminowe wsparcie

Tworzenie stron i aplikacji

Software that is not maintained does not stay still - it degrades. Dependencies go out of support, certificates expire, a payment provider changes its API, and one morning the checkout returns an error nobody has seen before, in code nobody knows.

This is the service for a system that is already live and needs to stay that way. It does not matter whether we built it.

What maintenance actually covers

Security and framework updates, applied on a schedule and tested before they go live
Uptime and error monitoring, with someone looking at the alerts rather than a dashboard nobody opens
Backups verified by restoring them, which is the only way to know they work
Bug fixes and small changes inside an agreed monthly allowance
Performance checks, so the slow decline that nobody notices gets noticed

Taking over code we did not write

Most of this work starts with a codebase from another team, often with no documentation and nobody left to ask. That is normal and it is not a problem, but it is not free either.

A handover review first: what it runs on, what it depends on, what is out of support, and what will bite within a year
The findings written down and priced, so you can decide what to fix and what to live with
Access moved into your own accounts if it is sitting with a previous agency
Only then a support agreement, on a system we understand rather than one we are guessing at

How it is agreed

A monthly retainer with a stated number of hours, a response time that is written down, and a named person rather than a ticket queue. A quiet month is reported as a quiet month rather than billed as work that did not happen.

Najczęściej zadawane pytania

Will you support a site you did not build?

Yes, and most of what we support we did not build. It starts with a review of what is there, priced separately, because agreeing to keep something alive before knowing what it is made of would not be an honest offer.

What is the response time?

It is written into the agreement rather than implied. A checkout that is down and a misaligned button are not the same emergency, so the agreement separates them and says what each one means in hours.

What happens to unused hours?

They do not roll up indefinitely - a retainer that banks a year of hours is not a support agreement, it is a deposit. We would rather tell you the month was quiet.

Can you just be the backup?

Yes. Some clients keep an internal developer and use us for the platform work, the upgrades, and the weeks when that person is on holiday.

Tell us what you are running

The platform, roughly when it was built, and what worries you about it. If the answer to the last one is that nobody knows how it works any more, that is the most common answer, and the review exists for exactly that.

Zacznijmy projekt