Maintenance & support

Updates, security, backups and developer hours every month.

Maintenance is an agreement that someone watches your site or system and answers when something breaks: updates, security, backups, monitoring and a set amount of developer time each month for changes. We do not sell hosting — we look after what runs on it.

Who it's for

No developer of your own

Companies where nobody knows what happens under the hood.

The agency disappeared

Teams whose previous partner stopped answering after launch.

Downtime costs money

Online stores where an hour of downtime is lost orders.

What's included

  • Platform, module and dependency updates with a check before publishing
  • Security monitoring, vulnerability fixes, SSL and access rules
  • Backups with a tested restore — not only creation
  • Accessibility and speed monitoring with alerts
  • A set number of developer hours a month for content and feature changes
  • Monthly report: what was done, what changed, what to plan
  • Response time by plan, with critical cases — first

Technology and approach

We do not sell hosting and we do not manage domains. We help you choose and move, but you receive the invoice directly from the provider — no markup and no lock-in to us.

  • Basic — from €150/month, 2 h
  • Business — from €400/month, 6 h
  • E-commerce — from €750/month
  • No hosting
  • No domain management

Frequently asked questions

Do you maintain a site someone else built?

Yes, after a short technical audit. It shows what state the project is in and which plan fits.

What happens if we want to stop?

Access and documentation are yours. No penalty and no holding you hostage.

Does this include SEO?

No, that is a separate piece of work. Maintenance keeps the page working — not growing it.

Is hosting included?

No. We deliberately do not sell it — you pay the provider directly, with no markup from us.

What usually comes with this

One team, so the next step does not start from zero.

Visi vienpadsmit pakalpojumi

Three steps to a proposal

No long intro. Usually one conversation is enough to understand scope and timing.

  1. Tell us the goal

    Enquiries, sales, speed or automation. A short note is enough.

  2. A short consult

    Goal, audience and what you already have. Usually one conversation.

  3. Proposal

    Scope, timing and the next step — before we write code.