Enterprise RAG implementation guide: architecture, steps and best practices
What RAG is, the reference architecture for enterprise RAG, the build steps, common failure points and how to measure answer quality.
DeadlinesE-Invoicing by Dec 31, 20262026 Computerized Books in ORUS by Jan 30, 2027E-Invoicing Dec 31 · ORUS Jan 30
Check ReadinessOdoo runs in three ways: in Odoo's cloud, on Odoo's developer platform, or on servers you control. The right choice depends on one question more than any other: will you need custom code?
By TechNext · · Updated · 4 min readTechNext & Odoo
The short answer
Choosing where Odoo runs is one of the first decisions in any project, and it is easy to get wrong in either direction: paying for infrastructure you don't need, or picking a setup that can't take the customisation you will need next year. TechNext implements Odoo on all three options, so here is how they compare in practice.
Odoo Online is Odoo's software-as-a-service. Odoo hosts the database, handles servers, backups and security, and runs version upgrades through its own upgrade service. You can configure everything Odoo offers, and on the Custom plan you can use Odoo Studio to add fields, views and automations without code.
What you cannot do is install custom Python modules or third-party modules outside what Odoo provides. For many companies that is fine: standard Odoo plus configuration covers far more than people expect. Odoo's One App Free and Standard plans run on Odoo Online.
Odoo.sh is Odoo's cloud platform for projects that need code. It connects to a GitHub repository, so custom modules are developed, reviewed and deployed like any software, and it gives you development and staging branches that copy production data for testing. Odoo still runs the infrastructure; you or your partner own the code. Odoo.sh needs the Custom plan, and hosting is billed on top of the subscription.
On-premise means running Odoo on your own servers or your own cloud account. You get full control of the environment, and full responsibility for it: hosting, backups, security patches, monitoring and upgrades. For Odoo Enterprise it needs the Custom plan, billed yearly. It makes sense when data-residency rules or internal IT policy require it, or when a company already runs its own infrastructure team.
Why
Who runs what OdooYou or your partner
Start on Odoo Online if standard apps and configuration cover your processes. Choose Odoo.sh as soon as a requirement needs custom code. Go on-premise only for a concrete reason, such as a regulator, a group IT policy or existing infrastructure.
| Odoo Online | Odoo.sh | On-premise | |
|---|---|---|---|
| Who runs the servers | Odoo | Odoo | You |
| Custom Python modules | No | Yes | Yes |
| Studio (no-code changes) | Custom plan | Yes | Yes |
| Staging copies for testing | Database duplicates | Built in (branches) | You set them up |
| Version upgrades | Odoo's upgrade service | Planned, with your code | Planned, fully yours |
| Plans | One App Free, Standard, Custom | Custom, hosting extra | Custom, yearly |
| Best for | Most first phases | Custom modules, integrations | Strict IT or data rules |
Plan names and what they include change from time to time; check odoo.com/pricing for the current terms in your country.
We decide hosting during discovery, once we know what the first phase needs. Our rule of thumb:
A company can move later. An Odoo Online database can be moved to Odoo.sh or on-premise when custom code becomes necessary, and we plan that move like a small project, tested on a copy first.
No. Odoo Online supports configuration and, on the Custom plan, Odoo Studio. Custom Python modules need Odoo.sh or an on-premise installation.
Usually Odoo Online, because hosting is included in the subscription. Odoo.sh adds hosting fees on top of the Custom plan, and on-premise adds your own infrastructure and operations costs.
Yes. A database can move from Odoo Online to Odoo.sh or on-premise when you need custom code. TechNext plans and tests the move on a copy before switching.
Odoo Online for most first phases, Odoo.sh when a requirement needs custom code, and on-premise only when IT policy or data rules require it.
About TechNext. TechNext Pte. Ltd. is a BIR compliance and integration partner for accounting firms and finance teams: an Odoo Ready Partner headquartered in Singapore, with its main development and consulting hub in Taguig City, Metro Manila. We plug Odoo into the system you already run, and our own experts implement it end to end (discovery, configuration, data migration, training and support), set up with the Philippine (BIR) and Singapore (GST) localisations, for clients in 25+ countries. We are not affiliated with, accredited by or acting for the BIR or any government agency, and we do not file or register on your behalf. About us · Get my custom blueprint
What RAG is, the reference architecture for enterprise RAG, the build steps, common failure points and how to measure answer quality.
Discovery, staging, data migration, training, integration and support: what happens at each step, and what your team brings.
Configuration, Studio or custom code: what each costs at upgrade time, and five questions to ask before building anything.
TechNext sets up your Odoo, can build your website and brand on it, and stays on after go-live, in Singapore and the Philippines. An adviser reviews your situation first.
2027 BIR Audit Guide · sent by our team
Four details. A BIR Compliance Expert sends the guide to your work email within one business day. Inside: the eLA rules, the 10-day document rule, what examiners ask for, and a routine for audit requests.