01
Basic
from $120/ mo
Updates, backups, uptime monitoring and a regular report, for a stable site without a constant queue of changes.
After a technical review, we turn scattered fixes into managed support. Your team knows what we monitor, what work is included, where the backups are and who steps in when something breaks.
// what we do
01
from $120/ mo
Updates, backups, uptime monitoring and a regular report, for a stable site without a constant queue of changes.
02
from $350/ mo
Everything in Basic plus an agreed volume of content and technical tasks. We set priorities together before each cycle.
03
from $650/ mo
The contract separately defines critical events, coverage hours, escalation channels, response time and what depends on hosting or third-party services.
You get the price and terms after we review the platform, access, change log and the level of responsibility you need.
Yes, after a technical review. We check the platform, access, backups, dependencies and known bugs, then decide whether we can take responsibility for supporting it.
Not by default. Support keeps the current system running and adjusts it. A new interface, structure or major feature becomes a separate task with its own estimate.
We define it in the contract. For example, the site is down, customers can't place an order, or logins fail across the board. Different systems have different critical scenarios.
No. Availability depends on hosting, the domain, payment providers and other external services. We commit to monitoring, response and a recovery procedure for the part we control.
Through the agreed channel, with a description, the URL, the expected result and a priority. We give a deadline after the estimate, unless the response terms already set one.
Keeping technical SEO settings intact can be part of support. Keyword research, content and ongoing SEO promotion are a separate service.
We decide after the review. In practice the team supports the platforms it builds on, but a specific version or custom modules can limit the format.
It depends on the platform, the number of environments, critical scenarios, coverage hours, update frequency and the expected volume of tasks.
A list of completed changes, how much of the agreed scope was used, check results, open risks and the next priorities.
Leave your name and a phone number or Telegram handle. We'll ask about your platform, critical scenarios, access and current task queue, then suggest a support format.
By pressing the button, you agree to the privacy policy
Kharkiv · Kyiv
// in detail
Technical website support starts with deciding who is responsible for what. You need to know who controls the domain, hosting, code, CMS, third-party services and analytics. Without that, even a simple bug turns into a hunt for logins and former contractors. During the initial review we map the system, check the backups and record the critical scenarios.
Routine work can include updates, backup checks, uptime monitoring, log reviews and going through open tasks. How often depends on the platform and the risk. Before an update we agree how we'll test it and how we'll roll it back. An installed monitoring plugin doesn't mean anyone receives the alerts or responds to them.
For backups we set what they contain, how often they run, how long they're kept and where they're stored, separate from the main server. We test restores against an agreed scenario. If an external service keeps part of the data on its side, we handle its backups separately. You should know what data could be lost between two backups and who decides on a restore.
The task queue keeps the description, priority and test result for each item. A content swap can be done within the existing template, while a new page type or integration gets estimated as development. This line protects both sides from the "small edit" that changes data, design and business logic all at once.
Critical systems need defined events, coverage hours, an escalation channel and a set time to respond. Promising to fix any failure within the same deadline wouldn't be honest. After diagnosis we report the status, the part we control and the next step. If the failure is with the hosting provider, payment system or another supplier, we coordinate the request within our access, but we don't claim control over their timelines.
Before taking a site on, we check versions, the repository, environments, domain, hosting, licenses, admin accounts and known bugs. We suggest fixing critical risks before regular support begins. If the system has no source code, documentation or safe way to update, we may offer a limited format or decline responsibility for a specific part.
Support keeps the site working and makes agreed changes. Website development creates new functionality or substantially rebuilds what's there. SEO promotion covers a separate plan of work on visibility and content. These services can run together, but they have different outcomes, budgets and owners.
The price of website support depends on the platform, the number of environments and the size of the codebase. Critical features, integrations, coverage hours and the expected task queue matter too. After the review we agree on the scope, exclusions, access, the report and how extra tasks get estimated. We set the start date once the critical risks and the handover of access are clear.
You get a defined process: a task channel, named owners, a change log, routine checks and a plan for the next cycle. Access and data stay with the owner of the system.
Handover and change control. We collect access and details for the domain, hosting, repository, CMS, analytics, third-party services and licenses, plus contacts of previous contractors. Access is transferred securely and with the minimum rights needed. If an important piece is missing, we record the risk and an alternative, such as restoring access, a new environment or a limited support format. Every task has a description, a URL or component, the expected result and a way to verify it. Before a risky change we define the backup, the environment and the rollback plan. After release we test the agreed scenarios and log the changes. When the work ends, we hand over access, the log, documentation, open tasks, backup status and risks. We revoke our own unneeded access through an agreed procedure, so you don't depend on a manager's personal account.
Monthly planning. At the start of each cycle we agree on mandatory checks and the queue of changes. A critical event can change the order, but its definition is already written into the terms. At the end you see how much of the agreed scope was used, completed and carried-over tasks, backup and monitoring results, and risks. If the queue grows beyond what support covers, we propose a separate development stage, so an architectural problem doesn't get patched with small fixes for years.
Third-party providers. Hosting, domains, payment systems, email and external APIs come with their own terms and support. We document requests and coordinate within our access, but we don't promise deadlines on another company's behalf. You keep ownership of accounts and billing profiles, so a change of contractor doesn't block the service.
Incidents and planned work. A broken checkout, an expired certificate and a routine content update follow different routes. For an incident we record when it was detected, its impact, the part we control, the actions taken and the recovery status. Once things are stable, we look at the root cause and set a task so it doesn't happen again. A planned change goes through an estimate, a backup, testing and a calm release. That way urgency doesn't become the default way of running the site.