Services/Maintenance
Application Maintenance and Support
Fixes, updates and small features after the release. For products we built and for products we take over.
What support covers
Eight kinds of work. Which of them your product needs depends on its age, its load and how often it changes. We propose the set, and you approve it before the work starts.
Debugging
Something has stopped working, and users are already writing about it. We reproduce the defect first, then find its cause in the code and fix it. After that we check that the fix has not broken anything else. You also get a short note on what happened and what was changed.Root cause analysis and continuous improvement
A fix removes the symptom, but the same failure can come back. Therefore, after a serious incident we look for the reason behind it: a weak place in the architecture, a missing test or a manual step in the release. Then we propose a change that removes the reason, and you decide whether to do it. As a result, the same kind of failure does not repeat.In-depth code audit
Before we take a product on support, we read its code. As a result, we know what the codebase can support, where the risks are and what should be fixed first. It is especially important when the product was built by another team. Then we propose a support plan based on the audit, and you approve it.Performance optimization
A product slows down when its data and its audience grow. We measure where the time is lost before users start to complain: heavy database queries, slow screens, overloaded servers. Then we fix the places that give the largest effect first. As a result, the product stays fast without a large rewrite.Feature updates and modernization
A product that nobody touches gets old. Operating systems change, libraries lose support, and the stores change their rules. We update the frameworks and libraries, and also add the small features your business needs, such as a new report or a new payment method. Larger changes, however, become a separate project with its own estimate.Migration
Sometimes the product has to move: to another cloud, to a new version of the framework or to a new database. We plan the move in steps, so the product keeps working while it goes on. Before the switch we check the new environment with real data. If something goes wrong, we go back to the previous version.SLA management
A service level agreement says how fast we react and how fast we fix. The terms depend on the product: an online store needs an answer at night, while an internal tool can wait until the morning. Therefore we agree on the reaction time separately for failures that stop the product and for minor defects. These terms are written into the contract, so you know what to expect.System health and capacity planning
We watch the servers and the app, so we learn about a failure before your users write to you. The same data also shows how the load grows from month to month. Based on it, we tell you in advance when the current servers will stop being enough. As a result, you plan the cost of growth instead of paying for an emergency.How support is organised
So that you always know who answers and what is being done.
Need a team that keeps the product running?Tell us what you have. We will look at the code and then propose how to support it.
Discuss supportWe turned to the 24Gen team when the project was in a critical stage. Deadlines were looming, and the product was far from ready. From the very beginning, we were impressed by the team's professionalism and accountability. In a short time, they assembled an MVP, set up scrum processes, and introduced an AI-based solution for moderation. Despite tight deadlines, all key modules were delivered on time and with solid quality. We are very satisfied with the collaboration and confidently recommend 24Gen as a reliable partner for large-scale projects.
Watch the video
Engagement models
Three ways to work with us. We help you pick one on the first call.
Our engineers work as an extension of your team, under your lead or ours.
We agree on the scope, the price and the deadline before the work starts.
You pay for the hours worked and change priorities whenever you need.
From our blog
All articlesCan you support a product another team built?
Yes. We start with a code audit to see what the codebase can support, then propose a plan for what to keep and what to rebuild, and start once you approve it.
How fast do you react to a failure?
The reaction time is written into the contract, separately for failures that stop the product and for minor defects.
How is support paid for?
Either a monthly amount for a set number of hours, or the hours actually worked. We suggest the one that fits how often your product changes.
What if we need a big new feature?
Then it becomes a separate project with its own estimate, done by the same team.
Do you update apps for new iOS and Android versions?
Yes. We check the app against each new version before it reaches your users and release an update when one is needed.
How do you estimate the cost?
After the first call we break the task into parts and send you a written estimate. When the scope is clear, we fix the price and the deadline. When it is open or likely to change, we work on time and materials or as a dedicated team.
Who owns the code? Do you sign an NDA?
You do. The code and all rights to it pass to you in full. We sign an NDA whenever you need one.
Tell us about your product
Describe the task in a few lines. We will get back to you to set up a call.
info@24gen.space



