Project at a glance
A consumer-electronics company took full control of its ERP: Odoo 18 Enterprise on AWS EC2 with RDS PostgreSQL, separate development and production environments, GitHub repositories for Community, Enterprise and custom add-ons, a controlled release workflow and the documentation to run it independently, with hourly expert support on call.
- Client
- Flintu
- Industry
- Technology & SaaS
- Platform
- Odoo 18 Enterprise
- Duration
- 2 weeks deployment, ongoing support
- Services
- Odoo Consulting, Odoo Implementation, Odoo Development, Odoo Support, Odoo Enterprise
The challenge
A self-managed Odoo Enterprise setup with complete control over deployment and version management, isolated development and production, Git-based customisation workflow, a clean start without legacy data, and enough knowledge transfer to operate production independently.
Working through a similar challenge? Talk to an Odoo expert
The solution
Designed and deployed the architecture on AWS: Odoo Enterprise on Ubuntu LTS, EC2 application servers, RDS PostgreSQL, DNS, SSL and services configuration. Git repositories for Community, Enterprise and custom add-ons with a custom add-on deployment workflow. A production replication strategy. Installation and deployment documentation. And ongoing consulting on server administration, email and deployment practice. Product customisations plus the OCA product_manufacturer module.
How we built it
- Installed and configured Odoo Enterprise on Ubuntu LTS.
- Configured AWS EC2 application servers and AWS RDS PostgreSQL database.
- Established Git-based version control using separate repositories for Community, Enterprise, and custom add-ons.
- Configured custom add-on deployment workflow.
- Set up DNS, SSL, server services, and environment configuration.
- Created detailed installation and deployment documentation using Google Docs for ongoing maintenance.
- Assisted with production replication strategy to ensure the client could independently manage production deployments.
- Provided ongoing technical consulting for server administration, email configuration, and deployment best practices.
Integrations
- AWS EC2 / RDS
- GitHub
Custom development
Technical details: 3 custom modules
- Client-specific Odoo customisations Product Customisation
- OCA Module: product_manufacturer
- Git-based deployment workflow for custom modules
What changed
- Scalable self-hosted Odoo Enterprise environment in production
- Structured development-to-production release workflow
- Change tracking through Git-based version control
- Client manages its own production servers
- Deployment risk reduced by isolated validation environments
Have a business process that doesn’t fit standard Odoo?
Discuss your requirementWhat made this project different
- Fully self-managed Odoo Enterprise deployment instead of relying on managed hosting.
- Separate development and production environments with controlled migration process.
- Git-driven deployment strategy for all customizations.
- Complete infrastructure ownership retained by the client.
- Detailed documentation and knowledge transfer enabling long-term self-sufficiency.
- Flexible hourly support model for both development and technical consulting.
Technology
- Odoo 18 Enterprise
- Python
- PostgreSQL
- AWS
Team
The expertise on the project, not personal profiles.
- Odoo Solution Architect
- DevOps & Infrastructure Engineer
- Odoo Developer
Questions
What did Heliconia build for Flintu?
A consumer-electronics company took full control of its ERP: Odoo 18 Enterprise on AWS EC2 with RDS PostgreSQL, separate development and production environments, GitHub repositories for Community, Enterprise and custom add-ons, a controlled release workflow and the documentation to run it independently, with hourly expert support on call.
Which Odoo version and edition does Flintu use?
Odoo 18 Enterprise, the Enterprise edition, version 18.
Which systems were integrated for Flintu?
AWS EC2 / RDS, GitHub.
What technologies were used on the Flintu project?
Odoo 18 Enterprise, Python, PostgreSQL, AWS.
How long did the Flintu engagement last?
2 weeks deployment, ongoing support.
Who worked on the Flintu project?
A team of: odoo solution architect, devops & infrastructure engineer, odoo developer.
