Your invoices never leave your network.
M³ runs on your own server or laptop. There's no cloud version to opt out of — this is the only version.
Most invoice-matching tools are SaaS: your vendor data, bank details, and GST numbers sit on someone else's servers, reachable from the internet by design. M³ is built the other way around — it installs on infrastructure you already control, behind your existing firewall, and it stays there.
Point it at a local AI model — Ollama, LM Studio, or vLLM — and invoice data never leaves your network at all, not even for the AI reading step. For a finance team that isn't allowed to send vendor bank details to a third-party cloud, that's the deciding factor, not a nice-to-have. Teams without that restriction can just as easily use a hosted provider — Gemini, GPT, or Claude — it's a Settings-page toggle, not a one-way decision.
The specifics your IT team will ask for
- 01
Field-level encryption at rest for every sensitive value — vendor bank account numbers, IFSC, GSTIN, PAN.
- 02
Role-based access — Viewer, Approver, Admin — enforced on every route on the server, not just hidden in the interface.
- 03
A full audit log — every login attempt, every setting change, every invoice action, permanently recorded.
- 04
Brute-force lockout (5 wrong passwords locks the account for 15 minutes), CSRF protection site-wide, rate limiting on sensitive endpoints.
- 05
Hardened report exports — every value is escaped before rendering, closing a class of injection risk other invoice tools leave open.
- 06
A Duplicate & Fraud Risk Report rolling every fraud signal into one view: duplicate invoice numbers, same-PO re-billing, vendor bank-account mismatches, over-billing.
Security here starts with where the data lives: on your own infrastructure, backed by the mechanisms above. No SOC2 badge, no zero-trust claim, no certification we don't actually hold.
Request the trial