Applications
Every application, and where it runs
35 applications across both editions. Each one says plainly which suite it ships in — because a module that exists in one and not the other is the thing worth knowing before you choose.
How this directory works
Every application is listed
All 37 of them, including the 2 that do not exist yet. Nothing is filtered out to make the catalogue look fuller, and nothing is added to make it look longer — this is the registry, rendered.
The edition chips are evidence-backed
An application is marked as shipping in an edition only when there is a mounted router and real screens behind it. The chips were built by reading the code, not by reading a product brief, which is why some of them say less than we would like.
“Coming soon” means nothing exists
Not a beta, not a preview, not a partial. A card marked that way has no page behind it and cannot be clicked, because a link would imply a product. Payroll and the native mobile app are the two.
Some are deliberately shallower in one edition
Where an application is materially thinner on Desktop than on Cloud, its page says so in words and its card carries an amber marker. Manufacturing meaning single-level BOM in one edition and a full MES in the other is exactly the kind of gap worth finding now.
Applications are not the same as packs
These are the horizontal spine — the things every business might use. Industry packs re-shape them for a trade and live under Industries. A pack changes the screens over these applications; it does not replace them.
They all share one database
Switching an application on adds menus to the same login and the same books. There is no integration step, no connector to configure and no sync to fall behind, because there are not two systems to keep in step.
Questions about the catalogue
How many applications does LekhaPro have?+
35 that ship today, listed above with the edition each one runs in, plus 2 marked as not yet built. We count what exists rather than what is planned, so the number here matches the number of pages you can actually open.
Do I have to pay for each application separately?+
No. They are part of the suite rather than a marketplace of paid add-ons, and there is no per-application or per-use charge. Your plan tier decides reach and depth — devices, multi-branch and multi-warehouse reporting, and whether the conversational AI copilots are on — not which applications you may open.
Do I have to switch them all on?+
No, and you should not. An application you have not enabled adds no menus, no fields and no clutter, which is the point of a modular catalogue — you are never paying attention to a trade or a workflow you are not in. Switching one on or off is a settings change, not a migration.
What is the difference between an application and an industry pack?+
An application is horizontal — accounting, inventory, CRM, documents — and behaves the same for every business. An industry pack re-shapes those applications for a trade: different screens, documents, statutory forms and workflows over the same double-entry books. A pack changes the surface; it never forks your ledger.
Why are some applications Cloud-only?+
15 of them are, and it is usually because the depth they carry assumes a connected team — external portals, approval chains, multi-branch roles and audit trails. The Desktop edition is built around a local database on your own machine at one site, and we would rather leave an application out of it than ship a hollow version.
Can I see which applications are in the Desktop edition before I buy?+
Yes — that is what the edition chips on every card are for, and there are dedicated catalogues at /desktop/apps and /cloud/apps showing only what that suite carries. The comparison page puts the two side by side if the choice is what you are actually deciding.
Are “coming soon” applications included in a plan?+
They are not, because they do not exist. Two entries are marked that way — Payroll and HR, and the native mobile app — and neither has a page, a beta or a date. Please do not buy a plan on the expectation of either arriving; buy for what the catalogue shows as shipping today.
Do the applications share data, or do I have to integrate them?+
They share one database, so there is nothing to integrate. A customer created in CRM is the customer the invoice bills and the collections screen chases; stock moved by a sale is the stock the balance sheet values. No connectors, no nightly sync, and no reconciliation between your own screens.
What happens to my data if I stop using an application?+
The menus go and the rows stay. Turning an application off hides its surface without deleting anything it created, so the decision is reversible and is never a data-loss event — switch it back on and you are returned to the records you left.
Is this list kept up to date?+
It cannot go stale, because it is not a list. Every card, count and edition chip on this page is rendered from the same registry the application pages and the sitemap are built from, so an application cannot appear here without a page behind it or ship into an edition without the chip changing.