Which option costs less to run, and what Odoo vs Dolibarr pricing depends on
A small or mid-sized business comparing these two should start with the fact that Dolibarr has no license fee to self-host, since it is free open source software under the GPL. Its running costs are therefore hosting, setup and staff time. DoliCloud, which hosts Dolibarr as SaaS, publishes a Basic plan at 14 euros per user per month and a Premium plan from 45 euros per month, each with a 30-day free trial. Odoo prices by user and ties its hosting options to plans. The pricing page places on-premise and Odoo.sh hosting under the Custom plan, which also includes multi-company, Studio, external API access and custom modules, so confirm whether that rule applies to your edition and deployment before modeling a budget. Check current per-user figures on the Odoo pricing page.
The answer turns on four variables. The first is user count, because DoliCloud Basic and Odoo's per-user plans both scale with seats, while a self-hosted Dolibarr install carries no seat charge. The second is hosting route: a Dolibarr server, Docker host or DoliCloud subscription, or an Odoo deployment on your own servers, Odoo.sh or cloud account, each carry different infrastructure, backup and patching duties. The third is apps. Odoo lists Studio, Documents, Sign, Payroll and Quality among Enterprise-only features, so the apps you need determine whether the license line is zero or recurring. Dolibarr's modules are free to enable, but any paid add-ons from its DoliStore marketplace should be confirmed with each publisher. The fourth is who does the work: your own staff, or a fixed-scope implementation partner.
Before comparing totals, split each option into one-time and recurring costs. For Dolibarr, recurring costs usually include hosting, backups, patching and any support contract, while installation, module configuration and data migration are one-time. For Odoo, subscription fees, hosting and Enterprise support recur, and implementation is typically one-time. Ask each vendor or partner for a written quote that states the user count, hosting route, apps and support level, then model at least two user counts using the figures you have confirmed. Ask any implementation partner for a fixed-scope proposal covering upgrades, backups and testing, because Odoo's upgrade service requires an Enterprise subscription, and Dolibarr upgrades will need your own test plan. DeployOpen agrees scope, deliverables and timelines in writing before work starts. The broader feature and fit comparison sits in the overall Odoo vs Dolibarr comparison on this site.
Pricing components for Odoo and Dolibarr side by side
This table breaks total cost of ownership into licence, hosting, implementation, add-ons, upgrades and support for each platform. Read each row as a question to answer in a quote: some costs are published as list prices, others depend entirely on the written scope and the environment you choose.
| Cost component | Odoo | Dolibarr |
|---|---|---|
| Software licence | Community is LGPL-3.0 and free to download. Enterprise requires a paid subscription matching your user count, under the Odoo Enterprise Edition License v1.0. | Free open source under GPL-3.0. No per-user licence fee applies to the core application. |
| Subscription plans | One App Free (one app, unlimited users, Odoo Online only), Standard (all apps, Odoo Online only) and Custom, all priced per user per month with a yearly discount. Confirm current figures on the Odoo pricing page. | DoliCloud publishes a Basic plan at 14 euros per user per month and a Premium plan from 45 euros per month, each with a 30-day free trial. Self-hosted Dolibarr has no subscription. |
| Hosting route and plan requirement | Only the Custom plan can be hosted on Odoo.sh or on-premise. Odoo Online is available on all three plans. Ask whether the quote assumes Custom for your hosting choice. | Self-hosted on your servers, virtual machines, Docker or a partner. DoliCloud is the vendor-preferred SaaS option. Ask which hosting route the quote covers. |
| Enterprise subscription for on-premise use | On-premise use of Enterprise requires a valid subscription, activated by entering the subscription code. Confirm whether the Custom plan price or a separate on-premise subscription applies to your user count. | Not applicable. No Enterprise tier exists to license. Modules are enabled within the single application. |
| Add-ons and extensions | Enterprise apps such as Studio, Documents, Sign, Payroll, PLM, Quality and Field Service are listed as Enterprise-only. Custom modules are included in the Custom plan. Ask which apps are priced separately. | Modules are included in the core install. Extensions are available through the DoliStore add-on marketplace, where third-party pricing varies. Confirm each add-on's licence and cost before scoping. |
| Implementation and customization | Fixed-scope work is quoted from written scope, covering installation, configuration, data migration and custom modules. Effort depends on the number of apps and custom code. No public price is supplied. | Fixed-scope work is quoted from written scope, covering installation, module configuration and any Module Builder or PHP changes. No public price is supplied. |
| Upgrades and version support | Standard support covers three years after a major release. Major upgrades are mandatory every two years on Odoo Online and Odoo.sh. The upgrade service requires an Enterprise subscription. Ask whether upgrade testing is in scope. | Upgrades are handled by your team or a provider on the version you run. Older lines such as 23.0 and 22.0 received maintenance releases in 2026. Ask what maintenance window the quote assumes. |
| Ongoing support | Standard support includes security updates and bug fixes. Unlimited functional support is listed as Enterprise-only. Paid extended support applies to on-premise and select Odoo.sh versions. Ask what your subscription covers. | Community support comes from the Dolibarr Association and its ecosystem. Paid support is a separate contract with a provider. Ask for response commitments in writing. |
How Odoo's plans map to hosting routes
The hosting route you want determines which Odoo plan you must buy, and that decision sets most of the recurring Odoo bill before any add-on is considered. Odoo's pricing page lists three plans: One App Free (one app, unlimited users, Odoo Online only), Standard (all apps, Odoo Online only) and Custom. Only the Custom plan can be hosted on Odoo.sh or on-premise. If your team plans to run Odoo on its own servers or in its own cloud accounts, the Standard plan is not an option, and the Custom plan is the only Odoo subscription route to compare against Dolibarr's self-hosted cost.
Custom is also the only plan that includes multi-company, Odoo Studio, external API access and custom modules. Those four items matter for a Dolibarr comparison because they are the features teams most often assume come with a cheap subscription. Enterprise apps such as Studio, Documents, Sign, Payroll and Quality are listed only for Enterprise, so confirm with Odoo which of your needed apps fall under that edition before you assume they are covered by the plan price. Ask the vendor to put each app and each plan in writing on one quote, so you can see exactly which features your entity count and integrations depend on.
Per-user prices and the yearly discount come from Odoo's pricing page and can change, so check them there at the time of purchase rather than relying on figures from older articles or this page. Ask for the per-user rate, whether it is billed monthly or yearly, how the user count is defined for your org chart, and whether the Custom plan's hosting fees appear as a separate line. Those answers, together with the DeployOpen written scope for your implementation, give you a complete cost picture to set against Dolibarr's hosting options.
What each route costs to run for Odoo and Dolibarr
Dolibarr is free under the GPL, so the recurring cost of a self-hosted install is infrastructure and the people who run it. The Dolibarr prerequisites page estimates about 150 MB for program files and 35 MB for an initial database, plus space for uploaded and generated documents, and recommends at least a 1 GHz CPU for 30 or more users. Treat those figures as a starting point and let load testing and document growth set your real sizing.
- Server or virtual machine: Paid to your hosting provider or data center. It recurs if rented and is one-time if bought, and storage rises as uploaded documents accumulate.
- Database engine: MySQL 5.7.7 or newer, MariaDB 10.3 or newer, or PostgreSQL 9.1.0 or newer. Using an engine your team already operates keeps staff costs down, but backups and restore tests still need time.
- Internal administration: Patching the PHP stack, applying maintenance releases, and managing modules, backups and accounts. For most teams this is the largest cost, and it is paid as staff time.
- Optional implementation services: One-time fees if you hire a partner for configuration, data migration or custom modules. Quote these from a written scope.
Check whether a quote covers installation, backup design and upgrade testing, and who maintains add-on modules after go-live.
Self-hosted Odoo on your own servers requires the Custom plan on Odoo's pricing page. Odoo's licenses documentation also states that the Enterprise edition requires a valid Enterprise subscription matching your user count. Community is free under LGPL-3.0, but it does not include Enterprise apps, the upgrade service or the mobile apps, so most on-premise budgets start with the subscription.
- Enterprise subscription: A recurring per-user line matched to your user count. Odoo's pricing page shows per-user monthly prices with a yearly discount, so confirm current figures there before budgeting.
- Custom plan: Required for on-premise use. It is also the only plan that includes multi-company, Odoo Studio, external API access and custom modules.
- Servers and database: Odoo 19 requires Python 3.10 or later and PostgreSQL 13 or later. You provision, monitor and back up these systems, and the costs are paid to your provider or your staff.
- Extended support: Standard support covers three years after a major release. Paid extended support is available for on-premise afterwards, so ask for its price and end date in writing.
- Upgrades and custom code: The upgrade service requires an Enterprise subscription on-premise. Custom modules must be re-tested at each major version, which adds recurring effort.
Ask the vendor or partner to price the subscription, the Custom plan and extended support as separate lines so you can see which costs recur.
DoliCloud, which describes itself as the official Dolibarr preferred partner, hosts Dolibarr as SaaS. Its published plans are a Basic plan at 14 euros per user per month and a Premium plan from 45 euros per month, each with a 30-day free trial. The subscription removes most server and patching work, but configuration, data migration and custom module work remain separate costs.
- Basic plan: 14 euros per user per month, so the monthly total grows with headcount.
- Premium plan: From 45 euros per month, which is a starting figure. Confirm the users, storage and modules it includes before comparing it with Basic at your size.
- Free trial: The 30-day trial lets you test data migration and daily workflows before you commit to a paid plan.
- Services you still pay for: Configuration, data migration and any custom work are usually contracted separately from the subscription, and are one-time costs unless you add ongoing support.
- Exit cost: Moving data and documents out later takes effort. Confirm the export format and any fees in writing before signing.
Compare the Basic per-user total at your headcount with the Premium starting price, and confirm storage limits and export terms before you sign.
Odoo's hosted routes differ mainly in plan requirements. Odoo Online is offered on One App Free, Standard and Custom plans, while Odoo.sh can be used only on the Custom plan. Odoo's pricing page bills these routes through per-user monthly prices with a yearly discount, so you pay for hosting through the subscription line, and you should confirm with Odoo whether any Odoo.sh charges appear separately.
- One App Free: One app, unlimited users and Odoo Online only. It suits a narrow trial, but it is not a route for custom modules.
- Standard plan: All apps on Odoo Online only, billed per user per month.
- Custom plan on Odoo.sh: Required for Odoo.sh, which provides custom modules and Odoo-managed branches. Ask whether any hosting fees sit outside the plan price.
- Upgrade effort: Major version upgrades are mandatory every two years on Odoo Online and Odoo.sh. Testing the upgraded test database before production is staff or partner time that recurs.
- Support windows: Standard support covers three years on Odoo Online, Odoo.sh and on-premise. Paid extended support is limited to Odoo.sh for select versions and on-premise, and security patches arrive only during standard support.
Confirm which upgrade testing and extended support costs are in your scope before comparing these routes with self-hosting.
Factors that move the total cost of Odoo and Dolibarr
Odoo and Dolibarr differ less in their license fees than in what surrounds them: how many people use the system, which apps or modules you switch on, and how much custom code you carry into each upgrade. The cards below explain when each factor starts to dominate the total and what to ask for before you compare quotes.
User count and per-user billing
Odoo's paid plans are priced per user per month, so headcount multiplies the subscription line directly, and the yearly discount changes the figure you compare. Dolibarr self-hosted carries no license fee at any user count, so its costs stay with hosting and staff time. If you run Odoo on-premise or on Odoo.sh, confirm with Odoo whether the Custom plan price is quoted per user and whether read-only or occasional users are billed differently. Ask for the monthly and yearly totals at your current and projected headcount.
Number of apps or modules enabled
Odoo's Standard plan includes all apps but is limited to Odoo Online, while on-premise use requires the Custom plan. Enterprise-only apps such as Studio, Documents, Sign, Payroll and Quality add cost on top of the base subscription, so the app list is a pricing decision. Dolibarr lets you enable only the modules you need, and its core modules are part of the free GPL application. Map your required processes to specific apps or modules before requesting quotes, because the feature list is what moves the total.
Custom code and upgrade effort
Custom modules are the cost that recurs most often. On Odoo, Studio and custom modules are only included in the Custom plan, and Odoo's upgrade service is available only to Enterprise subscribers on-premise. Every major version change requires testing custom code against an upgraded test database before production. On Dolibarr, the Module Builder and custom PHP modules carry the same maintenance question. Ask each vendor or partner who will maintain custom code between major releases and how that work is scoped in a fixed-scope engagement.
Extended support windows for on-premise and Odoo.sh
Odoo provides standard support for three years after a major release, including security updates and bug fixes, and paid extended support afterwards only for on-premise and selected Odoo.sh versions. Security updates stop after standard support ends, so a version you keep running beyond that window is a risk decision as well as a cost. Odoo 20.0 standard support is planned until September 2029, and Odoo 19.0 until September 2028. Compare this against your planned upgrade cadence, and ask Odoo for the extended support price for your target version.
Extension marketplace purchases
Dolibarr is extended through the DoliStore add-on marketplace, so functions that are not in the core application can add a separate purchase and its own maintenance. Each add-on may have its own license, vendor and compatibility with new Dolibarr releases, which affects upgrade testing. Odoo add-ons from third parties and the Odoo Community Association modules carry the same question. Before you commit, list each extension, its license, its maintainer and the Dolibarr or Odoo version it supports, and ask whether the vendor commits to updates for your target release.
Internal staff time and support
Self-hosting moves much of the cost to your own people: patching, backups, monitoring, user administration and vendor coordination. Odoo Enterprise includes support and version upgrades, which can reduce internal effort but adds a subscription line, while a Dolibarr deployment depends on support from the Dolibarr Association, a partner or your own team. Estimate how many internal hours each month you can actually allocate, and ask a provider to separate one-time implementation work from recurring support in the written scope so the two are not mixed in one number.
Upgrade and support costs over the life of the system
Upgrade labour and testing are recurring costs on both platforms, and they should be quoted as their own line rather than folded into the license or hosting figure. On Odoo, the main driver is the support window. Odoo's standard support covers three years after a major release, including security updates and bug fixes, and security updates are only provided during that standard window. Odoo 20 was released in September 2026 with standard support planned until September 2029, so a Custom plan deployment on Odoo 19 (September 2025) should be planned for a move to a newer version well before its standard support ends in September 2028. Paid extended support exists only for on-premise and selected Odoo.sh versions, and Odoo SaaS versions cannot use it.
On Odoo Online and Odoo.sh, major upgrades are mandatory every two years, so the schedule is set by the vendor rather than by your own change calendar. On on-premise deployments you control timing, but the upgrade service requires an Enterprise subscription, and the Community edition has no access to it. Ask the implementation partner to quote the upgrade test cycle for each major version, including the upgraded test database that Odoo recommends testing before production, custom module compatibility work, and data validation sign-off. Ask whether extended support is included or priced separately for your chosen hosting route.
On Dolibarr, the cost pattern is different because the GPL release line does not force a platform-level migration on a fixed calendar. Dolibarr 24.0.0 (August 20, 2026) and 24.0.1 (September 7, 2026) are the current releases, and older lines such as 23.0 and 22.0 still received maintenance releases in 2026. That gives you room to schedule upgrades around your own change windows. The trade-off is that there is no vendor upgrade service to buy, so the work of testing, patching and upgrading your modules and DoliStore add-ons sits with your team or your partner. Confirm with the Dolibarr Association or your partner how long each line receives maintenance before you rely on it for a multi-year plan, and check whether any installed third-party module is maintained for the target version.
How to build a true cost model for your own environment
This sequence turns the published plan prices and open-source terms into a three-year cost model that reflects your users, hosting choices and customization needs. The output is a comparable set of written quotes and internal effort estimates for Odoo and Dolibarr.
Inventory users, apps and data volumes
Start by listing every person who will log in, grouped by role, and every business area you expect to run in the ERP, such as sales, invoicing, stock, manufacturing, HR and point of sale. Note which areas need multi-company support, external API access or custom workflows, because those needs decide which Odoo plan and which Dolibarr modules you price. Record expected growth in users and the size of documents you will store. The step is complete when a single sheet maps each role to the apps it uses and each app to a named owner.
Choose the hosting route for each option
For Odoo, decide between Odoo Online, Odoo.sh and self-hosted on-premise, because the pricing page ties Odoo.sh and on-premise hosting to the Custom plan. For Dolibarr, decide between self-hosting on your own machines or Docker and a SaaS route through DoliCloud or another hosting partner. Document who will operate the servers, where backups go and which data residency rules apply. The step is complete when each option has one named hosting route and a short note on who carries the operating responsibility.
Request written quotes from each vendor and host
Ask Odoo for a quote that matches the plan, user count and apps on your inventory, and confirm in writing which plan terms apply, including any yearly discount. For Dolibarr, obtain the DoliCloud plan terms for your user count, or written quotes from the hosting partners you shortlist. Ask each provider to state what is included, what is billed separately and what recurs. Confirm current prices and plan terms on the vendor sites before you decide, since these change. The step is complete when every quote is in writing, covers the same users and apps, and is dated.
Price implementation from a fixed written scope
Write a scope that lists the modules to configure, the data to migrate, the integrations to build and the training to deliver, then ask implementation partners to quote against that scope for both platforms. Fixed-scope quotes make the two options comparable and show what is one-time. Ask each partner to separate configuration, data migration, testing and go-live support into distinct line items. The step is complete when both implementation quotes reference the same written scope and list their assumptions.
Model add-ons and custom modules
List every paid feature and extension you expect to need. For Odoo, check which capabilities sit in the Enterprise edition or the Custom plan, such as Studio, Documents, Sign, Payroll or custom modules. For Dolibarr, check which needed functions are core modules and which come from the DoliStore marketplace or require custom development with the Module Builder. Estimate who builds, tests and maintains each extension, and whether its cost recurs. The step is complete when every add-on has a source, an owner and a one-time or recurring label.
Estimate internal admin time for patching and backups
Estimate the internal hours your team will spend on upgrades, security patches, backup checks and restore tests for each option. For Odoo, account for the standard support window, the major-version upgrade cadence on Odoo Online and Odoo.sh, and the upgrade testing needed before production. For Dolibarr, account for patching the PHP application, the database and the web server, and for keeping modules compatible after upgrades. Put a loaded internal rate against each hour, or name the staff who will absorb the work. The step is complete when each option has a recurring hours figure reviewed by the people who will do the work.
Compare three-year totals side by side
Combine the subscription or hosting fees, implementation quotes, add-on costs, support fees and internal admin time into a three-year total for each option, separating one-time costs from recurring ones. Run a sensitivity check by changing the user count and the number of custom modules to see which inputs move the result most. Include the cost of a later migration if you may switch platforms. The step is complete when a single table shows both three-year totals, the assumptions behind each line and the figures that need to be confirmed with the vendors before you sign.
Questions buyers ask about Odoo and Dolibarr pricing
Is Dolibarr really free to self-host?
Yes, the software itself carries no license fee. Dolibarr is free open source software under the GPL, licensed GPL-3.0 per its GitHub repository, and the Dolibarr Association supports the project. What you still pay for is the infrastructure: a server or virtual machine, a web server running PHP, a MySQL, MariaDB or PostgreSQL database, backups, and the staff or partner who installs, configures and patches it. The Dolibarr prerequisites page estimates about 150 MB for program files and 35 MB for an initial database, plus space for uploaded and generated documents, so storage is rarely the main cost. Ask any implementation partner to quote hosting, setup, module configuration and ongoing patching as separate lines.
Why does Odoo on-premise require the Custom plan?
According to Odoo's pricing page, only the Custom plan can be hosted on Odoo.sh or on-premise, and only Custom includes multi-company, Odoo Studio, external API access and custom modules. The Standard plan is limited to Odoo Online. If your design needs your own servers, your own cloud account, or custom code, the Custom plan is the entry point, and its per-user pricing and yearly discount apply. The Enterprise edition is also required for on-premise use of the upgrade service. Confirm current plan terms directly with Odoo, because plan details change, and ask how user counts are measured across companies and environments.
What drives the implementation cost of Odoo or Dolibarr?
Implementation cost follows scope more than the license. The main drivers are the number of modules and processes to configure, how much data must be migrated and cleaned, the number of legal entities, integrations with payment, banking or e-commerce systems, and the amount of custom development. Odoo's Custom plan adds per-user subscription costs on top of implementation, while Dolibarr's modules are enabled individually, so scope tends to show up in configuration and extension work. Most DeployOpen engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts, so the quote follows from that written scope rather than a list price.
Can we do the Odoo or Dolibarr implementation ourselves?
You can, but the answer depends on skills and time more than software access. Dolibarr is a modular PHP application that runs on MySQL, MariaDB or PostgreSQL, and its modules can be enabled selectively, so a technical administrator with PHP and database experience can handle a basic install. Odoo is a Python and PostgreSQL application, and Odoo 19 requires Python 3.10 or later and PostgreSQL 13 or later according to its source installation documentation. Odoo on-premise also needs an Enterprise subscription code to activate Enterprise databases. Teams usually underestimate configuration, data migration, testing and the upgrade cycle, so list those tasks in a written plan and decide which parts your staff will own.
How long does a deployment take and what does it need from our team?
Duration depends on scope, data volume and how quickly decisions are made, and no supplied figure sets a standard timeline for either product, so ask for a timeline in the written scope rather than relying on a generic estimate. Your team typically needs a business owner who can sign off process design, a data owner for migration and cleansing, an administrator for infrastructure and access, and testers who can validate workflows before go-live. For Odoo, plan for the support window too: standard support covers the first three years after a major release, and Odoo 20 standard support is planned until September 2029, so schedule the first upgrade before that window closes.
What recurring costs should we budget beyond the license?
Recurring costs fall into five groups: Odoo subscriptions or Dolibarr hosting plans, infrastructure, backups and monitoring, add-ons or extensions, and support or upgrades. For Odoo, subscription per user is recurring, and Odoo's Enterprise support and upgrade service are tied to the subscription. For Dolibarr, DoliCloud publishes a Basic plan at 14 euros per user per month and a Premium plan from 45 euros per month, each with a 30-day free trial, if you choose managed hosting. Self-hosted Dolibarr trades those fees for internal or partner effort. Ask for annual totals in your quote and note which items change with user count.
Does Odoo support stop after a few years, and what does that mean for budget?
Odoo provides standard support with security updates and bug fixes for three years after a major release. Paid extended support is available afterwards only for on-premise and selected Odoo.sh versions, and security updates are only provided during standard support. Odoo 19, released in September 2025, has standard support until September 2028, and Odoo 17.0 standard support ended in September 2026. This means an on-premise Odoo deployment on an older release can carry a recurring extended-support cost or a forced upgrade cost, and both should appear in your budget. Confirm extended support pricing and eligibility with Odoo before you commit to a version.
When pricing should decide between Odoo and Dolibarr
Cost should decide the choice when the requirement list is short and stable. If the team needs only core modules such as invoicing, stock, CRM, projects or basic HR, and it can run a PHP web server with MySQL, MariaDB or PostgreSQL, self-hosted Dolibarr carries no license fee. The costs that remain are the server, database backups, staff time for installation and patching, and any DoliStore add-ons the team chooses. The Dolibarr prerequisites page estimates about 150 MB for program files and 35 MB for an initial database, plus space for uploaded and generated documents, and recommends at least a 1 GHz CPU for 30 or more users, so hardware is rarely the deciding line item. Confirm that every module you need appears in the Dolibarr module list before you assume the free route covers it.
Cost pushes toward Odoo's Custom plan once the requirements include Enterprise apps, multi-company, custom modules or on-premise hosting. According to Odoo's pricing page, only the Custom plan can be hosted on Odoo.sh or on-premise, and only Custom includes multi-company, Odoo Studio, external API access and custom modules. The One App Free and Standard plans are limited to Odoo Online. Odoo lists per-user monthly prices with a yearly discount, so the bill grows with headcount. Enterprise-only apps also fall under the Enterprise license, which requires a valid subscription matching the user count. Ask for a quote built on your exact user count, the apps you need, the hosting target, the support level and whether the upgrade service is included. If you use an implementation partner, ask for a fixed written scope before comparing totals.
Dolibarr is not free in every sense, so cost out one year of effort on each route. DoliCloud's published plans start with a Basic plan at 14 euros per user per month and a Premium plan from 45 euros per month, each with a 30-day free trial, so hosted Dolibarr also scales with users. Self-hosting moves the cost to your team: patching the PHP and database stack, handling major Dolibarr releases and building or buying extensions. Odoo Community is also free to run, but it leaves out the Enterprise features described above, so the real comparison is a free core with more manual upkeep against a paid platform with vendor-provided upgrades. The full comparison of licenses, module depth and upgrade effort appears in the overall Odoo vs Dolibarr comparison on this site.
How DeployOpen helps you price an Odoo or Dolibarr deployment
DeployOpen plans, implements, integrates, backs up, upgrades, documents and supports self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For an Odoo or Dolibarr pricing decision, that means turning hosting, edition, add-on and support assumptions into a written scope you can compare against vendor quotes.
How we scope
- We confirm user counts, companies, required apps and whether Odoo Online, Odoo.sh or on-premise fits your environment.
- We list which Enterprise apps, modules or DoliStore add-ons your processes depend on before any cost is set.
- Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts.
How we build
- We install and configure the chosen platform in your infrastructure, including database and web server requirements.
- We build the integrations, custom modules or Module Builder extensions that the written scope names.
- We test upgrade paths on a copy of the database and document the effort each major version change would add.
How we hand over
- You receive documentation covering the hosting model, licensing assumptions, add-ons and the recurring cost items.
- We set up backups, database copies for testing and the access controls named in the agreed scope.
- Handover includes a run book so your team can see what recurs each year and who pays for each part.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers after handover.
- A retainer can cover version upgrades and patching so the support window in your plan is actively managed.
- Ask any provider, including us, to state in writing which costs are one-time and which recur.
