top of page

Coverage

Support Coverage That Matches When Your Users Need You

Business hours, after-hours, 24/7, post-launch hypercare or a dedicated engineer. Choose the support coverage your application needs, with response times agreed in writing and no after-hours surcharge.

Codersarts support coverage defines when an engineer is available to respond to issues in your application, and how quickly. Options range from business hours in your timezone to after-hours critical response, full 24/7 cover, intensive hypercare after a launch, and a dedicated full-time support engineer.

Because our engineering team works across time zones, your nights and weekends are often a normal working day for us. That lets us offer after-hours and 24/7 coverage at standard rates, with a named on-call engineer, a named backup and a written definition of what counts as critical.

Support coverage decides when someone is actually there to fix your application. Codersarts offers business-hours, after-hours, 24/7, post-launch hypercare and dedicated engineer coverage, with response times agreed in writing. You choose the hours that match the risk, instead of paying for round-the-clock staff you do not need or hoping nothing breaks at night.




At a Glance


Item

Details

Coverage options

Business hours, after-hours critical, 24/7, hypercare, dedicated engineer

Business hours

Agreed in your timezone, Monday to Friday

Critical after-hours response

Acknowledged within 2 hours on Growth plans, 30 minutes on Dedicated Team

Hypercare

30 to 90 days of intensive support after a launch

Dedicated engineer

One full-time engineer on your application

Works with

Holidays

Coverage for critical incidents continues on public holidays where agreed



What Is Support Coverage?


Support coverage is the set of hours during which a support team is available to respond to issues, and the response time promised within those hours. It usually combines standard business hours with rules for nights, weekends and holidays, and states which priority levels are covered outside normal hours.


Coverage is different from support level. The level, such as L1, L2 or L3, describes how deep the support goes. Coverage describes when it is available. A small internal tool may need deep support but only during office hours, while a public-facing booking system may need fast critical response at midnight.


Pay for the hours your users actually need. Business hours for internal tools, round-the-clock cover for systems your customers depend on.


Why Coverage Matters


Most outages do not wait for office hours. Scheduled jobs run overnight, traffic peaks at weekends, and third-party services change without warning. Without defined coverage:


  • Critical failures overnight are only noticed when users complain the next morning

  • Developers are called on personal phones, with no agreed process or backup

  • Nobody knows whether a weekend outage counts as an emergency

  • Customers and partners lose confidence because response is unpredictable


Defined coverage replaces hope with a written promise: which issues get attention, how fast, and from whom.



Coverage Options


Business-Hours Coverage


Engineers are available Monday to Friday during business hours agreed in your timezone. Issues raised outside those hours are picked up at the start of the next business day, in priority order. This suits internal tools, early-stage products and applications where a few hours of delay has low business impact.


After-Hours Critical Coverage


Business-hours support plus an on-call engineer for critical incidents at night, at weekends and on holidays. Only issues that meet the agreed critical definition, such as a full outage or failed payments, trigger after-hours response. This is the most common choice for production applications with real users.


24/7 Coverage


An engineer is available around the clock, every day, for critical and high-priority issues. This suits public-facing services, transport and logistics systems, healthcare platforms, marketplaces and any system where downtime directly affects revenue or safety.


Hypercare After Launch


Hypercare is a short, intensive support period immediately after a new application, major release or migration goes live. Engineers watch the system closely, respond to issues faster than normal, and fix early problems before they become habits. It typically runs for 30 to 90 days, then moves to a standard support plan. For launch planning itself, see Go-Live.


Dedicated Support Engineer


One full-time engineer works on your application, learning it in depth and handling day-to-day issues, monitoring and small improvements. A backup engineer covers holidays and absences. This suits growing products that generate steady support work every day.



Coverage Options Compared


Option

Hours

Best for

Typical response for critical issues

Business hours

Weekdays, agreed in your timezone

Internal tools, early products

Next available business hours

After-hours critical

Business hours plus on-call for critical issues

Production apps with active users

2 hours

24/7

Every hour, every day

Public-facing and safety-critical systems

30 minutes

Hypercare

Extended attention for 30 to 90 days

New launches, migrations, major releases

1 hour

Dedicated engineer

Full-time on your application, with backup

Products with daily support needs

Agreed per engagement



How We Cover Nights and Weekends Without Overcharging


Many providers charge one and a half to two times their normal rate for after-hours work, because they pay local staff to stay on call. Our engineering team works across time zones, so a large part of your night is a normal working day for us. That lets us offer after-hours and 24/7 coverage at standard rates.


  • Follow-the-sun cover: engineers working their normal hours watch your system during your night

  • Named on-call engineer: a specific person is responsible, with a named backup

  • Same rate: after-hours work on Growth and Dedicated Team plans is billed at the standard hourly rate

  • Clear trigger: only issues that meet the agreed critical definition use after-hours response



What Counts as a Critical Incident


After-hours and 24/7 coverage only work when everyone agrees what an emergency is. At onboarding we write a critical incident definition for your application. Typical examples include:


  • The application or website does not load for most users

  • Users cannot log in, pay, book or complete the main task the product exists for

  • Data is being lost, corrupted or exposed

  • A core integration has stopped, such as payments, vehicle tracking or order sync

  • Scheduled jobs that the business depends on have failed, such as billing runs or nightly data exchange


