Defined Response Times · Named Incident Owner · Monthly Restore Test · One Monthly Invoice
Ongoing Support for Your Existing Application, Every Month
Once your app is live, it needs steady care. Managed Run gives you ongoing support for your existing application: updates, fixes, deployments, monitoring, tested backups and defined response times, for a fixed monthly fee.
What Is Managed Run?
Managed Run is the Codersarts monthly retainer for ongoing support of an existing application. For a fixed monthly fee, one accountable team keeps your live app secure, updated, monitored and backed up, fixes defects, deploys changes and responds to incidents within defined response times, with a named incident-response owner. It works for an existing Node.js application and for most modern web stacks, whether your app was built in-house, by a freelancer or agency, or with AI coding tools.
One fixed monthly fee, one accountable team and defined response times for every incident.
Managed Run at a Glance
Question | Answer |
|---|---|
What it is | An application maintenance retainer with managed hosting operations |
Monthly fee | Fixed, starting at $1,000 per month |
Engineering hours | A fair-use allowance of hands-on hours, confirmed after code review |
Coverage | Business hours, Monday to Friday, in your agreed timezone |
Out-of-hours cover | Optional 24/7 critical-incident cover at $250 per month |
Critical acknowledgement | Within 30 minutes with 24/7 cover |
Backups | Encrypted offsite backups with a monthly restore test |
Contract | 3-month minimum, then month to month with 30 days' notice |
Why Live Applications Need Ongoing Support
Software does not stay healthy on its own. Even when nobody touches the code, the world around it changes:
Security vulnerabilities are discovered in libraries and runtimes every month
Runtime versions reach end of life. Each Node.js LTS release line receives security fixes for a limited period, after which it is no longer patched
Third-party APIs change. Payment providers, email services, AI models and CMS platforms update their interfaces and deprecate old ones
Data grows. Databases, logs and backups fill disks that were sized for launch
Small failures compound. A scheduled job that fails silently for a week can mean a week of missing emails or unpublished content
Ongoing support turns these risks into routine, scheduled work instead of emergencies.
What Managed Run Covers Every Month
Area | What we do |
|---|---|
Monitoring | Availability, application errors, memory, disk, failed jobs and backup failures, watched continuously |
Preventive maintenance | Security patches, dependency updates and runtime upgrades for the server and your application |
Corrective maintenance | Investigating and fixing defects in the existing application |
Adaptive maintenance | Keeping the app working as browsers, APIs, platforms and runtimes change |
Deployments | Releases through your approved deployment process, with rollback if a change misbehaves |
Integration troubleshooting | Authentication, database, email delivery, AI provider and CMS connections |
Backup and disaster recovery | Backup checks, a monthly restore test and duplicate-safe recovery |
Incident response | Severity-based response targets and a named incident-response owner |
Reporting | A monthly report on uptime, incidents, work done, hours used and recommended next steps |
New features and major changes are quoted separately, so your monthly fee stays predictable.
Ongoing Support for an Existing Node.js Application
Node.js services are among the most common applications we support. Typical Node.js work under Managed Run includes:
Process supervision so services restart automatically after a crash or reboot
Planned upgrades between Node.js LTS release lines, tested before they reach production
Dependency updates and vulnerability fixes in your npm packages
Memory leak and performance investigation when response times drift
Persistence checks for SQLite in WAL mode and other local databases
Email sending through Nodemailer or your provider's API, with sending limits enforced
The same approach applies to Cloudflare Workers and D1, Supabase, Next.js on Vercel, Firebase, Python services and WordPress-connected applications.
How We Take Over Your Application
If we did not deploy your application, Managed Run starts with a short, structured takeover so that support is effective from the first incident:
Access and handover. You share access through a secure, separately approved handoff. We sign an NDA if you need one.
Baseline review. We review the code, dependencies, runtime versions, hosting setup and existing backups, and record what we find.
Monitoring and alerting. We connect monitoring for availability, errors, resources, failed jobs and backups, and route alerts to the named owner.
Backup verification. We confirm backups exist, are encrypted and offsite, and prove one with a restore test.
Runbook. We document how the application is deployed, restarted and restored.
First monthly plan. We agree priorities for the first month, such as overdue security updates or a runtime upgrade.
If your app has not been deployed yet, the Go-Live Package covers these steps as part of the launch.
What Your Monthly Report Includes
Section | What it tells you |
|---|---|
Availability | Uptime for the month and any periods of downtime |
Incidents | Each incident with severity, response times, cause and fix |
Work completed | Updates, fixes and deployments, in plain language |
Hours used | Engineering hours against the included allowance |
Backups | Backup status and the result of the monthly restore test |
Hosting cost | That month's cloud bill, shown as an information line |
Recommendations | Risks we see coming and suggested next steps, with estimates |
A Fixed Fee With Fair-Use Engineering Hours
Managed Run is priced as a fixed monthly fee, not as a timesheet. The fee pays for continuous monitoring, backups, restore testing and a team ready to respond, plus a fair-use allowance of hands-on engineering hours. We confirm the included hours with you after reviewing your code.
Month | Engineering work | What you pay |
|---|---|---|
Quiet month | A few hours of updates and checks | The fixed monthly fee |
Normal month | Within the included hours | The fixed monthly fee |
Busy month | 4 hours beyond the included hours | The fixed fee plus 4 hours at $50, approved by you in advance |
Unused hours do not carry over to the next month
We notify you when 80% of the included hours have been used
Incidents caused by our own changes are fixed at no charge and do not count against your hours
If the same issue causes repeated incidents, we propose a permanent fix with an estimate
Support Coverage and Response Times
Support runs Monday to Friday during business hours agreed in your timezone, excluding public holidays. Non-critical requests received outside business hours are handled on the next working day. Critical incidents outside business hours are covered when you add 24/7 critical-incident cover.
Severity | What it means | Acknowledgement | Investigation started | Recovery target |
|---|---|---|---|---|
Critical | Service down, data at risk, security breach or risk of duplicate emails or articles | 30 minutes (24/7 with cover) | 1 hour | 4 hours |
High | A major function or recurring job is failing, or a backup has failed | 2 business hours | 4 business hours | 1 business day |
Normal | A minor defect, a non-urgent change or a question | 1 business day | 2 business days | Next scheduled update |
What the Targets Mean
Acknowledgement: we confirm we have received the issue and are working on it
Investigation started: an engineer is actively working on the cause
Recovery: the service is working again, by a fix or a safe workaround; after a critical incident, a short root-cause note follows within 3 business days
Targets do not apply to outages of your cloud provider, platform vendors, AI provider or email provider, but we still respond, keep you updated and coordinate with them.
24/7 Critical-Incident Cover
If your application runs scheduled jobs, sends emails or publishes content outside office hours, a night-time outage should not wait until the next working day. For $250 per month, a named engineer stays on standby at night, at weekends and on public holidays to respond to critical incidents within 30 minutes.
Time spent on critical incidents comes first from your included hours
Once those are used, out-of-hours critical work is charged at $75 per hour
Without this cover, out-of-hours incidents are handled on a best-effort basis, with no guaranteed response time
Backups You Can Actually Restore
A backup that has never been restored is not a recovery plan.
Managed Run includes backup and disaster recovery with clear targets:
Item | Commitment |
|---|---|
Backup storage | Encrypted, offsite and separate from the main server |
Retention | Daily backups for 30 days, weekly for 12 weeks, monthly for 6 months |
Recovery point objective (RPO) | As low as 5 minutes for application databases with continuous replication; up to 24 hours for daily exports |
Recovery time objective (RTO) | Full service restored within 2 hours |
Restore testing | Monthly, to an isolated environment, with results shared with you |
Who restores | Codersarts, following the written recovery runbook |
RPO is the maximum amount of data you could lose in an incident, measured in time. RTO is how long it takes to bring the service back.
Duplicate-Safe Recovery
For apps that send emails or publish content, delivery records and uncertain-delivery holds are restored exactly as they were. After any restore, sending and publishing stay on hold until every record is checked, and nothing marked as uncertain is resent automatically.
Planned Maintenance and Downtime
Routine updates are applied in an agreed weekly maintenance window outside your peak hours
Expected downtime on a single-server setup is under 15 minutes per update
At least 48 hours' notice is given for any update expected to interrupt service
Urgent security fixes may be applied sooner, with notice as early as possible
Planned maintenance is part of Managed Run and is not charged separately
One Contract, One Invoice, Your Account
Hosting management and maintenance sit under one contract
Your cloud account stays in your company's name and is billed to you directly at actual cost
Codersarts sends one consolidated monthly invoice for support, on-call cover and any approved extra work
Each invoice shows your monthly hosting cost as an information line, so you see total spend in one place
You own all code, data, backups and documentation, and can remove our delegated access at any time
Managed Run Compared With Other Support Models
Model | How it is billed | Best for | Limitation |
|---|---|---|---|
Ad-hoc hourly support | Per hour, when needed | Occasional small fixes | No monitoring, no guaranteed response times |
Time and materials team | Monthly invoice for hours worked | Ongoing feature development | Costs vary month to month |
Managed Run retainer | Fixed monthly fee with fair-use hours | Keeping a live app secure, monitored and recoverable | A 3-month minimum commitment |
What Is Not Included
New features or major changes, which we quote separately on request
Third-party fees for cloud hosting, AI providers, email providers or platforms you already use
Your WordPress website itself and administration of your business email accounts
Switching on live email, AI generation or publishing without your written approval
Managed Run Pricing
Managed Run
Starting at $1,000 per month, business hours
For live applications that need one accountable team for maintenance, monitoring, backups and incident response.
Continuous monitoring with defined response times
Security and dependency updates, defect fixes and deployments
Monthly restore test and duplicate-safe recovery
Named incident-response owner and monthly report
Fair-use engineering hours, confirmed after code review
Add-ons and Extra Work
24/7 critical-incident cover: $250 per month
Additional engineering in business hours: $50 per hour, with your approval
Out-of-hours critical work beyond included hours: $75 per hour
Managed Run starts after your application is live and accepted, with a 3-month minimum and then month to month. If your app is not live yet, start with the Go-Live Package. For an overview of both, see Managed App Operations.
Frequently Asked Questions
What does ongoing support for an existing application include?
Monitoring, security and dependency updates, defect fixes, deployments, integration troubleshooting, tested backups and incident response, delivered by one team for a fixed monthly fee.
Do I pay the full fee in a quiet month?
Yes. The fee covers monitoring, backups, restore testing and a team ready to respond, not only hands-on hours.
What happens if I need more than the included hours?
Extra work in business hours is charged at $50 per hour, only with your approval. We notify you when 80% of the included hours are used.
Is 24/7 support included?
Managed Run covers business hours. 24/7 critical-incident cover is an optional add-on at $250 per month.
What is the difference between RPO and RTO?
RPO is the maximum data you could lose, measured in time. RTO is how long it takes to restore the service.
Can you support an app built with AI coding tools?
Yes. We maintain apps built by in-house teams, freelancers, agencies and AI coding tools such as Claude Code, Cursor, Lovable and Bolt.
Who owns the hosting account?
You do. It is in your company's name, billed to you at actual cost, and we manage it with delegated access you can remove at any time.
Can I cancel?
Yes. After the 3-month minimum, Managed Run continues month to month with 30 days' written notice to cancel.
Keep Your App Secure, Updated and Running
Tell us what your application runs on and how it is hosted today. We will recommend the right support level and confirm your monthly fee in writing.