Agents read the book
Software that reads the loan, decides what should happen next, and writes the proposal down before anything moves.
Servicing, monitoring, collections and recovery, inside your guardrails, with the goal of keeping operating cost from scaling linearly with the book.
Lokta is the agentic loan servicing platform for NBFCs, banks, fintech lenders and lending service providers (LSPs). Lenders run the live book on it after approval, inside their guardrails: servicing, monitoring, collections and recovery on a deterministic core. Agents propose, the lender's core decides, the record proves it. From the team behind Apache Fineract, for lenders in India and beyond.





Built by the team behind Apache Fineract*, the open-source lending core used by lenders in 70 countries.
Aggregate impact attributed to the Mifos/Fineract ecosystem, not Lokta directly.Read the impact essay
Most businesses end at delivery. Lending begins there.
Each application, repayment, and recovery can inform the next reviewed policy. Whether it improves the outcome is measured.
Repayment and recovery evidence can inform reviewed policy hypotheses. Improvement is measured, not assumed.
Agents can propose and evaluate candidates. Measure throughput and quality in the lender environment before claiming an improvement.
Measure servicing cost per account as volume grows. Do not assume a margin or portfolio outcome before the evidence exists.
Every claim logged, replayable, auditable.Audit by design isn't the pitch: it's the price of admission.
Lokta is built by the original architects and builders of Apache Fineract. We learned, at scale, what the next generation has to be, and Lokta is what we'd build if we started today.
"You cannot run a bullet train on narrow-gauge rails. The track width is the architecture. That's why we started over."
Agent-native means the operators of the book are agents: software that reads the loan, decides, and acts. Every agent action is a governed write, checked against your policy before it touches the book.
Software that reads the loan, decides what should happen next, and writes the proposal down before anything moves.
Built and governed in AI Studio, the AI control plane authorises, scopes, logs, and verifies agent actions. A kill switch is built in. The agent proposes. It does not post to the ledger. Your core does.
Two ledgers, the same inputs always producing the same outputs, and state changes on the loan record replayable for whoever asks.
Servicing, collections, and compliance, all on one ledger, with a loan product studio and servicing agents on the same canonical model. Or keep your existing Loan Management System (LMS) and run the agents on top of it.
Lokta Ledger, the deterministic loan engine your book runs on, with the Loan Product Studio that composes each loan product on top of it. Every product is one versioned contract, not a configuration row. Audit-ready, schema-per-tenant, governed APIs.
See loan managementOne inbox across WhatsApp, email, phone, and portal. Lending-aware triage, confidence-based automation, every resolution feeding the borrower model.
See AI loan servicingConnect Lokta to an existing loan system through a lender-specific data contract. Each rail, bureau, or partner connection is separately scoped, mapped, tested, and accepted before use.
See what Lokta runs onContinuous model-risk governance mapped to RBI's 2026 draft: validation, monitoring, and evidence organised for lender review. The regulated entity owns interpretation, submission, and accountability. Lenders under another supervisor's model-risk regime get the same validation, monitoring, and evidence structure.
See model risk managementLoan Origination is on the roadmap and is not available now. No release date is published. Read the roadmap design
Not ready for a conversation? Three ways to check our thinking against your own.
On-prem, VPC, or single-tenant cloud; maker-checker at the policy boundary; audit trails on state transitions.
For banks & NBFCsPolylithic modules, OpenAPI 3.1, Keycloak-native; extend in-tree, not by vendor SOW.
For fintechsMulti-partner from the core, per-partner isolation and audit, co-lending reconciliation native to the data model.
For LSPsIn lending, the autonomy you can audit is the only autonomy that scales.
A small number of institutions at a time: banks, NBFCs, and fintechs building a deliberate adoption, not a SaaS sign-up. If you already run a book, nobody is asked to cut it over.
Every agent action lands on the record before it lands on the ledger, so a model risk review has something real to check, not a screenshot.
Agents read, draft, route, and propose. Deterministic checks and required approvals control record-changing actions.
Repayment and recovery evidence can update reviewed hypotheses. Improvement requires a measured result.
We agree what a pilot has to prove with your risk and compliance people first, before a single loan moves.
Every enquiry is read by one of the founders, Ashok Auty or Chandramouli C S. Who they are
Every enquiry gets an answer. Sometimes it is a 30-minute call to dig in, sometimes it is "not yet, and here is what would change that."
Read what we're building towardApache, Apache Fineract and Fineract are trademarks of the Apache Software Foundation. Lokta is not affiliated with, sponsored by or endorsed by the Apache Software Foundation, the Mifos Initiative, or any other company named here.