Services

Maintenance and support for websites and apps

A monthly agreement for the site, app or system you already have. Updates, fixes and small changes, done by people who know how it works.

Website and app maintenance is the regular work that keeps software secure and working after launch: updates, fixes, checks and small changes. Vyorde offers it as a monthly agreement for small and mid-size companies that have a site, app or internal system in use and no developer of their own looking after it.

What you get

What's included

  • A first review of the code, hosting and accounts, with written notes on what we found
  • A written agreement on what is covered and how fast we respond to each kind of problem
  • Security and dependency updates, tested before they go live
  • Bug fixes, with a note on the cause
  • Small changes such as text edits, new pages and form fields
  • Regular checks of uptime, backups and error logs
  • A short monthly note on what changed and what we would do next

What's not included

  • New features or a redesign. Those are quoted separately as a Websites & Apps or Custom Software project.
  • Moving to new servers or rebuilding how releases work. That is DevOps & Cloud.
  • Answering your customers. We look after the software, and your team looks after the people using it.

You'll probably like this if

  • Your site or app works, and nobody is looking after it.
  • The developer who built it has moved on, and you don't know what's running.
  • You have a list of small changes that never feel big enough to start a project.

How it goes

  1. We look at what you have.

    Code, hosting, accounts and anything that's already broken. If we built it, this part is quick.

  2. We agree what's covered.

    Which work is included, how you report problems and how fast we respond to each kind. In writing.

  3. We do the routine work.

    Updates, checks and fixes on a regular schedule, plus the requests you send.

  4. We report every month.

    What changed, what we spotted and anything that needs a bigger decision.

Every project follows the same five steps. See the full process.

What changes the price

  • How many sites, apps or systems are covered
  • How much change work you expect each month
  • How quickly you need us to respond
  • Whether we built it or someone else did

Tell us what you need and you get a quote in writing before anything starts.

Before you start

  • A list of the sites, apps and systems you want covered
  • Access to the code, hosting and domain, or the name of whoever has it
  • Any documentation or notes the previous developer left
  • The problems and small changes already waiting
  • How quickly a serious problem has to be answered for your business

You don't need all of it for the first call.

Questions about website maintenance

How fast do you respond?

New enquiries get a reply within 24 hours. Response times under a support agreement are set in the contract, depending on how serious each kind of problem is.

Can you support something you didn't build?

Usually, yes. We look at it first and tell you honestly what state it's in and what that means.

What if we need something bigger?

We quote it separately, so the monthly agreement stays predictable.

How long does it take to get started?

If we built it, we can start straight away. If someone else did, we first review the code, hosting and accounts, which is similar in size to our Technical Audit of 1 to 2 weeks. We don't take over anything blind, because the first emergency is a bad time to learn how a system works.

What do you need from us to start?

Access to the code repository, hosting, domain and any third-party services the site depends on, all through accounts you control. Whatever documentation exists, even if it is out of date. The name of the person who reports problems and approves changes. And a list of what is already broken, so we start with it.

Are we tied to you once you maintain it?

No. Everything stays on accounts in your name, the code stays in a repository you can see, and we keep the documentation current as part of the work. If you hire a developer or move to another company, they get the notes and the access, and we remove ours.

What does a normal month look like?

Updates are applied to a test version, checked, then released. Uptime, backups and error logs are looked at on a schedule, not after a complaint. Requests you send are done in order of urgency. At the end of the month you get a short note on what changed, what we noticed and what we would do next.

More questions are answered on the FAQ page.

Want to start smaller?

Try the Technical Audit package first. For a website or web app that feels slow, shaky or invisible, when you want to know why before paying anyone to fix it. Typical timeline: 1 to 2 weeks. The exact dates are in your quote.

See all three packages

From Insights

Last updated

Tell us what you have running.

Book a call

Or write to us from the contact page.