SLA operations

Binding
instead of best effort.

An SLA at feinwerk is not an uptime promise on a pricing page but an operations contract: defined response times, defined review cycles, defined responsibility.

The building blocks

Request an SLA

Availability monitoring

24/7 checks on endpoint, archiving and database, with alerting before your users notice anything.

System hardening

Hardening profiles for OS, network and Matomo itself. Minimal attack surface, documented target state.

Pentests

Regular penetration tests (internal and external) with a report and tracked remediation.

High-traffic operations

Load tests, load balancing and capacity planning for instances with millions of actions per day.

How it works

  1. 01

    Define the scope

    Which instances, which requirements, which response times? We agree on the framework together.

  2. 02

    Take stock

    We review and document the current state and set up monitoring.

  3. 03

    Operate by contract

    Review cycles, hardening and tests run to plan, with reports instead of gut feeling.

Frequently asked questions

Does the SLA also cover instances on our own infrastructure?

Yes. The SLA can be combined with a managed instance or agreed for operations on your infrastructure (on-premise).

How is an SLA set up?

We agree on scope, response times and review cycles together and put them in the contract. You receive an individual quote.

Individual quote · no list price

Tell us about your Matomo.

Briefly describe traffic, infrastructure and requirements. Within one business day you get an honest assessment and a quote.

What is it about?