Skip to content
The Vector logoThe Vector

Maintenance & Support

The unglamorous work that decides whether software is still useful in three years.

Overview

The short version

Software does not stay still. Dependencies get security advisories, browsers change, APIs deprecate, traffic patterns shift and the business asks for something the original design never anticipated. Maintenance is how a system keeps earning its cost.

Technologies we use here

DockerGitHub ActionsNginxLinuxPostgreSQLMySQLAWSCloudflareSentry

Chosen per project against your team's existing skills, your hosting constraints and long-term maintenance cost — not house preference.

Scope

What we build

Security patching

Dependency monitoring, vulnerability triage and scheduled updates with a tested rollback path.

Performance optimisation

Query tuning, caching, asset and rendering work backed by profiling rather than guesswork.

Bug fixing

Triaged by severity against an agreed response window, with a root-cause note rather than a silent patch.

Infrastructure support

Backups, monitoring, uptime alerting, certificate renewal and cost review.

Continuous improvement

A reserved monthly block for small features and refinements so the product keeps moving.

Method

How we approach it

The same three commitments apply to every engagement, whatever the technology involved.

  • Written response times

    Severity levels and response windows are agreed in the contract, so 'urgent' means the same thing to both of us.

  • Inherited systems welcome

    We take on software other teams built. It starts with an audit and a documented risk list before we touch anything.

  • Monthly transparency

    A short report covering what changed, what broke, what was patched and what we recommend next. No mystery invoices.

FAQ

Questions

Straight answers, including the ones that occasionally lose us work.

Yes, after an audit. If the codebase is in a state where maintenance would be unsafe or misleadingly expensive, we will say so and give you the options.

A monthly retainer covering an agreed number of hours, with clear rates for anything beyond it. Unused hours and rollover terms are stated in the agreement.

Three months, so there is enough time to stabilise the system and be useful. After that it continues month to month.

Tell us what you are trying to build.

Send the problem, the constraint or the half-formed idea. You will get a straight answer on whether we are the right team for it, and what it would take.