manage
Keep the product current after the first release.
Applications decay when dependencies age, content structures change, and small defects wait for a project that never starts. Maintenance is the disciplined version of that follow-through.
Myrran looks after the code, hosting configuration, and release process for products we built or that we have assessed and agreed to take on. The agreement lists what is included.
Who it is for
Teams with a live website, web app, or mobile app and no dedicated person to ship safe updates.
Defect fixes
Reproducible issues in the agreed product, prioritised with you.
Dependency and platform updates
Framework, library, and runtime updates tested against the important paths.
Store and browser compatibility
Mobile OS and browser changes that break a known flow are addressed when they are in scope.
Small improvements
Copy, fields, and minor workflow tweaks inside a monthly allowance if you want one.
Release notes
A short record of what changed, so the next person is not guessing.
Limits we will say out loud
- A new module, a redesign, or a new integration is a project, not maintenance.
- We need repository access, hosting access, and a staging path. Without those, we will not guess at production.
- We do not guarantee that a third-party platform will remain compatible.
Questions
After an assessment. If the codebase is unsafe or undocumented, the first step may be stabilisation rather than a monthly retainer.
Related
Web application development
Logged-in software for operations, customers, and teams: portals, dashboards, booking, and internal tools.
Mobile app development
iOS and Android applications with a clear first release, backend integration, and a plan for updates.
Managed digital operations
Ongoing care for the websites, apps, accounts, and integrations your business depends on.