Deployment Strategy, Evaluation and Implementation Guide for mid to large size Financial Institutions for Accounting, lending and savings product management.
This is a derivative document, published by Muellners Foundation, licensed under The Creative Commons Attribution-ShareAlike 4.0 International Public License (Creative Commons — Attribution-ShareAlike 4.0 International — CC BY-SA 4.0)
Muellners Foundation does not take any responsibility and liability over the accuracy of the content, published here.
It is a non commercial Support content, which covers following open source projects namely: Mifos X community app
Apache Fineract.
Foundation community has created and published this wiki and routinely updates this, because we love open source and support open source projects for humanitarian reasons.
Guidance for Reading: This document is written with a view of Apache Fineract’s delivery into the existing technology frameworks of a "mid to large" scale/size Financial Institutions.
The sample institutions(FIs) offer wide range of financial instruments and products such as Checking, Savings, Lending, Micro-finance, Payment Processor Systems, credit cards, mortgages, other personal and commercial loans as well as trust and investment services. This documentation may also be used by Fintech aiming to have the scalability equivalent to sample Financial institutions.
Goal of the Guide: This guide details and describes a standard Apache Fineract and Mifos community app based 'core financial system' deployment. It also enlists necessary guiding principles to follow during different phases of such deployments.
Public Notice: The Apache Fineract, as further described on, including the organizers and other participants of the Apache Fineract community, (collectively, “Fineract”) will have no obligation to the accuracy and maintenance of this derivative documentation.
The Mifos Foundation, as further described on including the organizers and other participants of the Mifos X community, (collectively, “Mifos”) will have no obligation to the accuracy and maintenance of this derivative documentation.
Public Notice:
For public discussions; you can access #observationdeck1
We are currently observing few modalities of the third party projects listed in this guide, to define best practices for Open Source compliances namely:
a. Intellectual Property ownership changes through different legal bodies, of these project's history.
b. Diversity and Equity policies of the US based public charities, maintaining these projects,
c. the governance structure(s) of the Project Lifecycle Managements including volunteer IP contribution protection
d. Export restrictions on a US made software, including SBoM compliances
Contribute to the knowledge base here;
Follow a relevant public discussion here:
Last modified 4d ago