• Моніторинг · Uptime Kuma

Monitoring: you should learn your site is down from us, not from a customer

The site went down at two in the morning and came back at ten, together with you. For eight hours the store was shut, the advertising kept running, the money kept going. Nobody noticed a thing — except the people who wanted to buy during those hours. The worst part of such outages is not their length but that nobody knows about them: the reports show only a dip in orders, which gets written off to the season. Monitoring turns that into a message at 02:03.

See how it works
Price
after a free audit
Guarantee
30 days after project sign-off
Focus
sites and stores, mostly OpenCart
after a free audit
Price
30
Guarantee

days after project sign-off

sites and stores, mostly OpenCart
Focus
3
Timeline

to 15 working days to set up

free review of the critical points
Start
30
Warranty

days from the date the acceptance act is signed

within 2 hours
Reply
under a written contract
Terms
What's included

Complete list of work and what you get as a result

  • availability checks at an agreed frequency with a notification on failure
  • watching the key pages — catalogue, product card, cart — not only the home page
  • checking the content rather than the response code alone: a page can return 200 and be empty
  • a warning about the certificate and the domain several weeks before they expire
  • a response-time threshold after which a warning arrives before an outage
  • a check of the order scenario, if payment or the cart are critical
  • a rule for who gets notified and where, separately for nights and weekends
  • protection against false alarms: one failed check is not yet a reason to wake somebody
When this service isn't right

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

  • removing the cause of an outage — that is separate work with a separate estimate
  • a guarantee of uninterrupted site operation
  • responsibility for the work of the hosting, the carrier or the payment system
  • a person on call by the phone around the clock
  • promises of a specific uptime percentage
Who it's for

Situations where this service delivers results

Scenario 1 of 4

A store taking orders around the clock

Almost everyone gets night orders, and it is at night that outages stay unnoticed longest. The difference between one hour and eight is a notification.

We'll review your situation in a free audit
Free review of the critical points

We establish what genuinely has to be watched: checking everything indiscriminately is expensive and pointless.

What we measure

  • What stops ordersNot the site in general but specific places: the catalogue, the cart, payment. A blog going down and checkout going down are events of different weight.
  • Whether there were outages beforeIf there were, it matters how they were noticed. The answer «a customer phoned» is the most common and the most expensive.
  • Who will respondA notification with no recipient is just noise that quickly starts being ignored. This has to be decided before the setup.
  • What to do at nightTo wake somebody or wait for morning is the owner's decision, and it differs for a store with night orders and for a corporate site.
  • Whether a scenario is neededA page check is cheap. Going through the cart and payment costs more, but only that catches «the site works but you cannot buy».
  • What about the domain and certificate datesThe most galling outages are not technical. The domain or the certificate simply expires, and the site disappears for days because of a forgotten date.

What you get

  • a list of what is worth watching, and why exactly that
  • the notification rule: who, when and about what
  • an estimate of the setup and of ongoing support
  • an honest answer if a free tool is enough

Timeline: 1–2 working days

Why is it free

Half the sites are covered by a simple check that can be set up free of charge in an hour. We would rather not sell something complicated where something simple is enough.

What's next

You get the list and the notification rule. Then you decide for yourself — the document stays with you.

Short form: your contact and site URL

  • 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.

  • European clients

    Among our work — projects for 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.

What affects the price

Why two seemingly identical tasks are priced differently

  • Number of checksOne home page is a minute of work. A dozen addresses with different content expectations already have to be described and maintained.
  • Scenario checksThe main driver. Going through the cart and payment automatically is a small program that has to be fixed every time the checkout changes.
  • FrequencyOnce every five minutes and once every thirty seconds mean different load and different cost. For most stores, minutes are enough.
  • Where it runsAn external service is simpler. Your own system on your server does not depend on somebody else's subscription, but it has to live somewhere.
  • Notification rules«We write to Telegram» is cheap. Different recipients for nights, weekends and kinds of event is already separate logic.
  • Ongoing supportA one-off setup and continuous watching with our response are different arrangements. The second is paid monthly.
Cases

Tasks and results in numbers — all metrics measured by us

the agency's own CRM: deals, contracts, invoices, acceptance acts, projects and a client portal

