Local development
Source-code development, learning, demonstrations and functional testing.
- CPU
- 2 CPU cores
- Memory
- 4–8 GB
- Storage
- 20 GB free
- Usage
- 1–5 users
Installation Guide · Step 2
Mifos X system requirements
Plan the infrastructure required for Apache Fineract, the Mifos Web App, the database, reports, scheduled jobs, integrations, backups and production operations.
Infrastructure planning
Starting server-sizing recommendations
Use these values as an initial planning baseline. Production sizing should be confirmed using realistic data and workload testing.
Testing and staging
Regression testing, migration testing, user acceptance testing and release validation.
- CPU
- 4 CPU cores
- Memory
- 8–16 GB
- Storage
- 50–100 GB
- Usage
- 5–50 users
Small production
Small financial institutions with moderate transaction and reporting workloads.
- CPU
- 4–8 CPU cores
- Memory
- 16 GB or more
- Storage
- 100 GB or more
- Usage
- Up to approximately 100 concurrent users
Medium or large production
High-volume deployments, multiple branches, large portfolios, integrations and intensive reporting.
- CPU
- 8+ CPU cores
- Memory
- 32 GB or more
- Storage
- Based on transaction volume
- Usage
- Load testing required
Software stack
Required software components
| Component | Recommendation |
|---|---|
| Operating system | A supported 64-bit Linux distribution such as Ubuntu LTS is generally preferred for production. |
| Java | Use the Java version required by the selected Apache Fineract release. Record the exact JDK vendor and version. |
| Database | Use a database version supported by the selected Fineract release and validate Liquibase migrations before production. |
| Node.js | Use the version required by the selected Mifos Web App source or release. |
| Web server | Use Nginx or another trusted reverse proxy for HTTPS termination, routing, caching and security headers. |
| Container platform | Docker is useful for repeatable environments, but image tags and persistent storage must be controlled. |
Capacity planning
Factors that affect performance
Number of active clients
Portfolio size affects database growth, searches, reporting and batch-processing time.
Daily transaction volume
Repayments, deposits, journal entries, charges and corrections influence application and database load.
Concurrent users
Server sizing must consider how many branch, operations and back-office users work at the same time.
Reports and analytics
Large operational and accounting reports can consume significant memory, CPU and database resources.
Scheduled jobs
Close of Business, accruals, penalties, notifications and batch jobs can produce workload spikes.
External integrations
Payment gateways, mobile apps, credit bureaus, messaging and APIs increase traffic and processing requirements.
Production readiness
Infrastructure checklist
A financial system requires more than a running application. Security, backups, monitoring, recovery and change control must be planned before go-live.
- Separate development, staging and production environments
- Managed or professionally administered database
- HTTPS certificate and secure domain configuration
- Daily automated database backups
- Off-server or off-site backup copy
- Application and database monitoring
- Centralised application and infrastructure logs
- Firewall and restricted administrative access
- Documented disaster-recovery procedure
- Documented restore test and rollback procedure
- Regular operating-system and dependency patching
- Load and performance testing before go-live
MifosX infrastructure assessment
Unsure how much infrastructure your Mifos deployment needs?
MifosX can review your portfolio size, user concurrency, transaction volume, integrations, reports and growth plans to recommend a suitable production architecture.