January 16, 2026 Documentation update Review recommendedDocumentation Index
Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
Use this file to discover all available pages before exploring further.
Affects
Teams using the standalone Midaz Console or planning web-based operations across Lerian products. This update applies to the public documentation portal. It does not change the runtime API behavior unless the linked product documentation says otherwise.
What changed
We’re excited to announce Lerian Console — the unified platform that brings together all Lerian products under a single, cohesive interface.
What’s new?
Unified platform experience
Lerian Console replaces the standalone Midaz Console with a modular architecture that supports multiple products:- Midaz Module — All the ledger management capabilities you know, now integrated into Lerian Console
- Reporter Module — Dynamic, customizable reporting with reusable templates and downloadable reports
Key changes
- Single entry point — Access Midaz, Reporter, and future products from one interface
- Product launcher — Switch between modules seamlessly using the new product launcher
- Improved navigation — Reorganized sidebar with clear sections for Foundation, Accounting, Accounts, Transactions, and Plugins
- Better integrations — Seamless connections between modules and plugins like CRM and Fees Engine
Migration from Midaz Console
What stays the same?
- All core Midaz functionality remains available
- Your data and configurations are preserved
- The interface and workflows are familiar
Why migrate?
- Continued development — New features are exclusively available in Lerian Console
- Unified experience — Access all Lerian products from a single interface
- Enhanced workflows — Improved UI, navigation, and cross-module integrations
Documentation updates
We’ve restructured the documentation to reflect the new architecture: Ready to explore? Head to the Lerian Console documentation to get started.
Impact
This is a documentation update. Existing integrations do not need a migration from this release note alone.

