Maintenance model
StabilizeCustom software maintenance
Custom software maintenance for applications under FRAI control
Custom software maintenance keeps the application layer supportable after launch through bug fixes, dependency updates, documentation, controlled releases, and planned changes. It owns code and workflow upkeep; infrastructure operation is covered by the separate hosting and maintenance service.
Maintenance model
MonitorMaintenance model
MaintainMaintenance model
Improve01
When maintenance becomes urgent
Most software risk appears after launch: tools change, people leave, integrations break, and nobody has a clean operating record.
01
No owner for incidents
The software is used every day, but support, fixes, access, monitoring, and recovery are unclear.
02
Old dependencies and fragile integrations
APIs, forms, libraries, hosting, permissions, domains, and backups drift until a small issue blocks work.
03
No controlled change process
Teams keep asking for changes, but there is no clear work list, documentation, or release process.
02
What maintenance covers
This service owns application-level continuity and controlled change. Hosting infrastructure, uptime monitoring, backup routines, and recovery procedures belong to the hosting and maintenance scope.
- 01
Bug diagnosis, corrective fixes, and application-level incident support
- 02
Dependency updates, security patches, workflow corrections, and small changes
- 03
Integration upkeep for APIs, forms, CRM, ecommerce, payments, and internal tools
- 04
Custom CRM maintenance for records, dashboards, permissions, integrations, and workflow changes
- 05
Technical documentation, integration maps, release notes, and change records
- 06
Controlled testing, release coordination, and post-release application checks
- 07
Prioritized monthly change work for software under FRAI control
03
Audit before maintenance
If the software already exists, FRAI starts by checking whether it can be operated safely. The outcome decides whether we maintain, modernize, migrate, or rebuild.
01
Technical audit
Repository, dependencies, deployment, hosting, logs, security, data flows, integrations, documentation, and recovery paths.
02
Maintenance type
Corrective maintenance for defects, preventive maintenance to reduce risk, and evolutive maintenance for business changes.
03
Monthly plan
Response expectations, monitoring, backups, update rhythm, monthly changes, and the minimum control needed before FRAI takes responsibility.
04
CRM maintenance path
For an existing CRM, FRAI checks fields, permissions, reports, automations, integrations, hosting, and data quality before accepting maintenance.
04 — The boundary
No maintenance without technical control.
FRAI does not take generic responsibility for software built by third parties. If the system is not under FRAI control, the first step is a stabilization, rebuild, or migration project. Maintenance starts only when FRAI can operate the software responsibly.
FRAI maintains software it builds, rebuilds, migrates, or stabilizes under its technical responsibility.
05
Questions before starting maintenance
These questions decide whether maintenance can start directly or whether the software first needs an audit, modernization, rebuild, or migration.
Can FRAI maintain software built by another team?
Not as a simple handover. FRAI first audits the repository, infrastructure, documentation, dependencies, data flows, and deployment process. If the system can be recovered and brought under FRAI technical control, we can stabilize, modernize, migrate, or rebuild the necessary parts before maintenance starts.
Can FRAI take an old repository and modernize it?
Yes, when the audit shows that the codebase is recoverable. FRAI can update dependencies, clean up architecture, improve deployment, restore documentation, fix fragile integrations, and create a maintainable base for future work.
What happens if the old software is not recoverable?
If the audit shows that the repository is too risky, undocumented, insecure, or structurally broken, FRAI will not maintain it as it is. The responsible path is a rebuild, migration, or replacement of the critical flows.
Does FRAI simply deploy repositories built by others?
No. FRAI does not take an external repository and just deploy it. That creates too much operational risk. Deployment, hosting, monitoring, backups, and maintenance are offered only when FRAI understands and controls the system.
What does custom software maintenance include?
Maintenance can include monitoring, updates, bug fixes, backups, restore checks, incident response, access control, documentation, security hygiene, integrations, and scheduled changes for software under FRAI responsibility.
How much does custom software maintenance cost?
Cost depends on the audit: code quality, business criticality, hosting, integrations, monitoring needs, support expectations, security risk, and the monthly work needed. FRAI defines the maintenance plan only after understanding the system.
Can FRAI maintain a custom CRM?
Yes, when the CRM can be brought under FRAI technical control. Maintenance can cover hosting, monitoring, backups, fields, permissions, reports, integrations, bug fixes, documentation, and monthly workflow improvements.
When should a company rebuild instead of maintaining?
A rebuild is usually better when the software has no clear owner, no reliable deployment process, weak documentation, fragile integrations, old dependencies, security issues, or a structure that blocks normal changes.