Trust you can verify
The code that computes your interest, posts your GL entries, and builds your schedules is code your engineers and auditors can read — not a black box behind an SLA.
Open source · Apache 2.0
The lending core is open source. Your exit strategy is real.
The system of record that holds your loans ships under Apache 2.0 — a modern core, rewritten nearly end to end from its Apache Fineract roots. Read it, audit it, fork it, keep it — the ledger your business depends on should never be somebody else’s secret.
Why open source
Because your ledger is not a place for secrets
Lenders have been trained to accept that the system holding their loans is a black box they rent. We think the opposite: the deeper a system sits in your business, the stronger your claim to see inside it.
An exit that actually exists
Apache 2.0 means run it, modify it, fork it — with us or without us. Leaving a vendor should be a migration project, not a hostage negotiation.
Modern core, proven roots
We started from Apache Fineract, then rebuilt the core almost entirely. What we kept is what a decade of production portfolios at regulated institutions taught the community — the lending semantics that have to be right.
Open standards everywhere
Standard databases (PostgreSQL, MariaDB), standard deployment (Docker, Kubernetes), documented REST APIs with OpenAPI specs — nothing about your stack is proprietary to us.
The honest split
What's open, and what's commercial
Open-core done straightforwardly: the system of record is open source; the servicing intelligence on top of it is our commercial product. No asterisks, no bait-and-switch relicensing.
Open source — Apache 2.0
The lending core: configurable loan products, schedule engines, payments, charges, delinquency, integrated accounting and GL, and the REST APIs over all of it — the complete loan management system your portfolio lives in.
Explore the lending coreCommercial — the servicing plane
The servicing control plane, servicing workspace, and AI agent workforce — the governed automation layer — are licensed commercially. They attach to the open core (or yours) through a clean fact/action contract, and detach the same way.
See the full platformNo lock-in, concretely
What leaving would actually look like
“No lock-in” is a slogan until you ask a vendor to describe the exit. Here is ours, in specifics.
- Your loan data lives in an open, documented schema on a database you already know how to operate and back up
- Every capability is exposed over documented REST APIs — the same governed surface our own UI uses
- The core deploys as a standard container on your cloud or ours — no appliance, no proprietary runtime
- Attribution from the core's Apache Fineract origins is preserved intact — we rewrote the code, not the history, and we credit the community's work as Apache 2.0 intends
The repo opens with our public launch
Design partners get the code and the one-command demo environment first — including teams evaluating the core as part of technical diligence.
Request early accessFAQ
What buyers ask about the open core
No, and we are deliberate about saying so. LendEasy is open-core: the lending core — the system of record holding your loans, schedules, payments, and accounting — is open source under Apache 2.0. The servicing control plane, servicing workspace, and AI agent workforce are commercial products that run on top of it (or on top of the core you already have). The part of the stack you most need to control and audit is the part you can read and keep.
Kick the tires before you commit
Evaluate the open core as part of your diligence: read the code, run the demo, and pressure-test the exit story with the founding team.