The old team is gone
There is a repository, but little context, weak documentation, unclear access, and no clear release process.
Custom software audit
Custom software audit before maintenance or rebuild
FRAI reviews existing software, old repositories, deployments, integrations, hosting, and documentation before deciding whether to maintain, modernize, migrate, or rebuild.
When a software audit makes sense
The audit is for companies that already have software in production, but no longer know if it can be trusted, changed, or maintained.
The app works, but nobody wants to touch it
Dependencies are old, integrations are fragile, hosting is unclear, and every change feels risky.
Maintenance is being discussed too late
The company asks for maintenance, but the first question is whether the system can be recovered and controlled.
What FRAI checks
The audit is not a long report for its own sake. It tells us what can be kept, fixed, moved, or rebuilt.
Repository, branches, dependencies, build process, and deployment notes
Hosting, domains, SSL, credentials, logs, alerts, backups, and recovery
Database structure, data flows, integrations, APIs, forms, and automations
Security risks, access control, exposed secrets, outdated packages, and missing controls
Documentation, release process, ownership gaps, and maintenance workload
What can be kept, what should be fixed, and what should be rebuilt
Possible outcomes
After the audit, FRAI says which path fits the system: maintain it, recover it first, or rebuild the parts that are too risky.
Maintain
The system is clear enough to bring under FRAI control and start maintenance.
Modernize or migrate
The system can be recovered, but needs dependency work, deployment fixes, hosting changes, documentation, or integration cleanup first.
Rebuild
The codebase is too risky, undocumented, insecure, or blocked by old choices. The safer path is to rebuild the critical flows.
The boundary
FRAI audits existing software to decide whether it can be run safely. We do not accept blind deployment work for third-party repositories. If FRAI cannot understand and control the system, we will not maintain it as it is.
Questions before the audit
These questions usually come up when a company has an old system, an external repository, or a software supplier that is no longer available.
Can FRAI audit an old software repository?
Yes. FRAI can review the repository, dependencies, deployment, hosting, integrations, data flows, documentation, and security risks before deciding the next step.
Can FRAI maintain software after the audit?
Yes, if the audit shows that the system can be brought under FRAI technical control. If not, the first step is stabilization, modernization, migration, or rebuild.
Does FRAI deploy third-party repositories without changes?
No. Blind deployment of a third-party repository is too risky. FRAI only deploys and maintains software it understands and can run safely.
What if the software cannot be recovered?
FRAI will say so. If the repository is too risky or broken, the next step is to rebuild or migrate the critical flows instead of maintaining a weak base.
How much does a software audit cost?
It depends on system size, repository access, hosting, integrations, data, and documentation. FRAI defines the audit scope before starting.
Next step
If the system can be recovered, it moves into maintenance. If it cannot, the next step is a focused rebuild.