Support

Website Maintenance and Technical Support

Keep your website and connected services working after launch. We match the package to critical business functions and the current technical situation.

from 49 000 KZT / month

Ask our Telegram bot

Support packages

Choose the support level based on business criticality

Basic suits stable websites, Extended adds deeper integration and improvement support, while SLA is for commercially critical systems. Response and recovery commitments are defined only after technical assessment.

Support package49 000 KZT / month

Basic

For stable websites, landing pages and smaller corporate websites that need regular technical care.

Baseline monitoring and maintenance to keep the website available, forms working and routine technical issues under control.

Website and key-form checks
Basic monitoring
Backups within the agreed infrastructure
Dependency updates and security fixes
SSL checks within the KAMOZA responsibility area
Small technical fixes
Project health recommendations
Standard request priority

Support package89 000 KZT / month

Extended

For projects where the website, enquiries and integrations are part of day-to-day business operations.

Broader support for important integrations, working scenarios and regular small improvements to a live product.

Everything in Basic
Monitoring of important integrations
API and webhook scenarios
Key enquiry and analytics events
Integration error diagnosis
Regular small improvements
Support for existing product functionality
Higher request priority

Support packagefrom 149 000 KZT / month

SLA

For commercially important systems where response and recovery rules need to be agreed individually.

Support for critical services under an individually defined operating model, priority structure and SLA terms.

Everything in Extended
Individual SLA terms
Priority incident handling
Extended monitoring and logging
Production deployment control
Update and recovery procedures
Support for critical changes
Individually defined monitored services

Who it is for

For businesses that need a clear approach to checks, updates and fixes for a working website or digital service.

Scope of work

Technical support with a defined scope, request channel and responsibility boundaries.

Monitoring of agreed website, form and critical scenarios.
Dependency updates and security fixes within scope.
Backups within the agreed infrastructure.
Diagnosis and fixes within the KAMOZA responsibility area.
Recommendations and small improvements according to the selected package.

Getting started

What helps us start

No long preparation: just the information needed to agree the task and begin.

Define what needs support

List the website areas, forms, integrations and business-critical scenarios that need to stay operational.

Review access and infrastructure

We inspect hosting, domain, backups, external services and the technical access needed to support the project safely.

Set priorities

Clarify whether the main need is stability, updates, small improvements, integration support or a stricter incident process.

Process

How the launch works

Agree the task and estimate first, then move toward launch in clear stages.

Step 1

Technical assessment

Review code, infrastructure, access and critical scenarios to define the support boundary.

Step 2

Agree control points

Define the forms, integrations, backups, updates and other important scenarios that need monitoring.

Step 3

Handle updates and small fixes

Maintain the system and complete package-level technical work in a planned way.

Step 4

Check stability after changes

Verify agreed critical scenarios after updates and support work.

Step 5

Operate through a prioritised queue

Requests and technical tasks move through the agreed support process and priority level.

Support boundary

Technical support is not unlimited product development

Small fixes and improvements may fit within a package. Large new features, redesigns, new modules or major new integrations are estimated as separate development work.

Work estimated separately

New customer portals, major sections, redesigns, new CRM integrations or standalone modules are treated as separate development phases.

Projects built by another team

We can take over an existing project after assessing code, infrastructure, access, backups and major risks.

Common support cases

Support is most useful when a live system already matters to operations

Price: from 449 000 KZT

Useful when a multi-page website needs recurring content, form and integration maintenance.

Corporate website

Price: from 799 000 KZT

Useful when orders, payments and critical store scenarios need ongoing technical control.

Ecommerce website

Price: from 349 000 KZT

Useful when the website depends on external services and integration reliability matters to the business.

API and integrations

Price: from 549 000 KZT

Help buyers find the right product and contact your team. Categories, search, specifications and photos in a catalogue you can manage yourself.

Product catalogue

FAQ

Common questions before starting

How much does website support cost?

Support is billed monthly. Current entry pricing is from 49 000 KZT / month.

What is the difference between Basic, Extended and SLA?

Basic focuses on routine website stability. Extended adds deeper integration monitoring and ongoing small improvements. SLA is designed individually for commercially critical systems.

What is the SLA response time?

There is no single response time for every project. Response and recovery commitments are defined only after the system, critical services and required support schedule are assessed.

What is not included in support?

Major new features, redesigns, standalone modules and substantial new integrations are estimated separately.

Can you support a project built by another developer?

Yes, after a technical assessment of code, infrastructure, backups, access and critical scenarios.

Is support billed monthly?

Yes. Package prices are monthly. SLA pricing and operating terms are defined individually after technical assessment.

Next step

Choose support for your project

Send the project link and describe critical features and current issues. After assessment, we will propose a package and working arrangements.