01
A retainer plus hours.
The fixed monthly fee covers our standby: monitoring, the SLA and on-call cover. On top of that you get developer hours, which you can use for small features or which go on bug fixes.
[RESPONSE P1] from 30 min
[MONITORING] 24/7
[TIERS] 3 + custom
[STACK] JS · React · Next · Node
S
JavaScript app maintenance:
three tiers [
with a clear SLA.]
JavaScript applications need regular care. npm dependencies get security fixes all the time, and every Node.js upgrade can break something. So our maintenance contract states a response time, a monthly bucket of hours and a written scope, rather than a promise to get back to you after an outage.
→ Sustain · Maintenance · Development · Security patches
I
How we price it.
Each tier's price is a monthly retainer plus a bucket of hours. These are the four rules we agree before the contract is signed.
02
Response times in hours.
A critical outage (P1) has a contractual response time, measured in hours (or minutes on Enterprise) rather than business days. If we miss it, the hours go back into your bucket.
03
Unused hours expire.
You are paying for our time and availability in a given month. Up to 20% of unused hours roll over to the next month, so they don't pile up indefinitely.
04
P1 means a real outage.
The SLA defines a critical bug in writing: users can't log in, the basket doesn't work, payments fail. A typo in a heading is not a P1, however bad it looks.
II
Three tiers for different levels of risk.
We look after everything from stable side projects to online shops turning over €25M a year. If none of the tiers fits, we'll put together a custom agreement.
/ 01
Reactive
Basic / Standard
Stable projects that rarely change, where a short outage isn't a disaster.
€340–680
net / month
5–10
hours / month
[P1 outage]4–8 working hours
[P2 request]within 48 h
[work hours]Mon–Fri · 9–17
- Basic uptime monitoring
- Weekly backup
- Small fixes
- Estimates for new features
- Rate outside the bucket: €45/h
Most popular
/ 02
Active
Business / Growth
Applications under active development that earn revenue and need regular changes.
€1,000–1,800
net / month
20–30
hours / month
[P1 outage]2–3 h · 8–20
[P2 request]within 24 h
[work hours]Mon–Fri + weekend P1
- Extended monitoring (Sentry)
- Monthly npm updates
- Snyk · Dependabot · security patches
- Daily backups
- Named coordinator and a status update every two weeks
- Rate outside the bucket: €40/h
24/7
/ 03
Critical
Enterprise / Dedicated
High-traffic online shops and B2B SaaS, where every minute of downtime costs revenue.
from €2,700
net / month
40+
hours / month
[P1 outage]30–60 min · 24/7
[P2 request]within 12 h
[work hours]24/7/365
- Infrastructure as Code (Terraform)
- APM: New Relic / Datadog
- Database and API performance
- Vulnerabilities patched immediately
- Weekly reports
- Optional: dedicated developer at 0.5 FTE
- Rate outside the bucket: €35/h
III
Tiers side by side.
Every difference between the tiers in one table.
/ 01Reactive
/ 02Active
/ 03Critical
Monthly price
€340–680
€1,000–1,800
from €2,700
Hours in bucket
5–10 h
20–30 h
40+ h
Rate outside the bucket
€45 / h
€40 / h
€35 / h
P1 response
4–8 h
2–3 h
30–60 min
P2 response
48 h
24 h
12 h
Work hours
Mon–Fri 9–17
+ weekend P1
24/7/365
Monitoring
uptime
uptime+Sentry
uptime+APM
Backup
weekly
daily
daily+replica
npm updates
as needed
monthly
every two weeks
Snyk scan
—
yes
yes + alerts
Reports
—
every two weeks
weekly
Named coordinator
—
yes
yes
Hour rollover
max 20%
max 20%
max 20%
IV
What counts as a critical outage.
The most common SLA misunderstanding: someone reports a typo as a P1 and a developer gets woken at 3am. That's why both lists are written into the contract.
immediateP1: serious outage
- →The application is down (HTTP 5xx, blank screen).
- →Users can't log in.
- →The basket or checkout doesn't work.
- →The payment provider returns errors.
- →A data leak or critical vulnerability in production.
- →ERP or PIM sync has failed and is blocking sales.
queueP2/P3: important, but can wait
- ·A typo, a misaligned logo, the wrong colour.
- ·A single user reports odd behaviour.
- ·Pages load a little slower than usual.
- ·A minor bug in the admin panel.
- ·A feature request or small change.
- ·A CMS content change.
V
What uses up hours.
A short overview so your first invoice holds no surprises.
Development and new features
Yes: implementation, code review and deployment, billed in 15-minute blocks.
Estimates and analysis
Yes. Scoping a new feature is work, so it comes out of the bucket. It usually takes 30–60 minutes.
Bug fixing
All bugs (P1, P2, P3) come out of the bucket. If we can see an incident will use more than the bucket, we tell you early.
Package updates
Active and Critical tiers only. We do them on a regular schedule, outside the bucket.
Monitoring and alerts
These don't use hours; they are covered by the retainer.
Reports
These don't use hours. On Active and Critical they are covered by the retainer.
→
None of the tiers fit?
We also agree custom SLAs, for example with a dedicated developer at 0.5 or 1.0 FTE, a signed SLA with financial penalties for missed response times, or an audit and retainer in one contract. Thirty minutes is usually enough to talk it through.
Discuss a custom SLA