apache/fineract

Apache Fineract is an open-source core banking platform intended as a foundation for financial services aimed at underserved populations. Its most relevant fit is an institution or vendor that needs a lending, savings and group-finance backend and is prepared to build or buy the user-facing layer separately: the project supplies an API, not a UI. It is a verified Digital Public Good under Apache-2.0 repository.

What it provides

The platform is a Java backend covering banking domains such as loans, savings and group lending, exposed through a documented API. Its OpenAPI specification supports client code generation, and a live Swagger sandbox is linked for exploring endpoints platform API section.

How a deployment is put together

Running it locally means PostgreSQL on port 5432, a JDK, and the Gradle tasks that create the tenant and default databases before starting the backend on port 8443. Readiness is confirmed through an actuator health endpoint; authenticated calls require the tenant header and credentials quick start. The official Docker image bundles only the PostgreSQL JDBC driver, and the container images are explicitly not production-ready — the test Spring profile is enabled in the compose setup, so securing a real instance is the operator's responsibility production notes.

Larger installations can optionally fan out the Close of Business Day batch job across worker nodes via ActiveMQ or Kafka; both are disabled by default. Whatever path is used, JAR, WAR on Tomcat, Docker or Minikube, prerequisites are documented per route in the development environment guide requirements.

Production and licensing caveats

The project states plainly that a production deployment can be complex, costly and time-consuming, covering security, compliance, backups and availability, and that it does not provide a comprehensive production guide. Enterprise Java skills or a paid vendor may be needed deployment docs.

MySQL and MariaDB support is deprecated in favor of PostgreSQL, and their JDBC drivers are excluded from all distributed artifacts because of license incompatibility, so they must be supplied at runtime license section. Using MySQL also requires UTC handling to avoid misread historical dates during migrations.

HotRepo's take

On 2026-10-29 the repository was recorded on the daily trending board at 2,582 stars with a +3 gain that day. That is a single dated observation, not evidence of a trend.