Skip to main content
Noria Technologies

After it goes live

The year after launch is when it breaks.

The certificate expires on a Sunday. The disk fills up. The library with the hole in it needs patching. None of that is a project, which is why nobody plans for it - and why a customer always finds it first.

12 months
written into every build contract
Same day
reply on Operations
Restored
backups checked, not assumed

What it costs

Two levels, invoiced monthly in advance

The first month is invoiced with the final build payment, so nothing is ever handed over unwatched. Twelve months minimum, because the failures this prevents do not arrive on a convenient schedule.

Standard

per month

KES 45,000

USD 450 billed internationally

Monitoring and alerting, backups restored and checked on a schedule rather than assumed, security patching, and a reply inside two working days.

Operations

per month

KES 120,000

USD 1,200 billed internationally

Everything in Standard, plus two days of changes a month, a same-day reply, and a monthly sit-down over the reconciliation so the numbers are checked by someone other than the person who entered them.

monthly, twelve months from launch

Change work beyond the included days is quoted and signed before it starts, at a day rate, so a small request never turns into an invoice nobody agreed to.

What you get

What we do every month

Monitoring, tested restores, patching, and a person who answers - monthly, from the day you go live. The certificate expires on a Sunday. The disk fills up. The library with the hole in it needs patching. None of that is a project, which is why nobody plans for it - and why a customer always finds it first.

We find out before your customers do

Uptime, errors, and queue depth watched around the clock, with the alert going to a person who is paid to answer it. The first you hear of most problems is us telling you it is already fixed.

Backups that have actually been restored

A backup nobody has restored is a guess. We restore yours on a schedule and check the records came back whole, so the answer on the bad day is known in advance.

Security patching, on a schedule

The operating system, the framework, and every library underneath it. Most breaches are not clever - they are a known hole in a version that was six months out of date.

Changes without a new contract

On Operations, two days a month of real work - a new report, a changed rule, a field somebody needs. Small things get done instead of piling up until they justify a project.

The month end checked by someone else

On Operations, we go through the reconciliation with you monthly. Payments that did not match, invoices that sat unpaid, anything that looks wrong - found in the month it happened rather than at audit.

How it runs

What happens, step by step

We know when it goes down before you do, because the warning comes to us. Care runs for twelve months from launch and is written into every build contract - not offered in an email six months later, when the damage has already been done.

01 It starts the day you go live Care is in the build contract from the beginning, and the first month is invoiced with the final build payment. Nothing is ever handed over unwatched.
02 We watch it Monitoring, patching, and restore checks run whether or not anything is wrong. Most months you hear from us once, in a short written summary.
03 You call us when you need us Two working days on Standard, same day on Operations. You are talking to the people who built it, not to a queue.

When you should not buy this

We will not take Care on a system we did not build and have not reviewed. Being on call for code we have never read is a promise we cannot keep, so the honest route in is a Rescue review first.

What this is actually for

Every one of these happens after the invoice is paid

None of them show up while somebody is still building it. All of them show up once you have real customers, which is the point at which most people no longer have anybody looking.

The certificate expires on a Sunday Every browser starts warning your customers that the site is unsafe, and it is nobody's job to have noticed. We watch the expiry dates, so it renews before anyone sees it.
A known hole sits unpatched for six months Most breaches are not clever. They are a published vulnerability in a version that nobody updated because updating was not on anybody's list.
The backup has never been restored Nearly everyone has backups switched on. Almost nobody has tried using one. We restore yours on a schedule so the answer is known before the bad day.
It gets slow and nobody is measuring It was quick when it was empty. A year of records later the same page takes ten seconds, and the only people who know are the customers who gave up.
The month end stops adding up Payments that did not match, invoices sitting unpaid, a rule that quietly stopped firing. Found in the month it happened rather than at audit.

We will not take Care on a system we did not build and have not reviewed. Being on call for code we have never read is a promise we cannot keep, so the honest route in is a Rescue review first.

Not what you needed?

Discovery - Change your mind on paper, not in week nine. A week with the people who would build it, working out what actually needs building - before anyone writes code you paid for. Review - You built something. Will it survive real customers? A review of software you built with AI, inherited, or quietly stopped trusting - before it holds real money. Build - Built to be used every day, not demonstrated once. Customers, orders, stock, invoices, payments - built around how the work already moves, by people who are still here next year.

Talk about keeping it alive

If we built it, Care is already in your contract. If somebody else built it, the honest route in is a review first - we will not go on call for code we have never read.

  • Monitoring and alerting
  • Restores tested, not assumed
  • The people who built it

Or reach us directly

Weekdays, and we answer the same day.