Home · About · Services · Industries · Projects · Products · Process · Blog · FAQ · Contact
Application maintenance and support that keeps live apps healthy. Application maintenance and support for live web apps: bug fixes, security patches, framework upgrades and takeovers of inherited Angular, React or Python code.
Application maintenance and support is the ongoing work a live web application needs: fixing bugs, applying security patches, keeping frameworks and dependencies on supported versions, and making the small changes your users ask for. We also take over codebases that another agency or a departed developer left behind. We read the code, get it building and deploying again, write down how it works, and then keep it running. You get one accountable team and a record of every change.
Why teams call us after launch. The original developers are gone The agency or freelancer who built the app has moved on, there is no documentation, and nobody is sure how to deploy it safely.
Dependencies are years out of date The app runs on an Angular, Node.js, Python or Django version that no longer receives security fixes, and every audit report gets longer.
Small fixes take weeks Simple bugs sit in a backlog because each change risks breaking something else and there are no tests to catch it.
Problems are reported by users Errors, slow pages and failed jobs are only noticed when a customer or staff member complains.
What maintenance and support covers. Codebase takeover We get access to the repository, servers and accounts, get a clean build running locally and on staging, and write a short report on the state of the code before changing anything.
Bug fixing Reported issues are logged, reproduced on staging, fixed with a test where practical, and released with a note of what changed and why.
Security patching We track advisories for your dependencies with tools such as npm audit, pip-audit and Dependabot, and apply fixes on a regular cycle, sooner for serious ones.
Framework and runtime upgrades Planned upgrades of Angular, React, Next.js, Django, Node.js and Python before their support windows close, one major version at a time.
Error and uptime monitoring Application error tracking, uptime checks and log review, so failures are seen by us before they turn into support tickets.
Small enhancements Form changes, new reports, extra fields and integration tweaks handled within the retainer hours instead of as separate projects.
Release process If deploys are manual, we move them to a CI/CD pipeline with a staging step and a documented rollback.
Documentation A README that explains setup, environments, deploys and the parts of the code that surprise people, kept up to date in your repository.
Engagement options Takeover and stabilisation A fixed-scope project for inherited or neglected apps that need to be understood and made safe before anything else.
Code, hosting and access review Reproducible build and staging environment Critical security patches and fixes Written state-of-the-code report Maintenance retainer A monthly arrangement where we keep a live application patched, monitored and fixed, with a set number of hours for changes.
Bug fixes and small enhancements Dependency and security updates Monitoring and incident response Coverage hours and response times agreed upfront Upgrade project A fixed-scope piece of work to move an app off unsupported framework or runtime versions without a rewrite.
Upgrade path and risk assessment Version-by-version upgrade on staging Regression testing of key journeys Production release with rollback plan How it works Access and inventory We collect repository, hosting, domain, database and third-party service access, and list everything the app depends on.
Assess We build and run the app, check versions against their support dates, review error logs and send a prioritised list of risks.
Stabilise Urgent security issues and bugs are fixed first, deploys are made repeatable, and backups are confirmed with a test restore.
Maintain Regular patching, monitoring and fixes continue on the retainer, with a monthly summary of what was done.
Why Infigini We maintain our own products TechLogHub and EasySiteControl are platforms we build and run ourselves, so upgrades, patches and incidents are part of our normal week.
Comfortable with older code We have worked on Angular 8 applications and added Angular 13 features on top of a running AngularJS base, so legacy code does not put us off.
Full stack, one team Frontend, backend, database and hosting problems are fixed by the same engineers, without hand-offs between vendors.
You own everything Code, configuration, credentials and documentation stay in your accounts. If you move maintenance in-house, nothing needs to be migrated away from us.
Technologies: Angular, AngularJS, React, Next.js, Django, FastAPI, Node.js, PostgreSQL, MongoDB, Redis, GitHub Actions, Docker
Related projects Consumer Web Application — An Angular 13 application for end users, built on top of an existing AngularJS base.
University ERP Suite — Five Angular applications covering students, alumni, admissions leads, finance and core ERP.
Self-Service Deployment Server — A shared server that lets anyone in the organisation deploy applications through CI/CD to multiple domains and subdomains.
Campus ERP — An ERP system in daily use by students and employees.
Frequently asked questions What does application maintenance and support include? It covers the work a live application needs to stay usable and safe: fixing bugs, applying security patches, upgrading frameworks and runtimes before support ends, monitoring errors and uptime, keeping backups working, and making small changes users ask for. The exact scope, hours and response times are written into the retainer before work starts.
Can you take over an application another company built? Yes. We start with access to the code, hosting and accounts, get the app building and deploying from a clean environment, and write a short report on its condition. Only then do we start changing things, so you know what you are dealing with before committing to a longer arrangement. If the app cannot be made safe without a larger rebuild, the report says so.
What if there is no documentation or the source code is incomplete? We work from what is running. We compare the deployed version with the repository, recover configuration from the servers, and document setup and deploys as we go. If parts of the source are genuinely missing, we tell you plainly what can be rebuilt, what can be worked around and what it would take.
How is application maintenance priced? Retainers are a monthly fee based on the size and age of the application, how many systems it touches, the hours of change work included and the response times you need. Takeovers and upgrade projects are quoted at a fixed price after an initial assessment. Send us details of your app and we will reply within one business day with next steps towards an estimate.
How quickly do you respond to issues? Response times and coverage hours are agreed in the retainer and depend on how critical the application is to your business. We separate urgent production problems from normal requests so that a broken checkout or login is not queued behind a layout change.
Do we have to upgrade an old framework version? Not always immediately, but versions that no longer get security fixes are a growing risk. Each Angular major version is supported for 18 months, Node.js LTS releases get security fixes for roughly 30 months, and Django LTS releases for about three years. We check your versions against their published support dates and plan upgrades one major version at a time, usually without a rewrite.
Which technologies can you maintain? Web applications built with Angular (including AngularJS), React and Next.js on the frontend, and Python (Django, FastAPI) or Node.js on the backend, with PostgreSQL, MongoDB or Redis. We also handle the hosting side on AWS, Azure or your own Linux servers. If your stack is outside this, we will tell you on the first call.
Can we bring maintenance in-house later? Yes. Code, configuration and documentation are kept in your repositories and accounts throughout, so there is nothing to migrate away from us. Handover is a set of working sessions with your developers covering deploys, monitoring, backups and open issues. We can also stay on in a reduced role for upgrades or escalations if that suits you.
Further reading Application support retainer: what it covers and how it works
Taking over an inherited codebase: the first 30 days, week by week
Modernising a legacy system without a big-bang rewrite
What software maintenance after launch really involves
Backups that actually restore: Postgres and MongoDB
Moving Angular 8 applications forward without a rewrite
Infigini IT Services · 11 Kanwali Road, Dehradun 248001, India · info@infigini.com · +91 95684 87789