Ongoing · Subscription

Someone has to
keep it running.

Software does not stay finished. Dependencies age, certificates expire, hosting drifts and small changes pile up until they need a new contract. A care plan is a fixed monthly amount that keeps your project patched, backed up and watched — and, on the larger plans, gives you a pool of engineering hours you never have to negotiate for.

Price: From €150/month
Billing: Monthly in advance
Notice: 30 days
Starts: After hand-over

Ask about a care plan Compare the three plans

Monitoring runs every day Cancel with 30 days' notice

Scroll

Managed hosting TLS certificates Dependency updates Daily backups Restore tests Uptime checks Error logging Security patches Staging parity Monthly report Development hours

What the monthly fee buys

Maintenance is work,
not a promise.

Every plan is made of the same six things. The difference between them is how much engineering time sits on top and how quickly we come back to you.

Managed hosting

The server, the runtime version, the TLS certificate and the DNS records stay current and stay ours to keep current. You are not the person who finds out a certificate expired.

Core and dependency updates

Framework, library and CMS updates applied on a schedule — on staging first, with a rollback ready for the update that misbehaves. Security patches are not queued behind anything else.

Daily backups, actually restored

A backup is only worth what a restore proves. Copies run daily and we restore one onto a throwaway environment every month, so the recovery path is known before anybody needs it.

Uptime monitoring

Availability checks run from outside your own infrastructure and application errors collect in one place, so an outage shows up in a log rather than in a customer's e-mail.

Development hours

Active and Priority include a monthly pool of engineering time for the changes that never justify a new contract: another page, one more field on a form, a report, a small fix.

A monthly written report

One page at the start of each month: what was updated, what broke, what was restored, how the hours were spent and what we would do next. No dashboard login required to read it.

Three plans · one price list

Same engineers.
Different amount
of their time.

Billed monthly in advance, cancellable with 30 days' written notice. You can move up or down a plan from the start of any month.

PLAN 01

Essential

€150/month

The baseline. Your project stays hosted, patched, backed up and watched — nothing more, nothing hidden.

Managed hosting, TLS and DNS records
Core and dependency updates on a schedule
Daily backups with a monthly restore test
Uptime monitoring and error logging
Monthly written status report

No development hours are included. Change requests are quoted separately before any work starts. Response-time target: 2 business days.

Ask about Essential

Our recommendation PLAN 02

Active

€400/month

Everything in Essential, plus a standing pool of engineering time — so a small change takes a message, not a new agreement.

Everything in Essential
8 hours of development work each month
Response-time target of 1 business day
Staging environment kept in sync with production

Hours are counted per calendar month and do not carry over. Anything larger than the remaining hours is quoted before we touch it.

Ask about Active

PLAN 03

Priority

€900/month

For a system the business cannot be without for an afternoon: your work goes to the front of the queue and the response time is written down.

Everything in Active
20 hours of development work each month
Response-time target of 4 business hours
Priority queue ahead of other scheduled work
A quarterly technical review call

Hours are counted per calendar month and do not carry over. Out-of-hours cover is possible, but only where it is agreed separately in writing.

Ask about Priority

Prices are per month and exclude VAT where VAT applies. A care plan starts after hand-over of a project we built — or, for a project we did not build, after a technical audit from the Start package.

Line by line

What changes
between the plans.

Care plans compared
Included	Essential · €150	Active · €400	Priority · €900
Managed hosting	Yes	Yes	Yes
Core & dependency updates	Yes	Yes	Yes
Daily backups + restore test	Yes	Yes	Yes
Uptime monitoring	Yes	Yes	Yes
Development hours / month	—	8 hours	20 hours
Response-time target	2 business days	1 business day	4 business hours
Priority queue	—	—	Yes
Monthly report	Yes	Yes	Yes

The response times above are targets, not guarantees, and they are counted in Estonian business hours on working days. They describe how quickly a human answers and starts looking — not how quickly every problem is solved, because that depends on what the problem turns out to be. A binding availability guarantee can be agreed separately in writing.

Boundaries, written down

What a care plan is,
and what it is not.

A subscription only works when both sides know where it stops. Here is the line we hold, in advance rather than in an argument.

What it is

A fixed monthly amount with a written scope
The same engineers who built or audited the project
A backup and a restore path that has been tested, not assumed
A queue you are already in when something needs changing
A monthly report you can forward to whoever pays the invoice

What it is not

Not a rewrite — reworking the architecture or the design is a project, not maintenance
Not a new product — a new module, shop or integration is quoted as Business or Pro
Not 24/7 on-call — out-of-hours cover exists only where it is agreed separately in writing
Hours are not transferable between months — a quiet month does not become a bigger next one

The rhythm

Inside one month
on a plan.

Most of it happens without you noticing. The parts you do notice are the report, the invoice and the changes you asked for.

Start a care plan

Every day

Backups run, availability checks run, application errors are collected. Alerts arrive with us first, not with your customers.

Every week

A patch window. Dependency, core and security updates go to staging, get checked, and only then reach production — with a rollback prepared.

Whenever you need it

You send a change in one message. Small work comes out of the month's hours; anything larger gets an estimate and your approval before it starts.

Start of the next month

The written report and the invoice for the month ahead. Hours reset to the plan's allowance — they do not accumulate.

Before you subscribe

Straight answers.

Can I start a care plan on a site you did not build?

Can I cancel, and what happens to my project if I do?

What actually counts against the monthly hours?

Development, configuration and content work you request: a new page or field, a template change, a report, a small feature, a fix to something that was never in scope. Hosting, updates, backups, monitoring and the monthly report do not consume hours — they are the fee. Warranty work on a project still inside its warranty period does not consume hours either. Time is logged in 15-minute units and shown in the monthly report.

What happens if something breaks outside business hours?

Monitoring keeps running and the incident is recorded, so nothing is lost. Response times are counted in Estonian business hours on working days, which means a Saturday-night outage is picked up on the next working morning unless you have an out-of-hours arrangement. That arrangement is possible on the Priority plan, but it is agreed and priced separately — we would rather say that plainly than imply an on-call rota that does not exist.

Next step

Launch day is the start of the maintenance, not the end of the project.

Tell us what is running, where it is hosted and how much it would hurt if it stopped. We will answer with the plan that fits — including the answer that you do not need one yet.

Ask about a care plan See the build packages

E-mail: Blinovitservice1@inbox.eu
Phone: +372 5854 2311
Billing: Monthly in advance
Notice period: 30 days, in writing