Issues such as a broken report, a slow page or a cosmetic bug are handled in normal hours, even on 24/7 plans. This keeps after-hours response fast for the problems that truly need it.



Monitoring That Makes Coverage Work


Coverage is only as good as the alerts behind it. If nobody knows a system is down, nobody can respond. Every coverage option includes monitoring set up during onboarding:


  • Uptime checks on key pages and API endpoints

  • Error tracking for application exceptions and crashes

  • Alerts for failed or delayed scheduled jobs

  • Integration checks for third-party APIs and data feeds

  • Database health checks for connections, storage and slow queries


Alerts go to the on-call engineer and to the contacts you choose, so your team and ours see the same picture.



Common Coverage Mistakes to Avoid


  • Buying 24/7 cover for an internal tool that nobody uses at night

  • Relying on one developer's phone as the only after-hours plan

  • Leaving critical undefined, so every small issue becomes an emergency call

  • Skipping hypercare after a launch, when the risk of problems is highest

  • Promising response times to customers that your support provider has not agreed in writing



Response Versus Restoration


Coverage commitments are about how fast an engineer starts working, not a promise that every issue is fixed within a set time.


Term

Meaning

What we commit to

Acknowledgement

An engineer confirms the issue and starts work

A fixed time per priority and plan

Updates

Status messages to your team while work continues

Regular updates until the issue is resolved

Restoration

The system works again, fully or with a workaround

Continuous work until restored, with time recorded

Root cause

The underlying reason is found and fixed

A written note for every critical incident


Restoration time depends on the problem and on outside vendors such as cloud providers or platform suppliers, so it is tracked and reported rather than guaranteed.



How After-Hours Escalation Works


  1. The issue is raised through the agreed channel, such as your helpdesk, a monitoring alert, phone or a dedicated chat channel.

  2. The on-call engineer acknowledges within the agreed response time and confirms the priority.

  3. Work starts immediately and continues until the system is restored or a workaround is in place.

  4. Your contacts receive updates at agreed intervals, including any vendor escalations.

  5. A short incident note follows, describing what happened, what was done and what should change.



Pricing


Coverage is included in or added to a Support Levels plan.


Coverage option

How it is priced

Starting price

Business hours

Included in every plan

Included from USD 499 per month

After-hours critical

Included in Growth, add-on for Essential

Included from USD 1,299 per month, or USD 499 per month added to Essential

24/7

Included in Dedicated Team

From USD 4,499 per month

Hypercare

Fixed 30-day package, extendable

From USD 1,499 per 30 days

Dedicated support engineer

Monthly, full-time engineer with backup

USD 3,500 per month


After-hours critical incidents carry a 1-hour minimum charge per incident, billed from your plan hours first and then at USD 50 per hour.




How to Choose the Right Coverage


  • Ask what one hour of downtime costs. If the answer is lost revenue, safety risk or broken contracts, choose after-hours or 24/7 cover.

  • Check when your users are active. A global audience means someone is always using the system, even when your office is closed.

  • Look at when jobs run. Overnight data syncs, billing runs and reports often fail when nobody is watching.

  • Plan for launches separately. Hypercare costs less than a full year of 24/7 cover and protects the riskiest weeks.

  • Check your contracts. Public sector, enterprise and partner contracts often require written response times.



Coverage for Global and Multi-Timezone Products


When your users are spread across regions, there is no quiet period. Morning in one market is evening in another, and an outage at 3 AM in your office may hit your busiest customers. For these products we usually recommend:


  • After-hours critical cover as a minimum, so a full outage never waits until the next business day

  • Business hours set to your main market, with a second window for another region if needed

  • Planned maintenance windows chosen from real traffic data, not office hours

  • Status updates in one shared channel, so teams in every region see the same incident information



Holidays and Planned Maintenance


Critical coverage continues on public holidays where agreed in your plan. We publish a holiday calendar at onboarding so your team knows who is on call. Planned maintenance, such as upgrades and migrations, is scheduled with you in advance and carried out at low-traffic times in your timezone.



Who Uses Extended Coverage


  • Transport, fleet and logistics operators whose tracking and dispatch systems run day and night

  • SaaS products with customers across several time zones

  • Marketplaces and ecommerce stores with weekend and evening traffic peaks

  • Agencies and system integrators who promise response times to their own clients

  • Healthcare, education and public sector platforms where outages affect service delivery



Frequently Asked Questions


What is after-hours support?

After-hours support means an engineer responds to critical incidents outside normal business hours, including nights, weekends and holidays.

Yes. The Dedicated Team plan includes 24/7 coverage for critical incidents, with acknowledgement within 30 minutes.

No. After-hours work on Growth and Dedicated Team plans is billed at the standard rate, with a 1-hour minimum per critical incident.

Hypercare is an intensive support period of 30 to 90 days after a launch, major release or migration, with faster response and closer monitoring.

We guarantee acknowledgement times and continuous work on critical issues. Restoration time depends on the problem and outside vendors, so it is tracked and reported.

Business hours are agreed in your timezone at onboarding.

Yes. You can move between coverage options as your application and user base grow, with 30 days' notice.

Yes. A dedicated support engineer works full-time on your application for USD 3,500 per month, with a backup engineer for absences.



Choose Coverage That Matches Your Risk


Tell us when your users are active and what an outage costs, and we will recommend the right coverage and plan.



Explore all Support Services or see Maintenance for ongoing upkeep.





bottom of page