Editions
Antelao has four editions plus an unlicensed state. Two editions cost nothing.
The split is not feature-by-feature. It is by hand versus unattended, and local versus off-site. Running a backup yourself is Community. Letting the scheduler run it every night is Professional. Writing that backup to a local disk or an FTP server is Community; writing it to S3 or Azure is Professional.
What each edition unlocks
| Capability | Unregistered | Community | Developer | Professional | Provider |
|---|---|---|---|---|---|
| PriceCommunity and Developer are free of charge. Support for them is community-driven. | - | Free | Free | Subscription | Subscription |
| InstancesThe limit applies to creating one. What already exists keeps running. | 1 | 2 | Unlimited | 5 | Unlimited |
| Databases per instanceThe limit applies to creating one. What already exists keeps running. | 1 | Unlimited | Unlimited | Unlimited | Unlimited |
| EnvironmentsThe limit applies to creating one. What already exists keeps running. | 1 | 1 | Unlimited | 3 | Unlimited |
| Serving an instance on a public host nameBounds the Developer edition rather than reducing its feature set. | Yes | Yes | No | Yes | Yes |
| Publicly trusted certificatesBounds the Developer edition rather than reducing its feature set. | Yes | Yes | No | Yes | Yes |
| Backup and restoreTaking and restoring instance and database backups. Listing and downloading backups that already exist is never restricted, so an unregistered server can always reach its own data. | No | Yes | Yes | Yes | Yes |
| Sending e-mailSending e-mail through the server's relay: the test message, backup and security notifications, and the licence expiry warning. | No | Yes | Yes | Yes | Yes |
| Banning an address by hand in Fail2BanBanning an address in a jail by hand. Running the Fail2Ban container and the automatic bans it applies are never restricted - intrusion prevention is baseline protection, installed with the server at every edition. Reading the current jails and bans, LIFTING a ban, and removing Fail2Ban altogether stay available too - an unregistered server must never be locked out of its own remedy. | No | Yes | Yes | Yes | Yes |
| The Odoo Enterprise editionInstalling the Odoo Enterprise addons on an instance. Community instances are not affected. | No | Yes | Yes | Yes | Yes |
| Unattended scheduled maintenanceLetting the maintenance scheduler run backups, restores, certificate renewals, PostgreSQL maintenance and image cleanup unattended. Starting any of them by hand needs only the edition that operation itself needs, and the housekeeping schedules that look after the server's own state are never restricted. | No | No | Yes | Yes | Yes |
| The Azure and S3 backup targetsSending backups to Azure Blob Storage or an S3-compatible target. The local and FTP targets are not restricted. | No | No | Yes | Yes | Yes |
Everything on this page is generated from the checks the product actually performs, not from a sales sheet. If a row says an edition allows something, there is a guard in the code that agrees.
Unregistered is a supported state
A server with no licence is not broken. It runs one instance with one database, indefinitely, and never stops on its own.
| Instances | Unregistered | Community | Developer | Professional | Provider |
|---|---|---|---|---|---|
| Limit | 1 | 2 | Unlimited | 5 | Unlimited |
Quotas apply to creating things, never to what already exists. A server holding five instances whose Professional licence lapses keeps all five serving. It simply cannot add a sixth. Taking a customer's running systems down over a billing lapse is not a decision this software makes.
What lapses quietly rather than loudly
Some capabilities do not refuse when you drop below their edition. They run and do less. This is the part a comparison table cannot express, and the part worth knowing before a licence expires unattended at 3am.
| Capability | Below | What happens instead |
|---|---|---|
| The Azure and S3 backup targets | Professional | The backup still runs and still writes its local and FTP copies. Each configured cloud target is skipped and recorded as a failed result for that target, so a licence lapse never means no backup at all. |
| The Azure and S3 backup targets | Professional | Backups held at a cloud provider are omitted from the listing. |
| The Azure and S3 backup targets | Professional | Cloud sources are not offered as restore sources; local and FTP sources still are. |
| Sending e-mail | Community | The sign-in security notification is skipped instead of failing. It runs on the sign-in path, where throwing would lock people out. |
| Unattended scheduled maintenance | Professional | Non-housekeeping schedules are reported as unlicensed and skipped by the scheduler rather than failing the tick. The schedules themselves are untouched and resume when a licence is installed. |
The backup case is the one to understand properly:
A licence lapse therefore never means "no backup". It means the copies that leave your building stop, and each one is recorded as a failed target so the job result tells you.
The Developer edition is bounded, not smaller
Developer unlocks everything Professional does and costs nothing. What keeps it from being a free Professional licence is where it may run, not what it may do.
These two run against the ladder: a public host name works on an unregistered server and is refused on Developer. That is deliberate. Developer is for building and testing on the machine in front of you.
Neither constraint is a security boundary. Anyone willing to edit odoo.json, point DNS at the box
or terminate TLS in front of the product can go around both. They exist to make the paid path the
obvious one.
Installing a licence
Upload the .lic file on the Licence page of the Web UI, or install it from the command line:
prod-1# odoocli server license install ./antelao.lic --server prod-1Licences are signed per product. A licence issued for another Antelao product will be refused rather than accepted at a lower edition.