Skip to content

Maintenance and support

Keep your software healthy, patched and improving after launch.

Dependency updates, monitoring, bug fixing and steady feature work for products we built and for software inherited from other teams.

What happens to software nobody looks after

  • Dependencies age

    Unpatched libraries and runtimes accumulate known vulnerabilities and make later upgrades larger.

  • Problems are found by customers

    Without monitoring, errors and slowdowns surface through support tickets.

  • Knowledge walks out

    When the original developers move on, the system becomes a black box.

  • Small fixes wait in a queue

    Without a retained team, minor changes are delayed until they become urgent.

What maintenance covers

  • Updates and patching

    Frameworks, libraries, runtimes and operating-system packages kept current on a schedule.

  • Monitoring and alerting

    Error tracking, uptime and performance checks with defined responses.

  • Bug fixing

    Reproduction, fix, test and release for defects reported by users or found by monitoring.

  • Performance and cost tuning

    Slow queries, heavy pages and oversized infrastructure reviewed and improved.

  • Backups and recovery

    Backup configuration and restore tests, so recovery is a practised procedure.

  • Roadmap development

    A steady allocation of time for new features and refactoring.

Ways to arrange support

As-neededRetained
SuitsStable products with rare changesProducts in active use or growth
Response approachScheduled when requestedAgreed service expectations
Proactive workNot includedUpdates, monitoring and reviews
PlanningPer requestRegular roadmap time

Operational practices we apply

  • Scheduled dependency review

    Known vulnerabilities are checked and updates applied on a regular cycle.

  • Backups with tested restores

    Backups are only counted once a restore has been rehearsed.

  • Access reviews and secret rotation

    Who can reach production, and which keys are active, is reviewed periodically.

  • Change history

    Every release is tracked, reviewed and reversible.

What we support

Languages
  • TypeScript
  • JavaScript
  • Node.js
Frameworks
  • React
  • Next.js
  • NestJS
  • React Native
Data and hosting
  • PostgreSQL
  • Redis
  • Nginx
  • Managed cloud services

Taking over software built by someone else

  1. Audit

    We review code, infrastructure, access, dependencies and documentation, and report what we find.

  2. Stabilise

    Backups, monitoring and critical fixes are put in place before any new work.

  3. Document

    Missing architecture notes, run books and set-up instructions are written.

  4. Maintain and improve

    Regular updates and prioritised improvements begin under an agreed arrangement.

Inherited software you do not fully trust?

Give us read access or a description. We will tell you what condition it is in and what we would do first.

Questions about maintenance

Still have questions? Tell us about your project and we will answer in one business day.

Book a call
Can you maintain software you did not build?

Usually yes, after an audit. If the code or infrastructure is in poor shape, we report the risks and agree what to fix first. In rare cases we recommend a rebuild, and we show the reasoning.

What does an arrangement cost?

It depends on system size, risk and how much change you expect. After an audit we propose a fixed monthly scope, with additional work estimated separately.

Do you offer emergency support?

Response expectations are agreed in the support terms for each product. We do not promise round-the-clock cover unless it has been explicitly scoped and staffed.

Can you modernise an old system gradually?

Yes. Replacing a legacy system piece by piece is often safer than a full rewrite. We find seams, move one capability at a time, and keep the system running throughout.

Tell us about the software you need maintained

What does it do, who built it, and what worries you? Access details can wait until after we speak.

We use your details only to answer this inquiry.