• Maintenance · PHP and MySQL

Technical support for a website: so it does not break quietly, and not while you are not looking

A site without a store breaks differently from a store. There are no failed orders and no cart that fell over — so the breakage is not visible immediately. The form stopped sending enquiries, and there simply are no enquiries: the phone is silent, and the cause gets sought in the advertising. Technical support exists for exactly that gap: to notice before the client does, and to update the platform before somebody else makes use of the old version.

See how it works
Price
after a free audit
Guarantee
30 days after project sign-off
Who it is for
sites without a store: corporate, services, landing pages
Price
after a free audit
Guarantee
30
days after project sign-off
Who it is for
sites without a store: corporate, services, landing pages
Format
monthly, not tied to a number of requests
Start
free technical check
Warranty
30
days from the date the acceptance act is signed
Reply
within 2 hours
What's included

Complete list of work and what you get as a result

  • updating the platform and modules on a copy first, then on the live site — so an update does not become the cause of downtime
  • backups with periodic restore verification: a backup that does not deploy is not a backup
  • availability monitoring: the alert comes to us, and we start looking into it before your call
  • checking the contact forms: a test send and confirmation that the email arrived
  • watching the domain and certificate dates, with renewal before they expire
  • checking the technical foundation: sitemap, availability to search, redirects after changes
  • small content corrections within an agreed volume: text, images, contacts
  • a work log and a monthly report: what was done, what changed, what needs your decision
  • a separate list of what is worth doing but falls outside support — estimated separately
When this service isn't right

What's not included — so there are no surprises at delivery

  • developing new sections, features and a redesign — a separate scope of work
  • filling the site with texts, products and photographs
  • promotion, advertising and work on search positions
  • paying for hosting, the domain and licences — those invoices stay with you
  • recovery after a hack, if the site was taken on already infected: a separate clean-up first
  • maintaining an online store: there are orders, payments and delivery there, and that is a different set of checks
Who it's for

Situations where this service delivers results

Scenario 1 of 4

The site was built and left alone

It works, nobody touches anything. This is exactly where quiet debt accumulates: overdue versions, forgotten modules, backups nobody has ever restored. The problem becomes visible at the worst possible moment.

We'll review your situation in a free audit
Free audit

Free technical check of the site

Before any arrangements we look at the state the site is in now. That is more honest than a retainer taken blind: half the first month's work is usually clearing out what has accumulated.

What we measure

  1. Versions of the platform and moduleswhether any of them no longer receive security updates
  2. Backupswhether they exist, how recent they are, and whether anybody has verified a restore
  3. Domain and certificatewhen they expire and in whose name they are registered
  4. Formsa test send with confirmation that the email arrived
  5. Technical foundationthe sitemap, availability to search, errors in the server log

What you get

  • a written list of the findings, split into «urgent» and «can wait»
  • an estimate of the first month separately from the monthly one
  • an honest answer on whether support is needed at all

Timeline: 1–3 working days

Why is it free

Without a check any figure would be invention: a site that has been cared for and a site nobody has touched for three years are different work.

What's next

After the check — a broken-down estimate and a contract with a fixed monthly sum.

Short form: your contact and site URL
Contract and paperwork

We work officially

Contract, act and invoice — for every project, not just large ones.

Trusted by6 brands

Trusted by: Kvant Energy, GYPSUN, Naturel Cosmetics, Pancer Protection, LUGI, BeeTech

Terms fixed in writing8 points

  • Contract, act and 30-day warranty

    Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.

  • Sole proprietor & bank transfer

    The contractor is a registered sole proprietor. Payment by invoice with closing documents.

  • Rights & access — yours

    Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.

  • Client portal instead of email chains

    During the project you get access to a portal: contracts, invoices, acts and project status in one place.

  • Sites in nine countries

    Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.

  • Verifiable numbers

    Every case in the portfolio comes with a link to a live site and a technical measurement.

  • Audit first, then pricing

    There is no price list on the site intentionally: the scope of the same work differs multiples between clients.

  • We say "no" when unsure

    If the task isn't ours or the deadline is unrealistic — we tell you upfront.

  • Contract, act and 30-day warranty

    Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.

  • Sole proprietor & bank transfer

    The contractor is a registered sole proprietor. Payment by invoice with closing documents.

  • Rights & access — yours

    Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.

  • Client portal instead of email chains

    During the project you get access to a portal: contracts, invoices, acts and project status in one place.

  • Sites in nine countries

    Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.

  • Verifiable numbers

    Every case in the portfolio comes with a link to a live site and a technical measurement.

  • Audit first, then pricing

    There is no price list on the site intentionally: the scope of the same work differs multiples between clients.

  • We say "no" when unsure

    If the task isn't ours or the deadline is unrealistic — we tell you upfront.

We sign NDAs on request. After completing the work, we delete our access to your services ourselves.

What affects the price

Why two seemingly identical tasks are priced differently

  • The site's state at the startthe main driver: a neglected site requires a separate first month
  • The platforman off-the-shelf CMS with live updates is cheaper than a custom site with no documentation
  • Number of modules and customisationsevery customisation is something that can break on update
  • Volume of small correctionsdetermines how many hours a month are set aside for content changes
  • Hostingordinary hosting and your own server require different work
  • Required response speedworking hours or round the clock — a different regime and a different cost
