The Lerian Console is the unified web interface for managing and operating all Lerian products. It provides a single point of access for configuration, monitoring, and administration across the entire Lerian ecosystem. Built as a cross-product workspace, the Console centralizes navigation, authentication, and product management — allowing you to work with multiple Lerian products through one consistent experience.Documentation Index
Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
Use this file to discover all available pages before exploring further.
Architecture
The Console is organized into two layers:
- Platform layer — Shared capabilities that apply across all products: centralized authentication, product catalog, global navigation, language preferences, session policies, and feature flags.
- Product layer — Each Lerian product integrates as an independent module with its own navigation, workflows, and product-specific settings, while sharing the same design patterns.
Key capabilities
- Single sign-on: Log in once and access all enabled products without re-authenticating.
- Role-based access: Control who can access which products and features based on roles and permissions.
- Product management: Enable, disable, and configure products from a central dashboard.
- Unified experience: Navigate between products seamlessly with consistent UI patterns.
Who uses the Console
| Role | Primary activities |
|---|---|
| Platform administrators | Enable/disable products, manage users and roles, configure global settings |
| Product operators | Access enabled products, perform day-to-day operations, configure product-specific settings |
| DevOps teams | Install and update the platform, monitor system health, manage deployments |
Console modules
Each product has its own module in Lerian Console:
Midaz
Core ledger management — organizations, ledgers, accounts, assets, accounting, and transactions.
Reporter
Report generation and template management for financial and operational data.
Matcher
Automated reconciliation — matching rules, data sources, exceptions, and reconciliation workflows.
Flowker
Design visual workflows, configure provider integrations, run automated processes, and monitor executions through the Flowker module.
Tracer
Configure real-time fraud detection rules, set spending limits, and review the audit trail of every transaction validation decision.