Who built it
An idea, an engineering practice, and a company.
Three names appear on this software. They are not divisions of a marketing department - each did a distinct job, and the software would be worse without any of them.
Answerable for the software running your books.
Kalviyogi - the idea
That a shopkeeper should not have to understand double-entry accounting to have correct books, and should never lose a sale because a connection dropped.
It sounds modest. It is the reason for almost every hard decision in the software: derived balances rather than stored ones, invoice numbers reserved in advance, rules held in the database rather than in a checklist somebody has to remember.
369 Tesla - the engineering
The build, and the discipline behind it: nothing is claimed to work until it has been run. Every figure quoted on this site came out of a test suite or a live server, not an estimate.
Edunivra Private Limited - the company
The entity you have a relationship with, and the one answerable if the software running your books is wrong.
How it was built
Proved by running it, not by describing it.
A test that passes is evidence. A paragraph saying something works is not. These are the counts at the last build, and each is reproducible on the machine this is installed on.
The rules live in the database
An unbalanced voucher, a document carrying both CGST and IGST, an edit to a posted ledger entry, two invoice blocks that overlap: each is refused below the application, so a future change to the code cannot quietly undo it.
History is added to, not rewritten
Ledger entries, stock movements, the audit log and the withholding register are append-only. A correction is a new row that points at what it corrects, so the reason a number changed is still there next year.
Money never touches a floating-point number
Amounts are fixed-point from the database to the printed invoice. The one place decimals are usually lost - reading a row back into a program - is the place this is most careful about.
It runs on the machine you already have
One process serves the counter, the office, the customer portal and the API. No container runtime, no message broker, no second database. Node and MySQL, which is what ordinary hosting offers.
The honest part
What it will not claim.
Two things need an account with somebody else, and this software says so rather than implying otherwise.
It cannot take a card payment. It prints a UPI QR so the money goes straight to your bank, but nothing tells it the money arrived - so a QR never marks a bill paid.
It does not file your GST return. It computes them, keeps every revision, reconciles against GSTR-2B and exports in the portal's format. Filing needs a GST Suvidha Provider, and the acknowledgement number is recorded from what you were given.
Open it and judge it.
Everything above is checkable from the counter in about a minute.