Loading page
Backups, security, database growth, failed scheduled actions, email delivery, permissions, modules and version risk — scored, with every finding tied to the number it came from. We never ask for a password.
Three levels
Twelve questions about your Odoo, scored, with the headline risks named.
Free
Immediate.
You run a read-only diagnostic inside your own Odoo and paste the output. We score eight dimensions from the real numbers.
$49
Scored immediately, reviewed by a person within one business day.
The report, plus an engineer going through it with you and telling you which findings actually matter for your situation.
$149
Session booked within three business days.
We do not want your password
Eight dimensions
An untested backup is a belief, not a backup. This is the only dimension where being wrong can end a company.
Whether you could answer "who changed this" six weeks after it happened, rather than guess.
Size, growth and the tables that cause both. A database nobody watches becomes a database nobody can upgrade.
Odoo runs most of its automation on cron. A failed scheduled action is silent, and stays silent.
Email that does not arrive looks like email that was never sent. Customers read it as being ignored.
Who can reach what, once inherited groups are resolved — which is rarely what the group names suggest.
What is installed, what is abandoned, and what will block your next upgrade.
How far behind you are, and whether the version you run still receives fixes.
Twelve questions, then your score on this page. The paid levels add the diagnostic — which is printed in full below the questions, so you can read it before you run anything.
FAQ
No, and we would rather not have it. The paid levels work from a read-only diagnostic you run yourself and read before sending. We never ask for your Odoo administrator password, a database password or access to your server. There is no access to revoke because none is ever granted.
Counts, versions and statuses: how big the database is, how many users and administrators, how many scheduled actions are overdue, how many emails failed, which modules are installed, whether the base URL is HTTPS. No record contents, no field values, no user names, no email addresses. The whole script is printed on this page so you can check that before running it.
It performs no writes. Every statement is a read, and a test in our own suite fails the build if anything resembling a write appears in it. That said, it is your production system — read it first, and run it on a staging copy if you prefer.
It is reported as not measured, never as a pass. Printing a healthy score next to something nobody looked at would be the one mistake that makes the whole report worthless, because somebody would rely on it.
12 months, so a later check can be compared against it, and then it is deleted. Ask us sooner and we delete it sooner — email info@technovision.dev with the reference.
No. It reads counts and statuses; it does not probe your network, your server or your web application, and it is not a certification. If you want the security half done properly, the Odoo Security Package installs and configures the modules and produces a report an auditor will accept.
Looking for the security side specifically? The Odoo Security Assessment scores twelve questions about visibility against the rules our audit module actually ships, and the Odoo Security Package is the fixed-price version where we do the work.
Most of what this finds has a module behind it that already exists. The rest is quoted as work, against the findings rather than against a guess.