Three layers, in the order they are built. The entities you run become the core. The apps you choose sit on top of them. The workforce you hire operates the whole thing. Add to any layer at any time and watch the model change.
Start with a country. Everything else stands on it.
Drag to turn · click a block to remove it
01
Step 1 of 3
None yet
Entities. Which legal entities do you have?
Each one is a statutory book in its own currency, on one ledger. Consolidation is not a month-end project; it is the same ledger read from the top.
Start from a setup Or pick countries below
Countries 22 where Light runs a book today
02
Step 2 of 3
None yet
Apps. Which apps do you want on top?
Apps extend the core rather than sitting beside it: they read and write the same ledger, so there is no export, no side system, and nothing to reconcile between them.
Choose at least one country first.
For your entities
Every app
These are the apps you choose. The banks and payroll providers Light connects to, 681 of them, come with the platform: see Light Apps.
03
Step 3 of 3
None yet
Workforce. What are the rules, and who does the work?
Start with the policies: they define what right looks like. Executive agents then do the work, workflows run the steps that must never vary, and a read-only audit agent checks all of it against the policies you adopted.
Choose your apps, or skip them, first.
Policies The rules everything else is measured against.
Executive agents They do the work, end to end.
Workflows Fixed steps that run the same way every time.
The three layers are not three products you integrate. They are one system, and each one only works because of the one beneath it.
1
The core records
One ledger holds every entity, every currency and every transaction. A second book is not a second system: it is another set of statutory rules over the same data, which is why consolidation is a view rather than a project.
Local rates, audit files, payroll postings, the reporting your board asks for: built as apps on the same ledger, and maintained for you. When a government moves a mileage rate, the app moves with it.
Your policies define what right looks like. Executive agents do the work end to end, workflows run what must never vary, and a read-only audit agent checks every one of them against those policies, every month.
Hand us the code and we will open exactly what you configured, your entities and your apps and your agents, instead of a generic tour. The code carries the whole build, so it works from any browser, with nothing saved anywhere.
