Still working,
months later.
We handle the ongoing technical lifecycle of a website or app: security patches, OS updates, dependency upgrades, and bug fixes, plus the technical advice that comes with a product that keeps changing.
No separate support desk; the people who understand the product are the ones keeping it running.
Security and updates
Security patches, OS updates, and dependency upgrades so nothing quietly falls out of date.
↗Bug fixes
Practical fixes for the issues that come up once real users are on a live product.
↗Technical advisory
Advice as your product grows, your needs change, or new opportunities come up.
↗What we
look after.
Five ways we keep a product dependable long after launch.
Image 01
images/maintenance-security-updates.webp
Security and updates
Security patches, OS and platform updates, and dependency upgrades, applied regularly so nothing quietly falls out of date. New iOS and Android releases and changing store requirements are handled before they turn into a problem for your users.
- 01Security patches
- 02OS and platform updates
- 03Dependency upgrades
Image 02
images/maintenance-bug-fixes-monitoring.webp
Bug fixes and monitoring
Practical fixes for the issues that only show up once real people use a live product, backed by monitoring so problems are caught before they become outages. You get plain-language updates on what was found, what was fixed, and what comes next.
- 01Fixes for live-product issues
- 02Monitoring that catches problems early
- 03Plain-language reporting
Image 03
images/maintenance-health-checks.webp
Health checks and technical review
A structured look at where a product stands today: the code, the infrastructure, and anything overdue for attention. You get a clear picture of what is healthy, what carries risk, and what to do first, whether or not we built the product.
- 01Code and infrastructure review
- 02Risks and overdue work identified
- 03A prioritised list of what to fix first
Image 04
images/maintenance-technical-advisory.webp
Technical advisory
Technical advice for the decisions that come up as a product grows: evaluating a new feature, choosing between platforms or approaches, or spotting a risk before it turns expensive. You get a straight answer from the people who understand the product.
- 01Feature and platform decisions
- 02Architecture and approach review
- 03Risks flagged early
Image 05
images/maintenance-existing-projects.webp
Taking over existing products
If someone else built your website or app, we can step in. We learn the codebase, stabilise what needs attention, and take over maintenance and support, without asking you to start again from zero.
- 01Codebase review on takeover
- 02Stabilising what needs attention
- 03Ongoing maintenance and support
From health check
to hand-holding.
"Good work needs room to think."Coadex, on how we take on projects
Maintenance is a standing relationship, not a one-off ticket; the same team that knows the product is the one keeping it dependable.
- 01Health checkWe review the current state of the product: code, infrastructure, and anything overdue for attention.
- 02Ongoing careRegular patches, updates, and monitoring, so problems get caught before they become outages.
- 03AdvisoryWe're on hand for the technical decisions that come up as the product evolves.
- 04ReportingClear, plain-language updates on what's been done and what's coming up.
Two engagements,
kept private.
Maintenance and consultancy work is almost always under NDA. Here's the shape of it, without naming names.
Confidential Startup: Product Maintenance
This is a standing engagement, not a one-off build: regular security patches, monitoring, and code maintenance keep a startup's live product stable week to week, with technical review folded in as the product grows. The engagement is covered by an NDA, so we can't share specifics beyond that.
- 01Code maintenance
- 02Security support
- 03Ongoing technical consultancy
Private IT Consultancy: Technical Advisory
Rather than working inside one product, we sit across a client's portfolio of active projects — weighing in on technical decisions before they're built and flagging risks while they're still cheap to fix. Project details stay private at the client's request.
- 01Technical assessment
- 02Project and systems guidance
- 03Practical IT advice
Discretion is part of how this work has to run; most maintenance and consultancy clients are never named publicly, by design.
Before you
get in touch.
Security patches, OS and platform updates, dependency upgrades, and fixing bugs that come up once real users are using the product.
No, we regularly take over maintenance and support for websites and apps built by someone else.
Technical advice as your product or team changes: evaluating a new feature, a platform decision, or a risk before it becomes a problem.
Ongoing, typically: most maintenance and consultancy relationships run month to month rather than as a single project.
See everything else we doBack to Coadex ↗
Need something
kept running?
Tell us what needs ongoing care or advice, and we'll tell you honestly whether we're the right fit.