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.
- Free initial consultation
- Every value negotiable
- Also for your infrastructure and cloud
- ~300M hits per month in operation
- 8+ years running Matomo
- since 2009 Matomo experience
Matomo projects for clients including
When Matomo is business-critical.
Outages are noticed late
Tracking or reports fail, and nobody notices until numbers are missing.
Security updates wait
Patches for Matomo, plugins and servers keep getting postponed.
Nobody feels responsible
Between marketing, IT and agencies, operations fall through the cracks.
Audit asks questions
Internal audit, information security or your DPO want to know how Matomo is run and checked.
Archiving breaks off
Reports are missing for days, and nobody sees it in time.
Peaks during campaigns
Large campaigns or deadlines push Matomo to its limits.
The baseline: your starting point.
This is what an SLA with us looks like before we tailor it to you. Every value is negotiable, up or down, and ends up in your contract.
| Baseline | Can be agreed | |
|---|---|---|
| Monitoring | around the clock: tracking, UI, archiving, database | your own checks, alerts straight to your team |
| Response to critical incidents | within 4 hours, business days 8 am to 6 pm | shorter times, standby around the clock |
| Response to other incidents | next business day | as agreed |
| Security updates | critical ones within 2 business days of release | your approval process, a staging instance |
| Feature updates | as agreed, tested beforehand | fixed maintenance windows |
| Backups | daily, kept for 30 days, restore tested quarterly | longer retention, your own storage |
| System hardening | hardening profile at the start, reviewed yearly | to your information security requirements |
| Pentests | external once a year, with a report and tracked actions | more often, internal as well, scope to your requirements |
| Capacity | capacity review every quarter | load tests before campaigns and deadlines |
| Reports | monthly operations report | metrics of your choice, regular reviews |
| Contact person | one named person, by e-mail | your ticket system, regular video calls |
The building blocks.
An SLA is made of these building blocks. Which ones you need and how far they go, we agree together.
Request an SLAAvailability 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.
Four steps to your SLA.
-
01
Consultation
Which instances, which requirements? Free and without obligation.
-
02
Assessment
We check the current state and set up monitoring.
-
03
Contract
We adapt the baseline, the values go into the contract.
-
04
Operations by contract
Monitoring, updates, review cycles and reports as planned.
Without an SLA or with one?
| Without SLA | With a feinwerk SLA | |
|---|---|---|
| Incidents are noticed | when numbers go missing | by monitoring around the clock |
| Response to incidents | when someone has time | within agreed times |
| Security updates | some time | within agreed deadlines |
| Pentests and hardening | rarely or never | regularly, with a report |
| Evidence for audit and DPO | gathered by hand | monthly operations report |
| Ownership | unclear | one named contact person |
Who is behind it
Peter Boehlke, Matomo specialist since 2009.
Host with feinwerk and you talk to the same person who set up your instance.
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, in your own data center (on-premise) as well as in your cloud on AWS, Azure or Google Cloud.
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.
Are the baseline values fixed?
No. The baseline is our proposal to start from. We adapt response times, review cycles, pentest scope and reports to your requirements and put them in the contract.
Is there round-the-clock standby?
Yes, as an option. In the baseline we respond on business days from 8 am to 6 pm. Standby at night and at weekends can be agreed when your operations need it.
What does an SLA cost?
That depends on scope, response times and review cycles. After the free initial consultation you receive an individual quote.
Related articles
Hosting from €99 per month · quote to fit
Tell us about your Matomo.
Briefly describe traffic, infrastructure and requirements. Within one business day you get an honest assessment and a quote.
- info@feinwerk.io
- Munich · data centers in Germany