Task
Stop running the agency in chat threads and spreadsheets: bring deals, versioned contracts with approval, invoices and acts, projects, licences for our own products and client communication in messengers into one system — and make documents be born from data rather than typed in by hand.
Solution
An application on Next.js 16 with Supabase (authentication and RLS) and Prisma. A contract builder with templates, versions, comments and conditional option blocks; signing a contract automatically produces the invoices and the act. Document exchange with Vchasno, National Bank rates with daily snapshots for converting EUR into hryvnia on the invoice date, bank receipts, fiscalisation through Checkbox. Client communication in Telegram and Viber with a single history. A separate circuit for our own products: licences, deployments, domains, support tickets. 35 background jobs cover the routine: reminders about invoices and meetings, digests, lead scoring, health monitoring of integrations and backups, synchronisation with Vchasno.
Result
As of 02.08.2026 the system runs in production (first server response 188 ms — the fastest response among all the projects we have measured). 121 dashboard pages across 38 sections, 489 server routes, 20 tables in the data schema, 11 enumerations and 27 classifier types, 35 scheduled background jobs. 958 commits over 10 months of continuous work. Data exchange is set up with roughly two dozen external systems.

a sample of 41 Ukrainian online stores

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
Measurement 2026-08-08, 39 stores: PHP without security support: 3 sites out of 39; no usable sitemap: 6 sites out of 39; sitemap pointing at another domain: 1 site out of 39.

Did not find your case?

Describe how it works on your side — we will tell you whether “Site availability monitoring” 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:3–15 days

  1. Reviewing the critical points

    1–2 working days

    We determine what, when it goes down, actually stops orders. The list comes out shorter than people expect, and that is good: less noise in the notifications.

  2. Notification rules

    1 working day

    We agree who gets a message and where, what to do at night, and after how many failed checks to raise the alarm.

  3. Setting up the checks

    1–4 working days

    We set up availability and content checks, response-time thresholds, and warnings about the certificate and the domain.

  4. Scenarios

    2–7 working days

    If needed, we build automatic passage through the cart and payment. This is the most useful and the most fragile part: it breaks together with the markup.

  5. Running in

    3–5 working days

    For a week we watch the false alarms and adjust the thresholds. Monitoring that cries wolf stops being read within three days.

  6. Handover

    1 working day

    We show how to change checks and recipients yourselves, and what to do on each kind of notification. Then the 30-day warranty from the date the acceptance act is signed applies.

Technologies & integrations

What we build on and what it connects to

Stack

  • Uptime Kuma
  • Prometheus
  • Grafana
  • nginx
  • Linux
  • PHP
  • Node.js
  • PostgreSQL
  • MySQL
  • Docker
  • Git
  • SSH

Integrations

  • Telegram
  • Email
  • Slack
  • Google Analytics 4
  • Let's Encrypt
Monitoring or hearing it from customers

How this option differs from the alternative

Time to reactionminutes
Night outagesvisible
Ad spend during an outagecan be stopped
Complexityneeds setup and a notification recipient
When you can do without itoverkill for a site with no orders and no advertising
What we need from you

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

  1. which pages and scenarios are critical specifically for orders
  2. who should receive notifications and during what hours
  3. what counts as an outage and what as acceptable slowness
  4. whether there are night orders and whether they justify waking somebody
  5. who responds to notifications on your side
  6. who on your side accepts the work

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

Does the hosting not watch this itself?

The hosting watches itself, not your site. The server can be running flawlessly while the store returns a database error or an empty page. Formally everything is fine; in practice you cannot buy. That is why we check the page content as well, not only that the server responded.

Will you fix it when it goes down?

Not as part of this work. Monitoring reports rather than repairs — a deliberate separation, so you understand what you are paying for. Responding and removing causes is support, a separate arrangement. We do not switch it on silently and invoice afterwards.

Why not check everything, every second?

Because noise kills monitoring faster than its absence. When twenty messages a day arrive, people stop reading them within a week — and miss the real outage too. So we deliberately keep the list of checks short and run the thresholds in.

What is a scenario check and what is it for?

It is when a program adds a product to the cart itself and gets as far as payment. Only that catches the nastiest case: the site opens, pages are served, and an order cannot be placed. The downside is that such a check breaks every time you change the checkout.

Wake somebody at night or not?

That is your decision, and it has to be made in advance. For a store with night orders and active advertising — usually yes. For a corporate site — no, a message by morning is enough. We build different rules for different hours rather than one for everything.

Do you guarantee the site's availability?

No. We own neither your hosting nor the network links, and we cannot promise an uptime percentage. What we do guarantee is different: that you learn about an outage from the system rather than from a buyer, and can decide what to do straight away.

How much does it cost per month?

It depends on whether you need only the system or our response as well. The system itself can be set up so that it costs nothing beyond your server. Continuous watching with a response is a separate monthly arrangement, and we name the sum after the review.

How long does the setup take?

3 to 15 working days. Simple availability checks are a day or two. The timeline is set by cart-passage scenarios and by the week of running in, during which the thresholds are adjusted to remove false alarms.

Let us work out what you genuinely need to watch

We will determine the critical points and the notification rule. The review is free, we reply within 2 hours.

From measured casesAs of 02.08.2026 the system runs in production (first server response 188 ms

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.