Custom-Coded Website Maintenance
Your site was built specifically for your business — and the developer who built it has moved on. We document what exists, then keep it running: verified changes, tested backups and someone accountable when something breaks.
Discovery comes first. We confirm the stack, the access and the risks before recommending any maintenance scope.
If we cannot support your stack responsibly, we will tell you that instead of learning on your live site.
Site down, broken or compromised? Request Emergency Support.
1,000+ represents websites served cumulatively, not current actively maintained sites. 2 hours means initial response on business days, not a fix time or 24/7 service.
What Custom Website Maintenance Can Include
A custom site has no plugin directory and no update button, so maintenance starts with understanding rather than with a schedule. These are the pieces that follow.
1. Discovery and Documentation
We record the stack, dependencies, versions, integrations, deployment path and access in writing. That document becomes the baseline for every change afterwards — and it is usually the most useful thing a custom site owner gains.
2. Dependency and Version Care
Framework, library and runtime versions are tracked and updated deliberately, with a tested copy of the site between the change and your visitors.
3. Backup Checks and Recovery
Code, database, uploaded files and configuration all matter on a custom build — a database-only backup can be useless. We check what is actually captured and verify that a restore works.
Website Backup Services →4. Monitoring and Early Warning
Uptime, error rates and the business-critical paths specific to your build — a login, a calculator, an upload, an order flow. Monitoring surfaces change earlier; it does not mean someone watches every minute.
Website Monitoring Services →5. Security Maintenance
Patch review for the components you depend on, access review, and escalation when something looks wrong. No service can promise a site will never be attacked — on custom code, keeping the entry points small matters most.
Website Security Services →6. Routine Approved Changes
Small changes to existing pages, templates, content or configuration, within the included hours. New features, integrations and rebuilds are quoted as their own scope.
Website Update Services →Why a Custom Site Cannot Be Maintained Like a CMS Site
The usual maintenance model assumes a platform with a plugin ecosystem, a documented upgrade path and a community. A custom build has none of those, which changes both the risks and the work.
No Plugin Ecosystem
Nothing can be swapped in. Every fix is written against your code, so the person doing it has to understand the system first.
No Documented Upgrade Path
Framework and runtime upgrades have to be planned and tested. There is no one-click route, and guessing is how working sites break.
Undocumented by Default
Custom builds are often delivered without written documentation. Rediscovering how a site works is the first cost of any takeover.
Single-Developer Dependency
When one person holds the knowledge, their unavailability becomes a business risk. Documenting the system is how that risk is reduced.
Version Drift and Legacy Code
Old runtimes keep working until the host changes something. Bundled changes arrive without warning, which is why environment changes are tracked.
Thin Test Environments
Many custom sites have no staging setup, so every change is made on production. Building a safe place to test is often the highest-value first step.
Inherited or Undocumented Sites
This is the most common reason custom sites reach us: a developer, agency or past employee is no longer reachable. We document before we change anything.
Know What Custom Maintenance Covers
Boundaries matter more than usual here, because “just change one thing” on a custom system can reach further than anyone expects.
Usually Part of Ongoing Maintenance
- Documentation of the stack and environment
- Dependency and version review
- Backup checks and recovery verification
- Monitoring of uptime, errors and key paths
- Security and access review
- Routine approved changes within included hours
- Maintenance records and monthly reporting
Usually a Separate Scope
- New features or new application logic
- Rebuilding or modernising the platform
- New third-party or API integrations
- Full redesign
- Malware removal and incident recovery
- Server, cloud or infrastructure rebuilds
- Data migration between systems
- Hosting, licence and third-party fees
Important: a maintenance plan is not an unlimited development retainer. The scope is confirmed in writing after discovery, and anything outside it is quoted before work begins.
Included Work Hours per Month
The monthly fee covers defined maintenance within the included hours below. Custom systems vary widely, so the final scope follows the discovery pass. Work beyond the included hours is billed at the agreed overage rate or handled by upgrading the plan.
Custom Care
Up to 3 hours of included maintenance per month.
Growth
Up to 6 hours of included maintenance per month.
Priority
Up to 12 hours of included maintenance per month.
Custom Website Maintenance Plan Levels
Three tiers cover different levels of complexity and support need. Because custom systems differ more than CMS platforms, the tier is confirmed after discovery rather than assumed from the page count.
Custom Care
from $799/mo
- Documented stack and environment baseline
- Dependency and version review
- Backup checks and recovery verification
- Monitoring review
- Up to 3 included hours / month
Growth
$1,499/mo
- Everything in Custom Care
- Staging environment maintained for changes
- Key business-path monitoring
- More manual review and support priority
- Up to 6 included hours / month
Priority
$2,999/mo
- Everything in Growth
- Deeper security and access review
- Higher service capacity
- Proactive improvement work
- Up to 12 included hours / month
None of these plan names implies 24/7 support or unlimited development. The final scope follows a discovery pass; work beyond included hours is billed at the agreed overage rate or handled by upgrading the plan.
Why Contract-Accountable Maintenance
Some providers lead with “no contract, cancel anytime.” That convenience usually comes with low accountability: when something goes wrong, there is no agreed standard for who responds, how fast, and to what quality.
We use a clear initial term, monthly renewal, and a defined notice period. That structure is what lets us commit to an SLA, response times, and a party you can hold to account. For a site that matters to your business, accountability is part of the service — not a restriction.
What You Actually Pay For: Real Engineering Hours, Not a Task Queue
Some plans advertise “unlimited small changes (up to 30 minutes each).” That is a capped task queue, not real capacity — and it limits the depth of work that gets done.
Plans advertised as “unlimited”
- “Unlimited” small changes, each capped at about 30 minutes
- Updates often pushed straight to the live site
- Little stated SLA or accountability
- Hard to tell what is truly included
Our custom plans
- Defined monthly engineering hours — 3 hours (Custom Care), 6 hours (Growth), 12 hours (Priority)
- Changes staged and verified before production
- SLA-backed response and a contract you can reference
- Transparent overage at $99/hour, or upgrade the plan
You always know what is covered. Work beyond the included hours is billed transparently or handled by moving up a plan — no illusion of “unlimited.”
How Your Included Hours Are Counted
No guesswork and no hidden math. Your included hours cover hands-on engineering time only. Automated updates, backups, monitoring, and scans never draw down your allowance — they run in the background as part of the service.
A credit is a billing unit for the accountable result we deliver — verified, senior-reviewed, and covered by our SLA — not a stopwatch reading. AI lets us complete routine work far faster, and that efficiency is exactly what keeps our rates competitive. It never removes the human judgment or the responsibility behind a change.
| Counts toward your hours | Does not count |
|---|---|
| Content and image updates | Automated updates, backups, monitoring, and scans |
| Code and template tweaks | Routine consultation and planning discussions |
| Troubleshooting and incident handling | Rework caused by our own error |
| Migration, recovery, and optimization | New scope (quoted and approved before we start) |
Standard task credits
Common requests have a predefined credit, so there is nothing to negotiate after the fact.
| Common task | Standard credit | Notes |
|---|---|---|
| Content or image update (up to 5 minor edits) | 0.5 h | Batch these for better value |
| Style or copy tweak | 0.25 h | No structural change |
| Page structure change (add, remove, or reorder modules) | 0.75 h | Excludes new page build |
| New product or service page (existing template) | 0.75 h | New design quoted separately |
| Form or error fix | 1.0 h | Single-point issue |
| Plugin or theme conflict troubleshooting | 0.75 h | Diagnosis and fix included |
| Performance check and basic optimization | 1.0 h | Excludes dedicated performance work |
| Single-page or partial data restore | 1.0 h | Full-site recovery is a separate scope |
| DNS, email, or SSL configuration change | 0.5–0.75 h | Includes rollback and verification |
| Data export or report output | 0.5 h | Standard format |
| Security incident response (triage, isolation, and stop-loss) | 2.0 h (cap) | First-response containment only; malware removal and full cleanup are a separate scope, quoted first |
| Third-party integration change | from 1.5 h | Assessed first; complex work goes to a scope of work |
| AI content drafting with human review | from 0.5 h | Human review included |
| AI-readiness and structured-data upkeep | from 0.75 h | Visibility and structured data |
Security incidents are handled up to a 2.0 h standard credit; larger recovery work is quoted before we proceed. Credits are tracked in 15-minute increments. As a courtesy, minor changes that take only a few minutes (roughly 10–15 minutes, up to twice a month) are absorbed at no charge — you are not billed a full credit for a one-line fix. Work beyond your included hours is billed at $99/hour or handled by moving up a plan. Each month you receive a simple usage ledger — tasks, credits used, and your remaining balance — alongside your maintenance report.
Silent Failures Are What We Catch
A site that goes down is obvious. The failures that cost the most are the quiet ones. A contact form stops sending. A checkout breaks for one payment method. Pages quietly drop out of search. Speed slips a little every week. Nothing crashes, so nothing shouts — the leads just stop.
That is the failure mode we watch for. Alongside uptime, we monitor the signals that go silent:
Form submissions
We test that your forms still reach their destination, so a broken contact or quote form does not sit unnoticed for weeks.
Checkout and orders
For stores, we watch the order path and flag signs that a payment step has stopped completing.
Search indexing
We check that your pages stay indexed, and that nothing is accidentally blocked from search after a change.
Speed and Core Web Vitals
We track real performance over time and flag gradual decline before it starts costing you conversions.
And You Hear About It Every Month
A maintenance plan should not be a silent invoice. Every month you receive a short report: what we updated and checked, what monitoring caught, what we fixed, and how much of your included hours were used. If nothing went wrong, the report still tells you what was verified — so “nothing happened” shows up as visible work, not silence.
You Own Your Site. Always.
Your domain, your hosting account, and your code belong to you. A maintenance provider should never be the only one holding the keys.
Your assets stay in your name
Domain, hosting, and site files remain yours and under your control. We work with your access — we do not take ownership of it.
A clean handover if you leave
If you move on, the agreement sets out how access, files, and credentials are returned. We do not hold your domain, and we do not charge a release fee.
This is written into our agreement, not just promised on a page.
How We Deliver: Staging → Senior Review → Production
We do not blind-push updates to your live site. Routine changes move through staging, a senior review, then production — with SLA-backed response times. This is our standard, not a premium add-on.
Staging first
Updates and changes are verified in a staging environment before they reach visitors.
Senior review
Changes are checked by experienced engineers, not just an automated script.
SLA-backed
Response commitments are defined in the agreement, so expectations are clear.
AI-Assisted, Human-Accountable
We use AI tools to compress routine work, which helps us keep a competitive rate. But accountability for critical and complex changes stays with a human engineer. AI raises the floor — it does not remove responsibility.
Our Maintenance Model Fits You If…
A good fit
- Your website is tied to revenue — ecommerce, lead generation, or membership
- You run more than one platform and want one accountable vendor
- You have been affected by a broken site or a provider that disappeared
- You want a defined SLA and a party you can hold to account
- You need changes verified in staging, not pushed blindly to production
Not the best fit
- Your main priority is the lowest possible price and you accept the risk
- You run a small single-page brochure site with little traffic
- You prefer to manage updates and changes yourself
- You need “unlimited everything” with no scope boundary
- You are looking for a one-time project (that is a separate scoped engagement)
- You want service with no contract or commitment at all
Run more than one platform? We can cover your other sites under one contract, billed per site with a multi-site discount — not one price for every platform.
Our Commitments to You
Annual prepay flexibility
If you prepay annually and cancel within 30 days, we refund the unused difference. (Per our stated terms.)
Setup fee protection
If a setup or onboarding fee applies and you cancel before work starts, it is fully refunded within 7 days. (Per our stated terms.)
Is Custom Website Maintenance Right for Your Site?
Good Fit
- A custom or bespoke application that runs your business
- A site whose original developer is no longer available
- Heavily modified builds that no longer match their CMS
- Systems with integrations nobody currently maintains
- Teams with no in-house developer for the platform
Assessment Required
- No documentation and no access inventory
- Legacy runtimes well past support
- Multiple servers or a complex deployment pipeline
- Active malware or a current breach
- Unknown ownership of domain, hosting or source code
Not the Right Starting Point
- A new application built from scratch
- A full rebuild or replatforming project
- Staff augmentation — you need a developer, not a maintenance plan
- Urgent incident cleanup
- Design-only work
Looking for something else? Redesign · Migration · Malware Removal · Security Audit · Emergency Support
Continuity for Systems That Have None
Maizhe Network has worked in website development and maintenance since 2010 and has served more than 1,000 websites, including custom and legacy systems that outlasted the teams that built them.
Documented Before Changed
Nothing is modified until the stack, access and risks are written down. That protects the site and gives the next person a starting point.
More Than One Person Knows Your System
Knowledge is recorded rather than held by one individual, so an absence is not an outage.
Honest Capability Limits
If we cannot support a stack responsibly, we say so and point you to the kind of developer who can. Taking on work we should not is how a working site gets damaged.
Clear Scope Before Work Starts
What is included, what is quoted separately and what is not possible — stated before anything is touched.
Developed-market engineering, contract-accountable, at a competitive rate.
About Maizhe NetworkWhat Affects Custom Website Maintenance Pricing?
On a custom system the price follows the complexity that has to be understood, not the number of pages. The main factors are:
- Stack, language and framework versions
- How much documentation already exists
- Number of integrations and third-party APIs
- Whether a staging environment can be created
- Server, cloud or deployment complexity
- Traffic and business criticality
- Security and compliance requirements
- Support scope, response needs and included hours
A small custom site with documentation may fit the entry tier. An undocumented multi-service application will need discovery first. Tiers and included hours are listed above; this page does not invent price ranges.
Custom-Coded Website Maintenance FAQ
What counts as a custom-coded website?
A site that is not built on a mainstream content management system: custom PHP, Node, .NET or Python applications, bespoke admin panels, headless front ends, or a site so heavily modified that the original platform is no longer the thing running it. The defining feature is that the code is unique to you, so no plugin directory or update button can look after it.
The developer who built our site has disappeared. Can you take it over?
Usually, yes — this is one of the most common reasons a custom site reaches us. We start with a discovery pass: what the stack is, where it is hosted, what access exists, and what documentation survives. Only after that do we recommend a maintenance scope. Your domain, hosting account and files stay in your name throughout.
Do you maintain every language and framework?
No, and we will say so rather than take the work and learn on your live site. After the discovery pass we either confirm we can support the stack responsibly or tell you plainly that we cannot, and point you toward the type of developer who can.
There is no documentation. Is that a problem?
It changes the work, not the decision. An undocumented site is documented first: dependencies, versions, integrations, deployment path and access. That becomes the baseline everything else is measured against, and it is usually the single most valuable thing a custom site owner can buy.
Can you update custom code safely?
Yes, where a staging environment can be created. Custom code has no automatic update path, so changes are made deliberately, tested against a copy of the site, and verified before production. Where no staging environment exists, setting one up is often the first recommendation.
What happens if the site is hacked or goes down?
Use the emergency path. We assess first. Initial response — triage, isolation and stopping the damage — is handled within the included hours of your plan; malware removal, cleanup and recovery are a separate scope, quoted before we proceed. On custom systems, identifying the entry point often matters more than on a standard CMS.
How much does custom website maintenance cost?
Standard tiers are Custom Care from $799/mo, Growth $1,499/mo and Priority $2,999/mo. Complex custom systems are priced after a discovery pass, because the honest variable is how much undocumented surface area exists — not the page count.
Can you also handle hosting and infrastructure?
We can review and advise on the environment, and we work with your existing host or cloud account. We do not resell hosting. Server management stays with your provider unless a specific infrastructure change is agreed as its own scope.
Can you modernise a legacy system, or only maintain it?
Both, but they are different engagements. Maintenance keeps the current system healthy. Rebuilding or modernising it is a project with its own plan, timeline and price — and it is often better done in stages than all at once.
Why are your rates higher than a freelancer?
Because the risk profile is different. A custom application has no community to fall back on, so the value is in documented continuity: a defined scope, verified changes, an SLA, and a second person who knows your system. If the site is a small static build, a freelancer may genuinely be the better choice — we say so when that is the case.
Start With Knowing What You Have
Send the site URL and anything you know about how it was built. If documentation is missing, that is the normal starting point — not a problem.
Need urgent help? Request Emergency Support.