Straight answers.
The questions we get asked — answered the way we build: plainly, and honest about what exists today versus what is planned.
Is Datavrn live software, or still being built?
Being built, and we say so plainly. The foundation — identity, multi-tenant isolation, the immutable audit trail, and the full data-ingestion layer — is built, tested and hardened. The financial engines that sit on top (allocation, consolidation, reporting) are built against a validated reference implementation and are being hardened ahead of a pilot with our design partners. Nothing on this site describes a capability we have not built or specified; where something is planned rather than live, we say planned.
Which systems does Datavrn read from?
Three ways in, today. Spreadsheet uploads — thirteen canonical templates covering the trial balance, transactions, receivables and payables, and the operating data around the ledger. Tally file exports — trial balance and day book, in the XML or Excel formats Tally already produces. And a Zoho Books connector that syncs over OAuth, with credentials encrypted at rest.
Ingestion is deliberately source-agnostic: every source lands through the same staged-confirm-snapshot pipeline, so adding a new system is an adapter, not a re-architecture. If your books live somewhere else, tell us — it informs what we build next.
What does setup actually look like?
You create your organisation, add your entities, and bring data in — the product suggests column mappings and account classifications, you confirm them, and your confirmations are saved so the next cycle is a re-upload, not a redo. Nothing is ever auto-applied: every mapping suggestion is reviewed by a human before it takes effect.
As a design partner, you would run the first reporting cycle alongside us. Part of what the programme establishes is exactly how long onboarding takes for different shapes of business — so we will not quote you a number we have not yet earned.
What does a design partner get — and what do you expect?
You get early access to the product, a direct line to the two founders, and a real say in what gets built — the methodology you have refined over years, encoded and running as software. We expect you to run it on genuine reporting cycles, tell us honestly where it falls short, and tolerate the rough edges of pre-release software. Commercial terms are agreed individually with each partner.
Where does our data live, and who can see it?
In India. The database runs in Mumbai (AWS ap-south-1) and a residency gate refuses any configuration that would move it. Your organisation’s data is isolated at two independent layers — application scoping and database row-level security — and cross-tenant isolation is proven by automated tests on every change. Internal access is read-only, restricted, and recorded in your own audit log. The full picture is on our security page.
Can we get our data back out?
Yes — the design principle is that nothing is held hostage. Your uploads are retained verbatim and can be rolled back. Your mappings — account classifications, cost-centre assignments, cash-flow categories — export as CSV and round-trip back in. Report output leaves as standard files, including a fully linked Excel workbook. Deleted entities carry a 30-day recovery window, recorded in the audit trail.
Does Datavrn run AI over our numbers?
No. No AI model touches customer data in v1 — deliberately, because a confidently wrong number would contradict the one thing this product exists to guarantee. If AI-assisted commentary is offered in future, it will be opt-in, disabled by default, restricted to aggregated data, and every invocation will be recorded in your audit log.
Does Datavrn replace our accountant or analyst?
No — it removes their plumbing. The judgement stays with your team: how costs should be apportioned, what a variance means, what the board should be told. Datavrn encodes those decisions once and executes them every cycle, with the working shown, so the people who understand the business spend their time on the decision rather than the assembly.
What does it cost?
Design-partner arrangements are agreed individually. General-availability pricing is not set, and we would rather publish nothing than publish a guess.
Who is behind Datavrn?
Two Chartered Accountants, both qualified in 2013, who spent their careers producing exactly this kind of reporting before deciding to build it as software. The longer version is on the about page.
A question we haven't answered? Ask us directly — or request early access and ask it in the conversation.
Request early access