Software maintenance keeps a live product secure, fast and working after launch, through updates, fixes, monitoring and small improvements. Our engineers have worked on Autobuffy for around 28,000 hours and on Coach Catalyst across a 30-month roadmap.
Reviewed by Azmat Rana, CEO & Founder · Updated
Software that nobody looks after slows down, breaks with each operating system or package update, and turns into a security risk.
Core capability
Framework, package and server updates applied and tested on a regular schedule, before old versions stop getting security fixes.
Problems reported by users or caught by monitoring, fixed in order of impact, with each fix tested before release.
Error tracking, uptime checks and alerts for failed jobs, routed to an engineer who can act on them.
Slow pages and queries found and fixed as data grows, through indexing, caching and background jobs.
The changes that keep a product useful between big releases, such as a new report, an integration or a better form.
Support starts with learning the system, then settles into a steady routine.
Onboard
We get access, read the code and hosting, and set up monitoring if it is missing.
Agree
We agree what gets checked, how often updates happen and how quickly each kind of issue gets a response.
Run
Updates, fixes and small features ship on a regular cycle, each one tested on staging first.
Report
You see what changed, what was fixed and what is coming next, so the system never becomes a black box.
Monitoring, deployment and data tools we use to keep products healthy.
Sentry
Docker
GitHub
PostgreSQL
Redis
ElasticsearchMost products need some upkeep after launch. These are the signs it has fallen behind.
Each skipped framework or package update makes the next one bigger. Nextflag’s slowdown came from falling behind on them.
When the original developers leave, small changes start taking weeks. A team that knows the system fixes that.
If you hear about problems from users, monitoring is missing or nobody is watching it.
Queries that were fine at launch get slow at scale. Autobuffy’s part search needed Elasticsearch and new indexes to stay fast.
Outdated packages are a common way in for attackers. Regular updates close those gaps.
If a new report or field needs a full project, an ongoing team can deliver it in the normal cycle instead.
Long-running products our engineers have worked on for years.
Projects like this one usually involve these as well.
Further reading: Upgrading a live store from Angular 8 to 13 in 20 days
Hire full-time developers in the stacks we use for this work.
What teams ask before handing over a live product.
Security and version updates, bug fixes, monitoring, performance work and small improvements to a live product, on an agreed routine rather than as one-off projects.
Yes. We start by reading the code, getting it running and adding monitoring, then take over updates and fixes once we know how it behaves.
We agree response times with you at the start, and urgent production issues come first. The routine depends on how critical the system is to your business.
Yes. Mobile apps need regular updates for new iOS and Android versions and store rules, so we keep them building and releasing on current versions.
Yes. Most support work mixes upkeep with small improvements. Larger features are scoped separately so they do not crowd out the essential work.
You do. Everything we build for you, including the source code and the intellectual property in it, belongs to you.
Tell us what you are running and what worries you about it, and we will suggest a support routine.
Hire Ruby on Rails developers
Hire React and Next.js developers
Hire Node.js and NestJS developers