Backend and core banking engine
Apache Fineract
Latest published release: 1.15.0
Use a tagged stable release. Validate database migrations, APIs, accounting, scheduled jobs and integrations before production deployment.
Installation Guide · Step 1
Which Mifos X version should you install?
Mifos X is made up of multiple components. Selecting only the newest backend or frontend does not guarantee a reliable installation. This guide explains how to choose, test and record a compatible deployment stack.
Understand the platform
Mifos X is not one single application
A working Mifos installation normally includes Apache Fineract, a user interface, a supported database and production infrastructure. Each component must be selected and validated together.
Angular-based user interface
Mifos Web App
Main branch is described as the stable branch
Use a tested commit or release reference. Do not deploy an unrecorded moving branch directly into production.
Legacy Mifos user interface
Community App
Primarily used by older installations
Retain only for existing implementations that depend on it. New deployments should evaluate the current Mifos Web App.
Deployment recommendation
Select versions based on your deployment objective
New production implementation
Select a stable Apache Fineract release and lock the exact Mifos Web App commit that has been tested with it.
- Record backend version and Git commit
- Record frontend version and Git commit
- Complete functional regression testing
- Complete accounting validation
- Test scheduled jobs and Close of Business
- Test reports and integrations
Local learning or demonstration
Use the official or project-provided Docker Compose setup. It is suitable for learning but should not automatically be treated as production architecture.
- Use disposable test data
- Avoid real customer information
- Document container image tags
- Expect configuration to differ in production
Existing Mifos installation
Do not upgrade directly without reviewing database migrations, customizations, APIs, reports and frontend compatibility.
- Take complete backups
- Clone production into staging
- Review every intermediate release
- Test custom code and integrations
- Prepare rollback procedures
Validation
Version compatibility checklist
A successful login does not prove that the complete platform is compatible. Validate all important business and technical areas.
| Validation area | Question to answer |
|---|---|
| REST APIs | Does the frontend use endpoints and request formats supported by the selected Fineract version? |
| Authentication | Are login, tenant headers, roles, permissions and token settings compatible? |
| Database | Have Liquibase migrations been tested against a copy of the actual database? |
| Loan processing | Have loan schedules, repayments, reversals, rescheduling, write-offs and Close of Business been tested? |
| Accounting | Have journal entries, accruals, reversals, closures and financial reports been reconciled? |
| Reports | Do operational, portfolio, accounting and custom reports work with the selected version? |
| Integrations | Have payment, credit-bureau, mobile, notification and external API integrations been retested? |
| Infrastructure | Are the selected Java, database, Docker and operating-system versions supported by the deployment? |
MifosX implementation guidance
Maintain a deployment compatibility register
For every environment, record the exact frontend commit, backend release, Java version, database version, operating system, container image tags and customization release.
Development environment
Used for coding, experimentation and automated tests.
Staging environment
Mirrors production for migration and regression testing.
Professional version assessment
Planning a new Mifos deployment or upgrade?
MifosX can assess your existing platform, customizations, database, reports and integrations before recommending a safe Apache Fineract and Mifos upgrade path.