Corrective: fixing defects
Defects found in use get fixed, tested and released, whoever on your side spotted them.
Our software maintenance services start with a code audit before any contract. Code another team wrote also gets written findings and a handover.


Definition
Support and maintenance keep a product people use stable and safe to change, with fixes, updates and small improvements worked in order of priority. We take on products we built and products another team built, so a product keeps its support when the people who wrote it have moved on.
Software support is the reactive half of the work. Your team raises a bug, a feature that stopped working or a question about how something behaves, and we work it. Maintenance is the planned half, the upkeep that means fewer of those requests arrive. Skip the maintenance and the product gets louder every quarter.
Support is also the last stage of our own projects. We offer support that follows a project delivery, so a product goes from discovery to the build to support with one company. If you are weighing support against a managed team or extra engineers, compare support and the other engagement models.


Fit check
Support starts once real users rely on the product. From then on, a careless release costs more than a slow one.
Both work. Inherited code gets read before anyone changes it, however urgent the first request looks.
Our engineers work with Java, .NET, Node.js and Python on the backend, React, Angular and Vue.js on the frontend, and Flutter and React Native for mobile, along with the frameworks and tools that usually come with them.
If you have a tech lead and a backlog growing faster than your team can clear it, add engineers who work in your process. Support works through requests as they come and won't take on your roadmap.
If new features keep coming and priorities move every few weeks, support will feel like a queue. You want a managed team for ongoing product work, which we run while you set the priorities and own the backlog.
Every change breaks something else? Then upkeep alone won't fix it. Legacy modernization comes first, and support can follow once the system is safe to change.


Code built elsewhere
Before we sign a support contract, our code audit reviews the application and its code. For code another team built, it adds written findings and a handover. If the findings show the code needs more than upkeep, modernizing the system is the first job.
STEP 1
We read the code, its dependencies and the deploy and release setup, and note where tests and documentation are missing.
STEP 2
You get the findings in writing, with our recommendation on what to fix first.
STEP 3
A short handover follows: access, environments, runbooks, and a walkthrough from the previous team where one is available.
STEP 4
From then on we support the product the same way as code we built, request by request.
Retainer scope
Maintenance work is usually sorted into four types: corrective, adaptive, perfective and preventive. A support retainer with us can cover all four. Preventive work is the type that gets skipped when nobody plans it in.
Monitoring of the live product is part of the retainer and runs in support hours, so a problem can show up on our side before a user reports it on yours. Infrastructure and CI/CD work as a project of its own belongs to our DevOps services.
Defects found in use get fixed, tested and released, whoever on your side spotted them.
When a browser version, an operating system or a third-party API changes under the product, we change the product to match.
When a library, framework or runtime version reaches end of support, we move the product to a supported one.
A clearer form, one more field in a report: small changes to features your users already have.
Small refactoring where code is hard to change, and tests added where they are missing, so the next change in that area costs less to make.
How we work
Requests come in through Jira or Slack and are closed in the same place, so the history of every change stays in your tools. Each one goes through the same five steps, and none of them skips review because it looked small.
STEP 1
Your team raises a bug, a change or a question in Jira or Slack, with what we need to reproduce it.
STEP 2
Each request gets a priority, so a broken checkout is worked before a typo on a settings page.
STEP 3
An engineer makes and tests the change, and a second engineer reviews it before it is merged.
STEP 4
We prepare and test the release, your team approves it, and it ships through your own release process.
STEP 5
We close the request where it was raised, and you get a regular summary of the work done.
Tell us what the product does, who built it, what keeps breaking and which part your users can't do without.
Who and when


For a US client we can arrange 4+ hours of daily overlap with the West Coast, more with the East. UK and EU clients get business-hours support from our engineers across the full CET/CEST day.
80%+ of our engineers are senior-level or above, with 7 years' average experience. The figures cover every engineer we staff, testers and support engineers included.
A client handed us its call center operator console after work had started, and we developed and supported it for more than 5 years. We have also provided L2 support for a fintech product.
Every engineer we staff has passed three checks: a technical skills assessment, a soft-skills evaluation and an analysis of their job history. The first tests the stack they claim.
Engineers work through named accounts you issue, with only the access their role needs, and all their access is removed when they leave the engagement.
From a client's CTO
You can trust Octalance not just to build complex, original work, but also support the developed product and ensure it thrives after release.
CTO, UK-based fintech startup
Terms of support
We keep a live product stable and work through fixes, updates and small improvements by priority.
Usually a retainer plus hours or tickets by priority, agreed per client.
Our engineers join your team and work in your process and tools. You manage them; we source, vet and contract them.
Hourly rate per engineer by role and seniority, invoiced monthly.
An agreed team capacity that we manage. We coordinate delivery and handle the team's make-up. You set the priorities and own the backlog.
Per-engineer rates, or a fixed monthly fee for the agreed capacity.
"Missing tests are the first thing I'd fix on inherited code. Until they exist, every change is a guess about what else it breaks."

Dzmitry Kuchynski, Chief Operating Officer, Octalance
FAQ
Then the audit starts from what is in the repository and the deploy and release setup, so it doesn't wait on anyone's memory. If someone from the previous team can still be reached, their walkthrough becomes part of the handover. Either way, you get the findings in writing before we change anything, with what we would tackle first.
Hours or tickets are tracked in your own tools, with a regular summary of what they went on, and any overage is agreed with you. The price type is usually a retainer plus hours or tickets by priority. Rates and the retainer's size are agreed per client, so we quote once we know your product.
Yes. Start from how much of your working day needs to overlap with ours, and we agree the US cover with you on that basis. Without such an agreement, support runs in CET/CEST business hours.
An urgent issue goes to the front of the queue, since requests are worked by priority, and response times are set in your support contract. If the product can't wait for the next CET/CEST working day, out-of-hours on-call can be agreed per client. We don't run shifts, so that cover exists only where it has been agreed.
The code usually lives in your repositories, sometimes in ours. Systems we control are hosted in the EU. Code and data in your own systems stay wherever you keep them. We work under GDPR as an EU-registered company, and where support means handling your data, a data processing agreement is part of the engagement.
Only the tools and accounts you approve, and nothing goes to a tool you haven't allowed. AI-written code is reviewed by another AI agent first and then by an engineer before it is merged, and our testers test it like any other code.
Notice, minimum term and scale-down are agreed per client and set in your support contract. When support ends, transition-out is a routine step, whether the product moves to your own team or to another vendor, and our engineers' access is removed as part of it.