From your first question to a signed start, online and at your pace.
Get your price now, confirm it with the free scan, then read, sign and pay online. No sales call is needed, and we are a phone call away if you want one. Here is every step, how long it usually takes, and what protects you along the way.
Your server and backups are billed to you, not through us. Odoo runs on a server in your own Hetzner account and the backups go to your own Backblaze account. They bill you directly at their prices (usually about $40 to $75 a month for the server and a few dollars for backups), and we add no markup. If you ever leave, nothing has to move: your system keeps running exactly as it is, except that Allodi Print goes back to Odoo's standard PDF download, and our fee stops at the end of the 30-day notice period.
Or call us: +1 515-644-1400, any time.
Step by step, to a signed start
The same path for every service. You can stop after any step, and nothing is charged before you sign.
-
Get your price today
Enter your companies, branches and internal users in the price calculator, or let your own module list fill in the upgrade counts with the module list quote. Plans, add-ons and hourly rates are published, and what you enter stays in your browser until you choose to send it. This step is optional, and you see your price without giving a name or an email.
-
Run the free scan today, at your pace
The free read-only scan confirms the counts: download the scan file and run it yourself, or upload a backup through a personal link that reaches your inbox in about a minute. You give your contact details when you send the result file or ask for the upload link.
-
Your quote usually one business day after the scan
A person at Allodi checks the report and sends your quote, line by line from the published prices. Its one-time project fees are binding for what the scan counts: if the scan missed a module, Enterprise app, company, branch, internal user or customization that existed on the scan date, that cost is ours. The monthly Managed Odoo fee is an estimate that follows the daily counts. The quote holds for 30 days.
-
Read, sign and pay online when you are ready
The quote email opens a page with your quote, the payment schedule and every contract document, each with its version: the master services agreement, your statement of work, the Managed Odoo service description, the acceptable use policy, the portal terms and the privacy notice, plus the data processing agreement for EU/EEA, UK and Swiss customers. You sign on the page and pay the first payment only, by card up to $2,500 including tax, or by ACH bank debit or wire. Where your quote says so, you sign now and pay a 15-day invoice by bank transfer instead.
-
Welcome aboard once signed, with any payment due at signing made or under way
One welcome email with copies of what you signed, your first invoice, a link to set your support portal password, and your onboarding ticket with the next steps. Your personal secure links are emailed to the person who signed. It is sent once you have signed and the first payment is made, or started by ACH or wire. On a quote you sign now and pay by invoice, it is sent once you have signed.
A question first? Writing to us is optional
"Send me this estimate", under your price, opens the contact form with your counts filled in; you add your name, company, email and country. We usually reply within one business day, US Central time, with the next step for your case or a few questions. A call is there if you want one, not a required step. Sending your numbers is optional: you can go straight to the free scan.
What you need to start
-
Your countsCompanies, branches and internal users. Portal users are free. Your version is at the bottom of Odoo's Settings page.
-
For the scanAccess to run one read-only program where Odoo runs, or a backup download. On Odoo Online, the backup is the way.
-
To signSomeone authorized to sign for your company, and a card or bank account for the first payment.
-
For onboardingA shared company mailbox for the new accounts, a company card for Hetzner and Backblaze, an administrator login to your current Odoo, a list of the outside services it is connected to (payments, shipping, bank feeds, tax, email), and whoever can change your DNS.
Your first weeks on a move
For a move off Odoo Online, Odoo.sh or a partner's server. A small move can be done in two weeks, a large one takes up to six. Your part is about an hour in total, spread over the first week, and screen-sharing through any step is part of the service.
-
Kickoff days 1 to 3
The kickoff is your welcome email and your onboarding ticket. The ticket lists the next steps. Tell us there or by email who on your side can create accounts and change DNS. Your personal secure links are emailed to the person who signed the order. Your onboarding ticket shows when they were sent. They are one-time links for your Hetzner API token, your Backblaze master key (used once) and an administrator login to your current Odoo. Passwords and keys travel only through those links. Your written project plan follows within 10 business days of getting access, as your statement of work sets out. A call is there if you want one, not a required step.
-
Your accounts week 1
You open a Hetzner Cloud project in your company's name and send us an API token for it through a secure link (about 20 minutes), and open Backblaze B2 for your backups and send a master key once through a secure link (about 15 minutes); we use it to create your private bucket and its keys, and you then cancel it. Then you upload a full backup of your current Odoo, database and attachments, to your new bucket. You also send an administrator login to your current Odoo through its secure link, and a short list of the outside services Odoo is connected to. Step-by-step guides come with your welcome email.
-
A safe copy week 1 or 2
The build starts by itself once your token, your keys and your backup have arrived, the checks pass and your first payment is in. Your server is built from a script, the nightly backup to your bucket starts, and a test copy is restored with email, scheduled jobs and payment connections switched off, so a test never reaches a customer. Your onboarding ticket tells you when it is ready.
-
Testing one to four weeks, by size
Mail, your web address and your integrations are set up. Two or three of your people use the test copy for real work and tell us anything that looks different. Your current Odoo keeps running as it is.
-
Cutover one evening you pick
Users pause, we take a final backup from the old system, restore it on the new server, switch DNS and mail, and run a go/no-go checklist. Then everyone logs in at the new address.
-
Handover within 30 days of cutover
The runbook, the credentials list, the integrations list and a backup test report. You keep the old system available and unchanged for at least 30 days after cutover as a fallback, as your statement of work sets out; after that, switching it off is your decision.
Where are we? The stages your onboarding ticket shows
On a move, your onboarding ticket in the support portal shows each stage as it is reached. If something needs your attention, the ticket explains what and why.
Secure links sent. Your personal secure links were emailed to the person who signed the order: for your Hetzner API token and project name, your Backblaze master key, and an administrator login to your current Odoo. On your own hardware there is no Hetzner link. The ticket shows when and to whom they were sent, and the bucket and folder names to use.
Keys received. Your Hetzner token has arrived, and your backup bucket and its two limited keys are set up. The ticket then asks you to make a new Backblaze master key, which cancels the one you sent.
Backup found. We have found the full backup of your current Odoo that you uploaded to your bucket.
Checks passed. The checks run by themselves: the Hetzner token works, the bucket and the two limited keys we made with your master key are in place (private bucket, cleanup rule, keys that cannot delete), and your backup can be read. If a check does not pass, the ticket says which one and what to do.
Server built. Your server is built from a script, with the nightly backup to your bucket set up. This starts by itself once the checks pass and your first payment is in.
Test copy ready. Your backup is restored as a test copy with email, scheduled jobs and payment connections switched off, so a test never reaches a customer. You log in with your usual login and password: your users and their passwords came with the copy. The main administrator account gets a new password made for the test copy; ask in the ticket and we set a password for it, or for any login that does not work.
On an upgrade, the test copy is a first automatic conversion of your data to Odoo 19, so you can look around early. The planned steps in your statement of work still follow: the plan, your approval and the staging rehearsal.
Most moves take two to six weeks from signing, depending on size, most of it the testing on the copy; a partner who is slow to release your code or backup stretches the first week. Managed Odoo is billed from cutover, or from an agreed urgent move onto our interim servers; before that you pay only for the move. Read the migration caveats before you plan the date.
Managed Odoo only, on a server you already own
The monthly subscription starts when you sign and is billed on that day of each month, with no proration. The onboarding ticket lists the access we need, and monitoring, backups to your own bucket and a mail check follow from there.
An upgrade or a cleanup
Rehearsed on copies before production is touched. An upgrade usually takes four to twelve weeks depending on the number of custom modules, a cleanup two to six weeks. Both are billed 30% at start, 40% at staging sign-off and 30% at completion, and neither needs a Managed Odoo subscription (upgrade, then go).
Upgrade, then go
Use us to get to Odoo 19, or to Odoo 19 Community with no Enterprise license, and then be gone. The upgrade and the move from Enterprise to Community are one-off projects under a statement of work, and neither needs a Managed Odoo subscription.
-
A fixed, published price
Set by the free scan's counts, by custom modules to port, none: $0, 1 to 5: $750, 6 to 15: $2,000, 16 to 40: $4,500, over 40: $4,500 plus $100 per module over 40; plus $500 per major version jumped and $250 per Enterprise app replaced. Billed 30% at start, 40% at staging sign-off and 30% at completion.
-
Rehearsed, then one night on production
The upgrade runs on copies until it is clean, your team signs off on a staging copy, and production is upgraded on a scheduled night with a rollback point.
-
Handover at acceptance
The credentials we created, stored where you control them, a backup test report from your own bucket, the runbook, the integrations sheet and a summary of who has access to what.
-
Two weeks of fixes, then we step away
Defects you report in the portal within 14 days of acceptance are fixed at no charge. At the end of those 14 days we remove our access to your Hetzner project, servers, repository and backups and confirm it in writing, unless you ask us to keep it, and we delete our project copies of your data within 30 days.
What stays with you
Your server. When we set it up on your company's Hetzner account, the backups go to your own Backblaze bucket and the backup job keeps running without us. Every ported or new module in your repository with full source, licensed to you under LGPL-3, so you can use, change and share it without paying us again. From acceptance, backups, monitoring, patching and running the server are yours, or whoever you choose.
Worth knowing first
A hosting move is a separate project: if your Odoo is on Odoo Online or Odoo.sh today, the move to your own server comes before or after the upgrade, never in the same night, and it too needs no subscription. On a move from Enterprise, you decide when to end the Enterprise subscription; we suggest keeping it until the two weeks of fixes are over. Hetzner and Backblaze bill you directly, with no markup from us.
What protects you, in writing
Each of these is in the contract documents you read before you sign. The section numbers say where.
-
If the move fails, the start payment comes back
If we cannot get your database running on the new server (or on our interim servers), with all modules loading and the data integrity checks passing, the start milestone for that database is refunded in full, and either side can then end that project with nothing more owed for that database. The refund does not apply where the failure is caused by something your statement of work asks of you not being provided, by your withdrawal of our access, or by a third party's refusal to release your data when you ask for it.
Statement of work, section 11A
-
Month to month
Managed Odoo has no minimum term. Either side can end it with thirty days' written notice.
Master services agreement, section 8.2
-
Everything is in your name
You own your data and the environment it runs in: the Hetzner project, the servers, the code repository and the backup bucket. Custom modules we write are delivered to your repository with full source and licensed to you under LGPL-3.
Master services agreement, sections 4.1, 4.3, 9.1 and 9.3
-
Leaving is written down
When you leave Managed Odoo, within ten business days and at no charge, we take a final backup to your bucket, hand over the credentials and configuration we created, the source of your custom modules and the runbook, remove our own access and confirm it in writing.
Master services agreement, section 8.5
-
An upgrade does not tie you to us
An upgrade or de-Enterprise project needs no subscription. At acceptance you get the handover package, defects you report within 14 days are fixed at no charge, and then we remove our access and confirm it in writing unless you ask us to keep it. Your Odoo keeps running if our access is removed.
Statement of work, sections 13.4, 14.1, 16.2, 16.3 and 16.5
-
Response times in writing
On Managed Odoo, a server that is down or data at risk gets a response within one business hour, a core function broken for several people within one business day, and everything else within three business days. With the 24/7 outage response add-on, the first target becomes one hour at any time, day or night, including by a call to your own direct emergency line.
Managed Odoo service description, sections 7.2 and 7.6
-
Billed on counts you can check
Companies, branches and internal users are counted automatically every day. Each monthly invoice is billed on the highest daily count in the billing period and lists those counts next to the prices, and the monthly summary shows each day's counts.
Managed Odoo service description, section 11.2a
-
Fix hours from your tickets, and they carry forward
Included hours used are taken from the time logged on your tickets, which you can see in the portal. Time on an incident caused by our own error is not counted. Hours you do not use carry forward one month, then lapse; they have no cash value.
Managed Odoo service description, sections 6.2a and 6.4
-
Backups you can go back to
30 daily backups in your own Backblaze bucket, point-in-time recovery to a moment you choose within the last 29 days, a monthly test restore, and a staging copy of production on servers with 8 GB of memory or more.
Managed Odoo service description, sections 4.1, 4.1a, 4.3 and 4.7
-
No markup on hosting
Hetzner and Backblaze bill you directly, under your own accounts, at their prices. We add no markup; only interim hosting on our servers, when you ask for it, is passed through at cost.
Statement of work, section 8.4; master services agreement, sections 4.4 and 4.8
-
The quote holds
The fixed fees in your statement of work are binding on us. If the work turns up a module, Enterprise app, company, branch, internal user or customization that existed on the scan date and the scan missed it, that cost is ours.
Statement of work, section 11.3
-
Rehearsed on a copy first
Moves, upgrades and cleanups are rehearsed on a copy with outgoing email, scheduled jobs and payment connections switched off. Changes outside a short list of pre-approved routine actions need approval from a named person at Allodi, and so, always, does anything that deploys code, touches money, tax, user access or security settings, sends messages from your Odoo, or migrates or restores production.
Master services agreement, sections 5.3 and 5.4; how it works
Read the contracts
The current contract set is version 2026-10-24.1, dated October 24, 2026. These are the documents your quote links to when you sign. Your statement of work is written for your project and comes with your quote.
| Document | Version | Size |
|---|---|---|
| Master Services Agreement | 2026-10-24.1 | PDF, 15 pages |
| Managed Odoo Service Description and SLA | 2026-10-24.1 | PDF, 9 pages |
| Acceptable Use Policy | 2026-10-24.1 | PDF, 3 pages |
| Support Portal Terms of Service | 2026-10-24.1 | PDF, 4 pages |
| Data Processing Agreement | 2026-10-24.1 | PDF, 9 pages |
| Privacy Notice | 2026-10-24.1 | PDF, 5 pages |
Who you are dealing with
Allodi is a product of KEIGHT LLC, based in Des Moines, Iowa. It was started inside an Iowa manufacturer that runs on Odoo 18, on infrastructure it manages itself, with custom modules and outside integrations, and is moving to Odoo 19 Community: the same project we sell. Before that, Mark and Lisa Kladivo ran pcCentral, a desktop hosting company, for fifteen years, with more than 5,000 users, until it was sold in 2018.
Changes to a customer's system outside a short list of pre-approved routine actions need approval from a named person at Allodi, and so, always, does anything that deploys code, touches money, tax, user access or security settings, sends messages from your Odoo, or migrates or restores production. AI agents do the legwork under that review, and every action taken through the support portal is logged. Everything is set up so that your Odoo does not depend on us (what happens if we are unavailable).
Allodi
-
Phone+1 515-644-1400, any time
-
Emailhello@allodi.us
-
CompanyAllodi is a product of KEIGHT LLC, 109 SE 4th Street, Des Moines, IA 50309
-
See it firstAsk the agent about a sample company in the live demo, or open your own private copy of it.
Questions people ask before they start
Do we need a sales call?
No. Plans, add-ons and hourly rates are published, the free scan confirms the counts, and the quote, the contract documents, the signature and the first payment are all online. You can call us at +1 515-644-1400 if you would rather talk it through.
What happens if Allodi is unavailable?
Your Odoo keeps running without us. The server is in your company's own hosting account, the code is in a repository you control, the nightly backups go to a Backblaze bucket in your own account and keep running for as long as you keep that account and the backup job in place, the credentials we create are recorded where you can reach them, and the runbook explains how it all fits together. What stops is our work: monitoring, patching, restore tests and support, and Allodi Print, which goes back to Odoo's standard PDF download. Another Odoo partner or your own IT team can take over from the runbook with the access you give them. Managed Odoo is month to month with thirty days' notice either way, and when a subscription ends we hand over a final backup, the credentials we created, the source of your custom modules and the runbook, and remove our own access, within ten business days and at no charge (MSA 8.2 and 8.5).
What if the move does not work?
Every step before production happens on a copy, and your current system keeps running until cutover. If we cannot get your database running on the new server, with all modules loading and the data checks passing, the start milestone is refunded and either side can end that project with nothing more owed for that database. The refund does not apply where the failure is caused by access, data or code you were asked for not being provided, by withdrawing our access, or by a third party refusing to release your data.
How much downtime is there?
Users stop for the cutover only: one evening you pick, or a weekend for a large database, while a final backup is taken, restored on the new server, and the domain and mail are switched. Testing before that happens on a copy, and your team keeps working in the current system as normal.
Who owns our data and code?
Your company owns the data and the environment it runs in: the database runs on a server in your own Hetzner account, and backups go to your own Backblaze bucket. Custom modules we write are delivered to your repository with full source and licensed to you under LGPL-3, the license of Odoo Community, so you can use, change and share them without paying us again; we keep the copyright. We work through access you grant and can withdraw at any time, such as an API token you can delete.
How is our system kept secure?
Access is by named individual accounts with multi-factor authentication and SSH keys, and it is logged. We ask for passwords and keys only through one-time secure links. The AI agent runs on infrastructure we control and reads your system in place. Only what a ticket needs, such as a record or an error message, is sent to the model provider, Anthropic, and full database dumps are not sent to it. Anything that deploys code, touches money, tax, user access or security settings, sends messages from your Odoo, or migrates or restores production needs approval from a named person at Allodi. The privacy note and how it works have the details.
How long is the contract?
Managed Odoo is month to month with no minimum term; either side can end it with thirty days' written notice. Projects such as a move or an upgrade are billed in milestones as they are reached, and they do not need a Managed Odoo subscription. On the way out, within ten business days and at no charge, we hand over a final backup and the credentials we created for your system, and remove our own access.
Can we just use you for the upgrade and leave?
Yes. An upgrade to Odoo 19, or a move from Enterprise to Odoo 19 Community with no Enterprise license, is a one-off project at the published fixed price, and it does not need a Managed Odoo subscription. At acceptance you get the handover: the credentials we created, a backup test report, the runbook, the integrations sheet and who has access to what. Defects you report in the portal within 14 days are fixed at no charge. Then we remove our access to your server, repository and backups and confirm it in writing, unless you ask us to keep it. The code stays in your repository under LGPL-3 and the server and backups stay in your company's name, so your Odoo keeps running without us.
What are your support hours?
You can call the main number any time, day or night. Tickets and email are answered on business days. On Managed Odoo, a server that is down or data at risk gets a response within one business hour. With the optional 24/7 outage response add-on, that is within one hour at any time, day or night, including by a call to your own direct emergency line. Monitoring runs day and night and opens a ticket by itself; without the add-on, outside business hours we respond as soon as we can, without a time promise. The response targets are on the services page.
How do we pay?
The first payment is usually made online when you sign: by card for amounts up to $2,500 including tax, or by ACH bank debit or wire transfer for any amount. Each later invoice is due 15 days after its date. On a quote you sign now and pay by invoice, the first invoice is also due 15 days after its date. Customers outside the US pay by international wire in US dollars. Prices are plus Iowa sales tax where it applies. In Europe we sell to VAT-registered businesses only: the quote needs your VAT number, and no VAT is charged (reverse charge).
Can we start today?
Yes. Get your price in the calculator now, and run the scan file or ask for an upload link today; the link reaches your inbox in about a minute. We usually reply within one business day, and once you have signed and any payment due at signing is made or under way, onboarding begins with your welcome email.
Why not host Odoo ourselves?
You can, and the runbook we hand over is written so that you could. Managed Odoo adds the watching and the fixing: monitoring, patching, nightly backups with a monthly restore test, failed-mail alerts and small-fix hours every month. If your own staff already do that, running it yourselves costs less. The cost comparison works through the numbers.
How is Allodi different from Odoo.sh or an Odoo partner?
Odoo.sh is a hosting platform: for hosting a small database it is often cheaper, and the work on your system stays with you or your partner. Allodi is independent of Odoo's partner program and works on systems that are already running: it moves, hosts, supports and upgrades them, publishes every price, and keeps the server, code and backups in your name. For a first-time implementation, a full-service partner is the better fit, and we are glad to recommend one.
Start with your price
Enter your companies and users and your price is on screen. Send it to us from the same page, or start the free scan today.
Or call us: +1 515-644-1400, any time.