1,594 automated tests · 25 ledger checks · nothing cached

Your books, understood — not just recorded.

A multi-company accounting platform built for Indian business: a real double-entry ledger with database-enforced tenant isolation, GST working papers, bank reconciliation you can explain line by line, inventory, payroll and management reporting — over an audit trail that is sealed against tampering.

Start free Explore the demo books

No card required
Multi-company from day one
Your data stays yours

Trial balance

1 Apr 2026 — 31 Mar 2027

Balanced

Account	Debit	Credit
Cash in hand	2,84,500.00	—
Sundry debtors	11,42,300.00	—
Stock in hand	6,18,900.00	—
Sundry creditors	—	4,96,700.00
Output CGST	—	1,07,325.00
Output SGST	—	1,07,325.00
Sales	—	11,92,500.00
Capital account	—	1,41,850.00
Total	20,45,700.00	20,45,700.00

Difference 0.00 · derived from 100,000 vouchers in 41 ms

The dashboard — What was billed, what came in, what is still owed — and how late it is. — What was billed, what came in, what is still owed — and how late it is.

A photograph of the running application against seeded books, not an illustration. See 11 more screens.

What this is

An invoice is a by-product. The ledger is the product.

Most billing software prints a document and files a copy. When the year ends, somebody rebuilds the accounts from those copies. This works the other way round: every transaction is a balanced voucher first, and the invoice is what one kind of voucher happens to look like on paper.

Billing software

Documents, with totals stored on them
Reports assembled at year end
Stock and books reconciled by hand
“Export it to your accountant”

Falcon

Balanced vouchers against a chart of accounts
Statements derived on every request
Stock movement and ledger entry in one transaction
Your accountant works in the same books

The platform

Six areas, one set of books

Every module posts through the same engine, so there is no interface between them to fall out of step.

Coming from somewhere else

Your existing books come with you

Point it at the Tally running on your own network and it reads the masters and the day book across. Ledgers, customers, items and opening balances also come from a spreadsheet. Either way everything is staged and shown to you before a single entry is posted, and the assistant explains why it chose each ledger.

Bringing existing books in

Connect to Tally over your own network. Nothing leaves the premises.

The assistant

Say what you want done. It shows the exact entry before anything happens.

Take the full tour

Measured, not claimed

Numbers produced by commands in the repository

Every figure below comes from something you can run — the test suite, the load test, the backup rehearsal. None of it comes from a marketing meeting.

Vouchers load-tested: 100,000134 a second on PostgreSQL, in one company
Trial balance: 41 msBalance sheet 128 ms, over the same year
Automated tests: 1,594Plus 177 end-to-end tests through a real browser
Isolation policies: 91Row-level security, forced, on every tenant table

How it is built

The guarantees underneath

These are not features you switch on. They are properties of the system — which is what makes them the hardest part to retrofit, and the easiest part to fake.

Isolation the database enforces

Sixty-seven row-level security policies with FORCE, plus a restricted role that cannot bypass them. The application refuses to serve production traffic on a connection where those policies would be inert — because that failure is invisible from every screen.

Built for more than one company

Companies, financial years, numbering series and consolidation with intercompany elimination. Group reporting is not a separate product here.

Nothing stored twice

Every total is derived from postings. There is no cached balance to go stale, no nightly rebuild, and no support ticket that begins “the report disagrees with the ledger”.

Nothing here is connected to a government system. No filing credential is stored, no portal is scraped, and no return is submitted on your behalf. Identifiers produced by the e-invoicing screen are marked SANDBOX and must not be issued to customers.

Read the security page

Straight answers

The four questions everybody asks

All the answers

Is this an invoice generator?

Invoicing is one voucher type out of eleven. Underneath it is a double-entry ledger with multi-company books, GST, banking, inventory, payroll, fixed assets, period close and consolidation — the invoice is simply the document a sales voucher happens to produce.

Does it file my GST returns?

No, and it holds no credential that would let it. It prepares working papers you or your accountant can check and file. The e-invoicing screen runs against a mock provider, says so on screen, and marks every identifier it produces as SANDBOX.

How is one company kept separate from another?

By PostgreSQL, not by a filter in the application. Sixty-seven row-level security policies with FORCE, and a restricted database role that cannot bypass them. The application refuses to serve production traffic on a connection where those policies would be inert.

What happens when the books do not agree?

Twenty-five integrity rules run over the whole ledger and return the rows that failed — unbalanced vouchers, control accounts that disagree with their subsidiary, negative stock, gaps in a numbering series. You get the entries to look at, not a warning light.

Open the demo books and look around.

A seeded company with a year of real transactions behind it — vouchers, stock, payroll, a bank statement waiting to be reconciled. Nothing to install.

Start free See the whole platform