A website or app needs regular care after launch, even when nobody changes it. The platform, plugins and code libraries release updates, the security certificate that protects visitors' connections expires, contact forms stop sending, and a browser or phone update breaks a page that worked last month. Without someone responsible, customers find these problems first, and small fixes wait until they become urgent.
Kemlat takes on the regular care of your website or app under a monthly service agreement. We start by reviewing its current state, then apply updates in a safe order, fix faults, watch availability and security, and report every month on the work done. You know what is covered, how fast we respond, and which requests need a separate decision.
How we work
- 01
Review the current state
We check the platform version, plugins or libraries, hosting, existing backups and known faults. We also confirm who has access and where the source code is kept. The result is a list of risks to fix before regular maintenance starts.
- 02
Agree coverage and response times
We write down which systems are included, how faults are reported, and how quickly each priority level gets a response. Work outside the agreement is listed so it can be estimated separately.
- 03
Apply updates safely
We take a backup first, then test updates on a separate copy of the site (a staging copy) where your setup allows it, before applying them to the live site. If an update causes a problem, we restore the previous version.
- 04
Fix faults and small changes
Reported faults are logged, given a priority and answered within the agreed response time for that priority, then fixed. Small content or layout changes covered by the agreement go through the same queue.
- 05
Monitor and report
We monitor availability, certificate and domain expiry dates, and security alerts. Each month you receive a short report on updates applied, faults fixed, any downtime, and items that need your decision.
What you receive
Initial health check
A written review of the current state of the site or app, with risks ranked by urgency.
Service agreement
Coverage, included systems, priority levels and response times, agreed in writing before work starts.
Preventive maintenance
Scheduled updates to the platform, plugins and libraries, with a backup taken before each round of changes.
Corrective maintenance
Diagnosis and repair of reported faults within the agreed coverage.
Monthly maintenance report
What was updated and fixed, any downtime, open issues and recommendations.
What changes for you
- Updates are applied on a schedule instead of only after something breaks.
- Faults are reported through one channel and answered within the agreed response times.
- You are warned about certificate and domain expiry dates before they lapse.
- You keep a monthly record of all work done on your website or app.
Where this service sits in the KEMLAT Method
Scope: Maintenance runs as an ongoing monthly service. New features, redesigns and major platform upgrades are outside regular maintenance and are scoped separately. Hosting and licence fees are paid to your providers unless agreed otherwise.
Questions clients ask
Can you maintain a site or app that another company built?
Yes. The initial health check shows how it was built and what needs fixing first. We need admin access, hosting access and the source code where there is one. If the code is in poor condition, we tell you before coverage is agreed.
What is the difference between preventive and corrective maintenance?
Preventive maintenance is planned work that lowers the chance of problems, such as updates, backup checks and expiry tracking. Corrective maintenance means fixing something that has already gone wrong, such as a broken form or an error page. The agreement covers both.
Does maintenance include new features?
No. Small changes listed in the agreement are included. New pages, features or integrations are estimated separately, so the monthly service stays predictable.
What do you need from us?
Access to the site or app, the hosting and domain accounts, and one contact person who can approve changes. It also helps when your team reports problems as soon as they notice them.
What happens if we end the service?
We hand back all access details, a record of the work done and notes on any open issues, so another team can continue without starting from zero.
Related services
All servicesStart with a conversation
Tell us where you are today. We will suggest the right first step, with no obligation.