Maintenance, so the app you launched still works next year.
Security patches, OS compatibility, dependency updates, uptime monitoring, and a real engineer who answers. Monthly retainers with a stated response time — not a support ticket into a void.
Software decays even when nobody touches it. iOS and Android ship breaking changes every year, dependencies accumulate vulnerabilities, certificates expire, and payment providers deprecate the API version you integrated against. An unmaintained app does not stay still — it slowly stops working.
We maintain applications whether or not we built them. That includes inheriting codebases from teams who have moved on, which is more common than anyone admits.
What a retainer covers
Security patching — dependency scanning with prioritised updates, and emergency response for critical vulnerabilities.
OS and platform compatibility — annual iOS and Android releases tested and fixed before your users find the breakage.
Store compliance — App Store and Play Store policy changes handled, including privacy declarations and target SDK deadlines.
Uptime and error monitoring — alerting on downtime, error spikes, and slow responses, with someone on the other end.
Bug fixes within an agreed response time by severity.
Backup verification — restores actually tested, not just scheduled.
Performance review — a quarterly look at what has grown slower and why.
Small enhancements — an included monthly allowance of development hours for the changes that are too small to be projects.
Retainer tiers
Essential
Standard
Growth
Monitoring and alerting
Yes
Yes
Yes
Security and dependency patching
Monthly
Monthly
Continuous
Critical bug response
Next business day
Same business day
Priority, same day
OS and store compliance updates
Included
Included
Included
Included enhancement hours
None
A monthly allowance
A larger monthly allowance
Reporting
Quarterly
Monthly
Monthly + review call
Best for
Stable internal tools
Live customer-facing apps
Products still evolving
Exact hours and response windows are set in your agreement, sized to the application. We quote after looking at the codebase rather than guessing from a tier name.
Taking over an app someone else built
1
Code and infrastructure audit
We read the codebase, review the architecture and dependencies, and check what is deployed where. You get a written assessment.
2
Risk report
What is urgent, what is merely untidy, and what will break at the next OS release — with honest severity, including 'this is fine'.
3
Access and continuity
Repository, store accounts, cloud, domains, and certificates transferred and documented so no single person is a bottleneck.
4
Stabilise
Fix the urgent items, add monitoring, and get backups verified before anything else.
5
Ongoing retainer
Predictable monthly maintenance with reporting you can show a board.
Key facts
Applications
Web, iOS, Android, Flutter, React Native, and backend services
Codebases
Ours or someone else's — audit first either way
Response times
Defined by severity in your agreement, in writing
Contract
Monthly rolling with 30 days' notice — no annual lock-in
Included after any Qalmax build
30 days of bug fixes at no charge
Reporting
What was patched, what broke, what is coming
Technology stack
We choose tools for what your team can maintain after handover, not for novelty. Typical stack for this service:
SentryBetter StackGitHub ActionsDependabotGrafanaFirebaseApp Store Connect
FAQ
Questions, answered.
Will you maintain an app you didn't build?
Yes — it is a large part of this service. We start with a paid audit so both sides know what we are taking on, and the audit report is yours regardless of whether you continue with us.
What happens if the app breaks at 2am?
That depends on your tier. Monitoring alerts fire regardless, and critical response windows are defined in your agreement by severity. We are honest that we are not a 24/7 network operations centre — if you need follow-the-sun cover, we will tell you to buy that instead of overselling you ours.
Why does an app need maintenance if nothing is changing?
Because everything around it changes. Apple and Google enforce new SDK requirements annually, dependencies get security advisories, TLS certificates expire, and third-party APIs deprecate versions. An app left alone for two years typically needs a significant remediation project to become releasable again.
Are new features included?
Small changes come out of an included monthly allowance on the higher tiers — copy edits, a new report column, a config change. Anything larger is quoted as a fixed-price piece of work so a retainer never quietly becomes an open-ended bill.
Can we cancel?
Yes, with 30 days' notice. There is no annual commitment, and on exit we hand over documentation, access, and monitoring configuration so the next team is not starting blind.
Do you monitor for security vulnerabilities?
Yes — automated dependency scanning on every repository, with critical advisories triaged and patched. For applications handling payments or health data we also schedule periodic security reviews against the OWASP Top 10.
Smaller ways to start
You do not have to commit to a whole build.
Most people arrive somewhere between “just curious” and “ready to sign”.
These are the smaller, fixed-fee ways in — each one useful on its own, and each one credited or extended
into a bigger project only if you decide you want that.
Code & architecture audit
You have a codebase — inherited, stalled, or just worrying — and want an honest read before committing to anything.
Written report on architecture, security, data model and deployment
A prioritised list separating genuinely urgent from merely untidy
A straight answer on repair versus rebuild, even when rebuild pays us more
The report is yours whether or not you continue with us
Not sure which fits? Describe the problem and we will tell you
— including when the answer is that you do not need us yet.
The Qalmax Promise
Six things we put in writing.
Not values on a wall — contract terms. Ask any other supplier to match them line by line.
A price in 24 hours
Send a brief, get a fixed written price and a delivery date the next working day. Free, no obligation, and the scope document is yours to keep even if you go elsewhere.
The price does not move
Fixed, not an estimate. If scope changes we re-quote in writing and you approve before we build it. You will never open a surprise invoice.
Half on delivery
50% to start, 50% when it is live and you are satisfied. You never fund the whole project up front.
Unlimited design revisions
We do not write production code until you approve the screens. Changing your mind at that stage costs nothing.
You own everything
Full source code, design files and credentials on delivery. No licence, no platform fee, nothing that stops another developer taking over.
30 days of fixes included
Free bug fixing for a month after launch, then an optional retainer only if you want one.
A paragraph is enough to start. You get a scoping conversation and a
fixed written price with a delivery date within 24 hours —
free, and yours to keep whether or not you go ahead with us.