No brochure voice, no answers that dodge. Where the truthful reply makes us look smaller than the competition, the truthful reply is the one printed here.
Twelve things people ask before they buy, answered the way they would be answered on the phone. Where the honest answer is a weakness, it says so. Every number here is a real setting on the machines running the 16 live databases on the fleet today — pilot, internal and pre-revenue deployments, with no paying reference customer yet — and every one of them is checkable during the 14-day trial rather than taken on trust.
Often it does work, and the fair comparison is not one product against another but your whole stack: the licence, the bolt-ons, the spreadsheets that hold the bits nothing else holds, and the hours spent retyping between them. A trade package is £79 to £249 a month all-in, not per seat. Fourteen days, no card, and you run both side by side before you decide anything.
Sixteen live databases, one operator, and that is the risk you are weighing. If he is ill, new work stops; the system does not. The nightly dump at 02:30 runs, the off-site copy at 03:30 runs, the standby keeps replaying transactions, checks continue every 60 seconds, and routine faults are repaired automatically. What does wait for him is anything the automation does not cover: only a heartbeat and a disk watchdog notify a human today. It is Odoo 19 Community Edition, so any Odoo firm could take the databases over.
There are 16 live databases on the fleet — pilot, internal and pre-revenue deployments — and no paying reference customer yet. There are no logos for two plain reasons: there is no paying customer to name, and nobody has been asked for permission to use their name either. The first ten paying customers pay half for twelve months in exchange for being named. Until those names exist, take the free recoverability review and judge the log rather than the wall.
The repair layer works on infrastructure, not records: it acts on routine failures, re-reads the real state of the machine afterwards, rolls its own change back on any regression, and escalates to a human. Trade AI features are separate, priced per package and documented on their own pages. Ask before switching one on and you will be told exactly which fields leave the database and which never do.
It is, and it is one all-in price for the trade package rather than a per-seat charge that grows every time you hire. The price is frozen for the life of the subscription. Annual billing is ten months for twelve. There are no discounts; if the number is wrong for you the answer is a smaller plan, not a haggle. The first ten founding customers pay half for twelve months.
Most people do, and that is not the question. The question is when a backup was last restored and read by somebody. Here it is a nightly dump, a separate daily off-site copy, point-in-time recovery from write-ahead logs covering the period since 23 July 2026 at 15:03, and a weekly timer that restores a live database backup into a throwaway one. One drill has run so far — 24 July 2026, started by hand — and it passed: 399 tables, about 25,092 rows counted from the restored catalogue, from a 19.2-hour-old backup, in 3.8 seconds. Two things you should know before you rely on any of it: until 24 July 2026 the nightly backup covered the database only, so attachments and uploaded documents were not in it — the fix is deployed and the first backup with documents is the night of 24–25 July 2026 — and the copies for 21, 22 and 23 July 2026 are missing after a disk-full incident.
It is free, and you could have it running this afternoon. Then you configure it for your trade, host it, patch it, back it up, monitor it, and fix it at 03:00 when it breaks. That work is what the monthly price buys. The licence stays Community Edition throughout, so none of what you pay for buys you a cage you then have to be let out of.
The plan limits are printed rather than buried — five fee earners, ten active sites, and so on, depending on the package. Past those numbers you want an implementation team with several people in it, and you should go and get one. Because it is Odoo 19 Community Edition, the exit is a database and a filestore that any Odoo partner can pick up and carry on with.
It is work, and anyone who says otherwise has not seen your data. Start with the free review: send an export and get back the log of what came through clean and what did not. Then choose what goes live and what stays a read-only archive. No date is quoted before the data has been seen, and the trial runs beside your old system rather than replacing it.
No percentage is published, because a number one operator cannot staff is a number you should not be given. Here is the mechanism instead: streaming replication to one standby machine, asynchronous today with synchronous mode in preparation, so work committed in the last seconds before a failure may not have reached the standby; lag alerts at 30 and 120 seconds; checks every 60 seconds, recorded, of which only a heartbeat and a disk watchdog notify a human today; and operator-assisted failover measured in minutes rather than seconds.
You export everything yourself, any time, in standard formats, and a full database dump with the filestore is yours on request. It is Odoo 19 Community Edition, so that dump is a working system anywhere it is restored, not an archive that needs us to read it. Take the export in week one of the trial and satisfy yourself the exit works before you rely on it.
A one-hour setup call, then the trade template configured, then your own data imported wherever an export exists, and finally a written list of what did not import and why. Nothing is promised same-day. Onboarding is one engineer's working days, so the useful question is which week it starts, not which hour it finishes.
Send an export of whatever you run today. It is restored on a throwaway database, read, and then destroyed, and you get the log: what came through clean, what did not, and how old the copy you sent really was. No charge, and no follow-up call unless you ask for one.
Start a trial and check every number on this page yourself, or read the published restore drill first and see how the last one went.