Cases

Tasks and results in numbers — all metrics measured by us

a sample of 41 Ukrainian online stores, of which 39 responded and a product page was checked on 30

Task
Assess the technical foundation of the stores: whether there is a usable sitemap and whether the platform gets updated.
Solution
An external measurement of the home page and one product page from the sitemap: traces of features in the HTML, product markup, prices and attributes. The presence of a trace, not the quality of the implementation.
Result
Measured on 17 September 2026, 35 stores: PHP without security support: 2 sites out of 35; no usable sitemap: 7 sites out of 35; sitemap points to another domain: 2 sites out of 35.

Did not find your case?

Describe how it works on your side — we will tell you whether “Technical support for a website” fits and what it means in your situation. No brief and no call: one question, one answer.

Process steps

Transparent stages with approval at every step

Total duration:1–5 days

  1. Technical check

    1–3 days

    We look at versions, backups, the domain, the forms and the error logs. We compile a written list split into urgent and the rest.

  2. Gathering access

    1–3 days

    Hosting, panel, admin area, domain, email. We register everything in your name if it is currently otherwise, and record where everything lives.

  3. The first month

    5–20 days

    We close the urgent items: updates, backups with restore verification, monitoring, forms. This is the hardest month, and it is priced separately.

  4. The regular cycle

    monthly

    Updates on a copy, checking backups and forms, watching the dates, small corrections. Once a month, a report listing the decisions needed from you.

Technologies & integrations

What we build on and what it connects to

Stack

  • PHP and MySQL — the basis of most sites we take on
  • Nginx or Apache, Linux, SSH access to the server or hosting panel
  • Git for code changes, so any correction can be rolled back
  • Cron for regular backups and checks
  • SSL/TLS: watching the certificate date and correct redirection to https

Integrations

  • Google Search Console — to see indexing errors rather than hear about them from the client
  • GA4, if analytics is already in place
  • notifications to Telegram or email about the site being unavailable
  • SMTP to verify that emails from the forms are actually sent
Monthly support versus a call-out when it breaks

How this option differs from the alternative

We call somebody when it breaksOur approach
When you learn about a breakagefrom a client or from enquiries drying upfrom us, from a monitoring alert
Updateswhen they can no longer be postponedregularly, on a copy first
Backupsusually present, but whether they deploy is unknownpresent, and the restore is verified
Cost of an incidenturgency always costs morewithin the monthly sum
History of changesin the memory of whoever fixed it this timea work log and a monthly report
What we need from you

We can't start without this — best to prepare in advance

  1. access to the hosting, the control panel and the site's admin area
  2. where the domain is registered and in whose name
  3. a list of the forms and the addresses enquiries should reach
  4. a contact for the person who decides on changes to the site
  5. information about the previous contractor, if the access details are incomplete
If something is missing — let us know, we'll help you gather it or do it as a separate task.
FAQ

Most frequently asked questions — with concrete answers

How is this different from maintaining an online store?

In the set of checks. A store has orders, payments, delivery and product feeds — there what breaks costs money immediately, and has to be checked daily. On a site without a store the breakage is quiet: the form goes silent, a page returns an error, the certificate expires. If you have a store, you need a different scope — there is a separate page about monthly store maintenance in this section.

How many corrections are included in a month?

The volume of small corrections is fixed in the contract — changes to texts, images, contacts. Anything beyond it is estimated separately, and we tell you before the work rather than in the invoice at the end of the month.

You make backups — but who verifies they work?

We do, periodically and in practice: the backup gets deployed in a separate environment. This is not a formality. A backup nobody has restored is, at the moment of an incident, equally likely to turn out empty or corrupted.

The site is old and has not been updated in a long time. Will you take it on?

Yes, but we will honestly split it in two: the first month is clearing out the accumulated debt, after that a regular cycle. These are different volumes, and merging them into one sum would be wrong. How large the first month will be is what the free check shows.

What if an update breaks the site?

That is exactly why an update goes onto a copy first. If something behaves oddly after the update, we see it before it reaches the live site. If a problem does appear in production, the rollback is done from a verified backup, and mistakes that are our fault are fixed under the warranty.

Will you take the access details for yourselves?

No. The domain, hosting, repository and analytics are registered in your name — that is a matter of principle. We work under our own accounts inside your services, and when the cooperation ends we delete our access and tell you we have.

Does this include promotion?

No. Support is about the site working, not about positions. We make sure the technical foundation does not get in search's way: the sitemap, page availability, redirects after changes. But working with demand and positions is a separate service, and we give no promises about places in the results at all.

How quickly do you react if the site goes down?

We learn about unavailability from monitoring, not from your call. We answer requests within two hours — that is one figure across all our services. The response regime outside working hours is fixed separately in the contract.

Let us look at the state the site is in now

We will check the versions, backups, forms, domain and certificate, and say what is urgent and what can wait. The check is free, we reply within 2 hours.

View cases
  • Reply within 2 hours
  • No commitment
  • We work under a contract

There is no price list on the site on purpose: the same work differs several times over between two clients, and a “from” figure explains nothing in that case. First a free audit — we count your pages, duplicates and speed — then we name the sum and the deadline and fix both in the contract.