Free scan of your Odoo. A quote from the counts.

Run the scan file yourself

The scan file is one Python program, allodi_scan.py, that you can read before running. It connects to your Odoo database, reads the settings tables in a read-only session, prints a summary and writes a small result file. It does not start Odoo. It connects only to your PostgreSQL database server. If you leave out --db, it first reads the list of database names on that server, and nothing else, to find yours. It reads settings only from the database it scans, and only that database goes in the result file.

You can download it and run it right away. We ask for your name, company and email when you send the result file. On Odoo Online, upload a backup instead.

On your own server, or a partner's

1. Log in to the server where Odoo runs (or its database server) with SSH.
2. Go to a folder the Odoo user can write to, and download the file:
   cd /tmp
curl -fsSLO https://allodi.us/downloads/allodi_scan.py
3. Run it as the user Odoo runs as:
   sudo -u odoo python3 allodi_scan.py collect
   Use the Odoo user, not postgres. The postgres user is a database superuser and can change anything on the server. If the scan is started with more rights than Odoo's own database user has, it stops and tells you why.
   Without --db, the scan opens one read-only session on the server's built-in postgres database (or template1) and reads the list of database names there, nothing else. If the server has one database, it scans that one and tells you which. If it has several, it lists them and stops, and you run the command again with --db NAME for the one you choose. If there are more than 50, or the list cannot be read, it says so and stops: add --db NAME. It opens no other database. If the database is on another server, add --host and --user. The scan then asks for that user's password (your IT person will know it). If Odoo runs in its own Python environment, use that environment's python instead of python3.
4. It prints the counts and writes a file named like allodi-scan-YOUR_DATABASE-2026-09-25.json. Open it in any text editor if you want to see exactly what it holds.
5. Send the file with the form below, which shows you what it holds before anything goes, or email it to hello@allodi.us.

On Odoo.sh

1. Open your project, choose the production branch, and open the Shell tab.
2. Run:
   curl -fsSLO https://allodi.us/downloads/allodi_scan.py && python3 allodi_scan.py collect
   The Odoo.sh shell already knows the branch's database, so no --db is needed. If it asks which database, add --db with the database name shown on the branch page.
3. Download the result file from the Editor tab (it is in your home folder) and send it with the form below, or email it to hello@allodi.us.

It needs Python 3.8 or later and either the psql program or the Python environment Odoo runs in, which an Odoo server usually has. On a Windows server, get an upload link instead.

Upload a backup: get your upload link by email in a minute

For Odoo Online, or anyone who would rather not run a program. Fill in the form and a personal upload link goes to your email address. It works for 72 hours.

A read-only database login

For IT teams that prefer to let us connect. Your database administrator runs a short script that creates a login called allodi_scan. The database lets that login read only the settings tables, and only a few columns of the users and companies tables, so it cannot see business records, and it has no permission to change any Odoo table. Your administrator lets Allodi's server connect through a restricted SSH account, sends the password through a secure one-time link, and removes the login afterwards. Ask for the script through the contact form.

What you get back, whichever way you choose

The sample report shows all of it for a fictional company.

• A report in plain English: every count, what it means and how it was counted. A model made with Studio counts once, together with the fields, views, access rights and record rules on that model. Fields, views and other items on standard models or on models made by hand, including Studio fields, count one each.
• Your quote, line by line, from the published prices: Managed Odoo, Rescue, Upgrade and Customization cleanup.
• Whether your database can leave Odoo Online now, or what has to happen first.
• What the scan did not count, so nothing is hidden in the quote.
• An appendix with the name of every module and customization it found.

The one-time project fees in the quote are fixed and binding for what the scan counts: modules, Enterprise apps, companies, branches, internal users and customizations. If one of those existed on the scan date and the scan did not count it, that cost is ours. The monthly Managed Odoo fee is an estimate from the counts on the scan date; each month's fee follows the daily counts. The quote uses the published prices on the report date, holds for 30 days and excludes sales tax. What the scan does not count, such as integrations, is listed in the report and agreed with you before work starts.