Support after headless migration — zero downtime
- 99.9%
- SLA
- 0
- Critical incidents
- 12+ mo
- Retainer
Service · Retainer & SLA
An hour of store downtime in peak season costs thousands of dollars. Most agencies write SLA clauses where the downtime penalty is "we sincerely apologize". Ours is calculated in dollars and credited to your next invoice automatically. No tickets to raise, no negotiation, no approval chain. We work with Next.js and 1С‑Bitrix projects.
Frontbox · core
SSR · ISR · edge cache · facets · synonyms · auth
What makes this different
Every minute beyond the SLA window is a percentage of the monthly retainer, deducted from the next invoice automatically. The formula is in the contract on page one.
No negotiation, no "we apologize"
Alerts on uptime, error rate, Core Web Vitals and queue depths go to Slack/Telegram before your users notice any issue.
We learn about incidents first
For growth-stage products — an optional bonus/penalty layer: if CR or NPS target is not hit by the quarter checkpoint, we refund a share of the monthly fee.
Bonus/penalty mechanics, optional
Documentation, runbooks and CI/CD pipelines are yours from day one. If you move to another team — no three-month ramp-up, no ransom for the codebase.
Switch teams without pain
Live projects
A retainer is a long-term relationship. Here is what it looks like in practice.
How we work
A retainer is a product with a predictable cycle. No "drop us a message".
If the project is already in production — we start with a technical audit: document the architecture, identify critical zones (infrastructure, queues, integrations, monitoring). Fixed price.
We agree on severity levels, response windows, escalation channels and the penalty formula. Everything is written into the contract. No changes after kickoff.
Incidents — handled per SLA. Improvements — from a prioritised backlog within monthly scope. The team knows what is in the current month, what is deferred and why.
Report on hours, incidents, releases and metrics. Based on it we update priorities and workload for the next month. No surprises in the invoice.
Why this is safe
A retainer is a product with contractual guarantees. Not a service on a whim.
No fine print. The penalty formula, response windows and severity levels are visible before signing — not buried in an appendix.
Full architecture documentation from the start of the retainer. Not after the contract ends, not on request, not for extra charge.
When you approach 80% of the hour bucket — we notify you in advance. Extra hours are added only after agreement. No surprise invoices.
Source code, CI/CD and Elasticsearch indexes are yours. If you switch teams — the new agency ramps up without a three-month onboarding.
We take over projects built by other teams: we start with a technical audit at a fixed cost. SLA commitments only after we know the codebase.
Comparison
A financial penalty written into the contract is something most agencies on the market simply do not offer.
Three support tiers
All three tiers include a financial penalty for missed SLA written into the contract. The difference is the response window, hours included and team dedication.
Basic Retainer
For projects with standard availability requirements. Monitoring and incident resolution during business hours.
10 hours per month included
Professional Retainer
For high-load e-commerce projects. Priority incident response, bi-weekly sync, Core Web Vitals monitoring.
20–40 hours per month included
Enterprise Retainer
For mission-critical projects. Round-the-clock coverage, dedicated team, weekly session with your CTO.
Custom hours, custom SLA
KPI-tied contract is available on Professional and Enterprise tiers: if the target metric (CR, NPS, LCP) is not reached — we refund a portion of the fee. Mechanics are defined in the contract before kickoff.
FAQ
Each tier has a defined response window. Every minute we miss it, a specific percentage of the monthly retainer is automatically deducted from the next invoice. The formula is in the contract on page one — no negotiation required.
An optional contract layer available on Professional and Enterprise tiers. We fix a target metric (CR, NPS, LCP or another). If the target is not reached by the agreed checkpoint — we refund a portion of the fee. The mechanics and refund percentage are defined in the contract before kickoff.
Yes. We start with an onboarding audit at a fixed price (typically 2 weeks): we document the architecture, identify risks, describe integrations and critical zones. After that we take on SLA commitments.
We notify you when you approach 80% of the bucket. Extra hours are added only after agreement — no surprise invoices at the end of the month.
Hours breakdown, closed incidents, released improvements, key metrics (Core Web Vitals, error rate, uptime) and priorities for the next month. One document — the full picture.
Via email, Telegram, Slack or a dedicated task board — whatever your team already uses. We adapt to your channels, not the other way around.
No ransom. All documentation, runbooks, CI/CD pipelines and source code are yours from day one of the retainer. A new team ramps up without a three-month onboarding.
Both. The retainer covers incidents, hotfixes, performance tasks and a portion of roadmap improvements within the monthly scope. The incident/development ratio is agreed at kickoff.
Tell us what needs to be covered — we will scope the SLA level and price. If the project was built by another team, we will start with an onboarding audit.
Documentation, runbooks and CI/CD are yours from day one — why that is the real insurance.
ServiceA store we build goes onto retainer support from day one.
ProductFast Next.js storefront — the stack we support under SLA.