The certificate expires on a Friday
The browser shows a red warning on every page, the site is technically working, and the person who could renew it is on holiday. Two days of a scary screen cost more than a year of care.
We keep your site, bot and mail working: monitoring, updates, backups that have actually been restored, renewed domains and certificates — and a living person who answers when something breaks.
Nothing, for months. That is exactly the problem: it accumulates quietly and comes due all at once, usually on the worst possible day.
The browser shows a red warning on every page, the site is technically working, and the person who could renew it is on holiday. Two days of a scary screen cost more than a year of care.
It was being made every night for a year and a half — of the wrong directory. You find that out on the one day you need it, which is also the day the alternative is retyping everything from memory.
Changing a price or a phone number means finding the person who built it, agreeing a rate for twenty minutes of work and waiting for a slot. Meanwhile the wrong number stays on the site.
It is deliberately unexciting. Most of the month you should not notice us at all — and that is what the subscription buys.
What you have, where it stands, whose the domain is, when the certificate expires, where the backups go and who has the keys. Half the incidents in a small business come from nobody knowing this.
Availability, response time, certificate and domain dates, disk and errors in the logs. The alert comes to us, not to you — you already have a job.
Updates and security patches, renewals, backups — and once a quarter we restore one of those backups onto a test server. A copy that has never been unpacked is not a copy.
What was done, what was updated, what hours went where and how much of the quota is left. Without this the subscription looks like money paid for silence — and it gets cancelled first.
The list is short and closed on purpose: everything outside it is named honestly as extra work, at a rate, in advance.
The site, the bot, the mail and the API — checked continuously. If something stops answering, we know within minutes and start before you have written to us.
Daily copies, kept away from the server they came from, and a quarterly restore onto a test machine with a note in the report saying how long it took.
Dependency updates, patches for known vulnerabilities, and versions kept close enough to current that an upgrade never becomes a rewrite.
Renewal on time, in your own name and your own account. A domain registered to the contractor is a hostage situation waiting for a disagreement.
Change a text, a price, a photo, add a page, fix a phone number. Hours are counted openly, and what is left is shown in the report — no arguments at the end of the month.
When something does fall over, you get a plain account afterwards: what happened, why, what we did and what was changed so it does not happen again.
Care is sold by trust, and trust dies on the first unspoken condition. So the uncomfortable parts are here, on the sales page.
Unlimited «small edits» is how this product dies: the studio starts avoiding the client, and the client feels it. Hours above the quota are billed at a rate agreed in advance — which is why nobody has to be avoided.
A new section, a new integration, a redesign — that is a project with its own estimate. Calling development «support» is how a monthly fee quietly turns into a full-time obligation.
The domain, the server and the payment accounts are registered to you; we work with access you can revoke in one evening. Leaving should be a decision, not an operation.
The difference between the plans is response time and the size of the quota, not the level of attention.
For a site that mostly stands still and simply must not fall over.
For a business whose site, bot and mail all matter and all belong to different generations.
When downtime is measured in lost orders and an evening is not an acceptable answer.
We already do all of this for our own clients. What is missing is the accounting that turns it from a favour into a product.
Monitoring, metrics, alerts and support in the client cabinet — running for our own projects.
Hour accounting per client and a monthly report — without them Care is a verbal agreement that ends in an argument.
A maintenance schedule: updates, restore drills and renewals planned rather than remembered.
A status page for your clients and a public incident history — the thing that keeps trust during an outage.
Usually yes, after an inspection: we look at what it is built on, where it stands and what state it is in, and then say plainly what has to be put in order first. Taking responsibility for something we have not looked at would be dishonest.
We tell you before it runs out, not after. Anything beyond it is either agreed at the rate or waits for the next month — your choice, made with the numbers in front of you rather than in an invoice at the end.
No — and on purpose. The server and the domain are registered to you and paid by you, so that leaving us never means losing your infrastructure. We can choose it, set it up and manage it, but we do not sit between you and it.
The alert reaches us first. We start on it, tell you what has happened and what we are doing, and afterwards send a write-up: cause, actions, and what was changed so that it is not repeated. Silence during an incident is the only unacceptable behaviour.
Yes, at the end of any paid month, and we hand over the inventory, the access and the backups. A subscription held by an exit barrier rather than by usefulness is not worth keeping — for either side.
Tell us what is running and who looks after it now. We will do an inspection and send back a plain list: what is in order, what expires soon, and what would fall over first — regardless of whether you take a subscription afterwards.