About
Built because most billing software is not accounting software.
A company can run for years on documents and spreadsheets and never notice that nothing underneath it ties. The point at which it matters is always the worst possible one.
Why
The gap this fills
Indian business software divides oddly. At one end there are invoice generators — quick, pleasant, and structurally incapable of producing a balance sheet. At the other there are full accounting packages that assume a trained operator, a desktop, and a tolerance for interfaces designed decades ago.
In between sits almost everybody: a business with real inventory, real GST exposure, staff on payroll, several bank accounts and more than one company — and no system that holds all of it in one ledger.
Falcon is built for that middle. A real double-entry engine with the compliance work India actually requires, wrapped in an interface that does not assume you enjoy accounting software.
The name is a claim, so the product has to earn it: books that are continuously checked rather than periodically trusted, and every figure traceable to the entries that produced it.
Principles
Six decisions everything else follows from
These were settled early, and most of the difficult parts of the system are consequences of them rather than choices made later.
01The books are the product
Everything else — the invoice, the report, the dashboard — is a view of the ledger. When a system treats documents as primary and the ledger as a summary, the two drift, and reconciling them becomes somebody’s permanent job.
02Store nothing twice
No cached balances, no nightly rebuild, no denormalised totals. A derived figure can be wrong; a stored copy of a derived figure will be wrong, eventually, and nobody will know when it started.
03Correctness belongs in the database
Balance constraints and referential integrity are enforced by the database, where they cannot be talked past. Keeping businesses apart is moving there too: every query is scoped by the application today, and the database’s own policies bind on writes. An application-level rule is a rule until somebody writes a new code path.
04Say what it does not do
Every limitation on this site is stated on the page it belongs to. A product that overstates what it is connected to is not merely embarrassing in accounting software — it is a compliance risk for the person who believed it.
05Motion should mean something
Animation is used to show order and relationship, and it is switched off entirely when the operating system asks for reduced motion. A ledger read for eight hours a day should not shimmer at anybody.
06Original, throughout
No screen, wording, icon or asset is copied from any other accounting product. Where a convention exists because accountants expect it — a trial balance with two columns — the convention is followed; everything else is our own.
Godengine
What “Powered by Godengine” means
The engine is the part underneath: the posting path, the integrity rules, the audit chain, the isolation model. The product is what you use; the engine is what makes its guarantees hold.
- Automated tests
- 2,410Across the engine and the screens
- Integrity rules
- 26Run over the whole ledger
- Isolation policies
- 95In PostgreSQL, binding on writes today
- Capabilities
- 69Across 8 roles
Have a look for yourself.
Create an account and try it with made-up figures. Free while in preview, with no card.