Open core
Odoo's core is open source; depending on the project, community, enterprise and Corelane modules combine. Open APIs, exportable data – and the freedom to leave.
Architecture & technology
One source of truth.
CRM, ERP, store and communication are not synchronised systems – they are one system. Odoo on PostgreSQL is the data truth. Everything else docks on.
Why Odoo
An open core, open APIs, full data sovereignty.
PostgreSQL
The entire company state lives in one proven relational database. Consistent, transactional, restorable – one backup contains the whole company.
Python
The world's most popular programming language – number 1 in the PYPL index for years – and the language of the AI ecosystem. Extensions, integrations and AI workflows speak the same language, and developers are easy to find.
Modular by design
From accounting to the warehouse: modules share one data model instead of exchanging data over interfaces.
The extended stack
The core stays lean. Intelligence docks on.
AI, search and storage run beside the core – never inside it. They read context from the platform and write back through controlled interfaces with human approval.
C
Odoo + PostgreSQL
The data truth: master data, transactions, documents and communication in one transactional context.
LangGraph
Agent orchestrationAI agents work outside the core and hand results back for human approval – steered from the Corelane AI Cockpit.
Qdrant
Vector databaseSemantic search and retrieval-augmented generation over your own documents and knowledge.
Elasticsearch
Store searchFaceted, fast product search across catalogues with 100,000+ products.
S3 object storage
Documents & assetsImages, documents and generated assets – versioned and EU-hosted.
Proxmox
VirtualisationOperations on our own European infrastructure – full control over data, backups and recovery.
Redis
Sessions & cachingFast sessions and caching for a responsive platform under load.
The AI construction kit
This is how an AI co-worker is built.
Every Corelane agent is assembled from six proven building blocks. What varies is the task – the kit stays the same.
- 01
Model
The language model is configuration, not architecture: leading providers, European alternatives or local models – interchangeable per workflow.
- 02
Skills
Reusable abilities instead of one-off builds: extraction, matching, drafting – tested once, used by many agents.
- 03
MCP servers
Controlled tool access: agents reach platform, search and data only through defined MCP interfaces – never directly.
- 04
Orchestration
LangGraph teams with review loops instead of a single prompt: scouts, writers and reviewers check each other.
- 05
Knowledge & context
Retrieval from your own sources, context preserved across runs – the agent knows the case, not just the question.
- 06
Approval & operations
Every effect passes through the cockpit: people approve, budgets meter, the audit trail records.
Not a chatbot experiment: this kit produces at STASTO in daily operations.
Security architecture
Layered from the outside in.
Public traffic never reaches the core directly: it is filtered at the edge, passes a hardened security layer and only then reaches the platform.
Internet
Public traffic
Edge protection
Filtering & WAF
Security layer
Firewall, reverse proxy and VPN for locations
Platform core
Not directly reachable from the internet
Odoo platformSearchAI servicesData & backups
The core stays private
Every external access passes filtering and security layers before it reaches a core system.
Own operation, full control
Business-critical systems run in our own cluster on European infrastructure – data, availability and evolution stay in one hand.
Backups by design
Automated backups up to offsite copies are part of the architecture, not an add-on.
Sovereignty & governance
Your data. Your platform.
01Data stays in Europe
The platform and its data run on European infrastructure under GDPR; external AI models are swappable add-on services – never the data store.
02AI with approval
Every AI action is logged and traceable. Decisions with business impact are made by people, not models.
03Exit-capable by design
Open formats, an open-source core and your data in one database – exportable at any time.
Communication counts too
Data sovereignty gets discussed for the ERP. Mail, calendar and contacts have usually been with a cloud provider for years – although that is where the company's entire correspondence sits. At Corelane the same principle applies to them as to the rest of the platform.
An open-source stack
Postfix, Dovecot and SOGo on standard protocols – IMAP, SMTP, CalDAV, CardDAV. Outlook, Thunderbird, iOS and Android connect as usual.
Administered where the people are
Mailboxes, aliases and delegations are maintained on the employee record in Odoo instead of a second admin console. Joining and leaving stay one process.
A security gateway in front
Spam and malware filtering runs on a specialised commercial service ahead of the mail servers. Operating the transport yourself does not mean operating the threat defence yourself.
No licence per workstation
Mail and calendar are part of the platform rather than a per-seat subscription, and the mailboxes stay exportable in open formats.
At STASTO this carries 205 active mailboxes across eight domains; 106 of them are tied directly to their Odoo user.
The next step