Technology & SaaS
Product engineering for technology companies: frontend and backend architecture, APIs, authentication, subscriptions and billing, search, performance and integrations. If you're building the product, the engineering pages cover the how. This page is about running a software business on it, with Odoo carrying subscriptions, billing, support and the back office.
Reviewed by Atul Makwana, CEO & Co-Founder, Heliconia Solutions · Odoo 16 Functional Certification · Updated
Businesses that run on what we built
Direct answer
Heliconia builds and extends software products: Next.js web applications, React Native and Flutter apps, Node.js and Python APIs, authentication, multi-tenant data models, subscription billing on Stripe, search and caching: as a dedicated team inside your engineering process or as a delivery team for a defined product. Where a product needs subscriptions, invoicing, support or accounting, we often run those on Odoo behind the product rather than building them again.
This page is different from the others in the cluster because the buyer is different. You don't need to be told what an ERP is. You need to know whether we can hold a frontend/backend boundary, ship on a sprint cadence with your team, keep a multi-tenant system safe and make billing boring. The projects below are the answer.
SaaS challenges
Shipping features without constantly rebuilding the platform underneath them. App Router migrations done once, properly.
Maintainable frontend/backend boundaries, typed API contracts, services that can be replaced one at a time.
Multiple customers and organisations on one platform, database-per-tenant or shared, with provisioning, expiry and isolation handled.
Plans, subscriptions, upgrades, interval changes, invoices, payments and dunning that reconcile with accounting.
CRM, payments, communication, maps, identity, third-party services, through APIs and webhooks that survive vendor changes.
Traffic, data and usage that grow: caching, search, background jobs, load testing before customers find the limit.
SaaS architecture
The reference shape behind our SaaS work. Odoo sits in the application layer only when the product needs its subscriptions, orders or accounting. WaveContact and MEP Emart do. Tubo Ventaja doesn't.
Web
Next.js (App Router): server and client rendering, streaming, caching
Mobile
React Native (Expo) or Flutter, OTA updates
Admin
Operations screens: custom or Odoo back office
API layer
GraphQL / REST · authentication and authorization · webhooks · rate limits
Auth · Billing · Search
OAuth / OTP / SSO · Stripe subscriptions · Meilisearch
Application layer
Node.js / Python services: or Odoo for subscriptions, orders, helpdesk and accounting
Database / cache
PostgreSQL · Redis · object storage (S3 / R2)
External services
Payments · email / push · maps · identity · analytics
The subscription lifecycle
What a SaaS billing workflow has to do, as built for MEP Emart on Odoo 14 Community with Stripe, and for WaveContact on Odoo with Stripe recurring payments.
Step 01
Account and organisation created, plan chosen, trial or immediate activation.
Step 02
Tenant or database activated automatically from the subscription state.
Step 03
Stripe subscriptions for online plans. Offline annual plans with bank transfer or cheque records.
Step 04
Plan upgrades and billing-interval changes by the customer, prorated and invoiced.
Step 05
Reminders before expiry, retries, expiration handling and reactivation.
Step 06
Subscription health, payment history and expirations across every tenant on one dashboard.
Step 07
Invoices and payments posted. Revenue reported per plan and period.
Capabilities
Only the technologies our SaaS and product projects run.
Capability matrix
| Capability | Custom development | Odoo | Integration |
|---|---|---|---|
| Web application (Next.js) | Yes | –No | –No |
| Mobile application | Yes | –No | Yes |
| API layer and authentication | Yes | Yes | Yes |
| Subscriptions and recurring billing | Yes | Yes | Yes |
| Multi-tenant provisioning | Yes | Yes | –No |
| Orders, invoicing, accounting | –No | Yes | –No |
| Helpdesk and support tickets | –No | Yes | Yes |
| Search, caching, real-time | Yes | –No | Yes |
| Analytics and admin dashboards | Yes | Yes | Yes |
| Cloud infrastructure and CI/CD | Yes | –No | Yes |
Industry experience
Real systems. Real workflows. Real engineering.
| Project | Industry | Odoo | Key capabilities | Technology |
|---|---|---|---|---|
| WaveContact | SaaS: digital business cards | Odoo | Digital Business Card Management · Contact Management · Profile Management · Subscription Management | Odoo · Python · PostgreSQL · GraphQL · Flutter |
| MEP Emart | SaaS: AI solutions & digital transformation | Odoo 14 Community | Stripe · Odoo Website & customer portal · Email (SMTP) | Odoo 14 Community · Python · PostgreSQL |
| LittleQ | eCommerce, baby care | Odoo | Headless Odoo API · Product Catalog Management · Product Discount Engine · Distributor Registration Portal | Odoo · Next.js · PayloadCMS · React · Node.js |
| Tubo Ventaja | HRTech / FinTech: workforce payments | – | Google Maps API · Face recognition API · Location services · HRIS backend services (REST) | Next.js · React · Node.js |
| Kaypear Engineering | Process safety & engineering consulting | Odoo | Kaypear Base (Tank Design Models) · Kaypear Portal Theme | Odoo · Python · PostgreSQL · JavaScript · QWeb / XML |
| iDT Labs | ICT consulting & software: HRIS SaaS | Odoo 9 Community | HRIS SaaS Management · Employee Management · Attendance Management · Leave Management | Odoo 9 Community · Python · PostgreSQL |
| Opsio | Cloud managed services | Odoo 18 Enterprise | Cash Flow Forecast Report · Working Capital Report · Timesheet Profitability · Project Profitability | Odoo 18 Enterprise · Python · PostgreSQL · JavaScript · REST APIs |
| Flintu | Consumer electronics | Odoo 18 Enterprise | Client-specific Odoo customisations Product Customisation · OCA Module: product_manufacturer · Git-based deployment workflow for custom modules | Odoo 18 Enterprise · Python · PostgreSQL · AWS |
Evidence
A subscription SaaS with web and mobile clients, subscription automation for a multi-database platform, a D2C product on a headless stack, a Next.js team inside an HRTech product.
SaaS: digital business cards
Digital profile and contact-sharing platform where Odoo runs subscriptions, orders and the store behind a web frontend and a Flutter mobile app, with Stripe recurring payments, Google integrations and vCard export.
SaaS: AI solutions & digital transformation
A subscription lifecycle for a multi-database Odoo SaaS (online recurring plans on Stripe and offline annual plans, automated database activation and expiry, renewals and reminders, plan upgrades and billing-interval changes, customer self-service and a central subscription-health dashboard) built entirely on the Community edition.
eCommerce, baby care
A direct-to-consumer baby care brand selling through a Next.js storefront, with Odoo behind it for ERP, inventory, orders and customers: connected over GraphQL, with Cashfree payments, Shiprocket shipping and a distributor onboarding portal.
HRTech / FinTech: workforce payments
Payroll, timekeeping, leave and e-wallet features for agencies and employers: Heliconia Next.js developers embedded in the product team migrated the app to the App Router, rebuilt authentication, built HRIS, timekeeper, face-recognition and e-wallet interfaces and integrated Google Maps location features across sprint releases.
Process safety & engineering consulting
A client-facing portal where engineers run API 2000 fire-relief and breathing calculations through wizard forms, with the company’s engineering maths executed in the Odoo backend, a live input-audit tool, folder and batch organisation of tank designs, stage-based approvals, watermarked PDF reports with annexures and QR-code verification, plus sign-up, invitations and support ticketing.
Consumer electronics
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.
Engagement models
Next.js, Flutter and Odoo developers on your sprints, code reviews and repositories. Tubo Ventaja, PayRemit, iDT Labs.
Scope, architecture, build, launch: WaveContact, MEP Emart, Keypear.
When subscriptions, orders and accounting shouldn't be rebuilt, we put Odoo behind the product and expose it over an API.
Self-hosted, Git-driven deployments with documentation to run them without us.
What clients say
Heliconia provided a unique canteen solution, saving us valuable ordering time. Their innovative approach has been invaluable to our operations.
Pradeep LakhaniBusiness Owner, Avasar AgencyHeliconia transformed our business with Odoo. They implemented a dynamic website with e-commerce capabilities, enhancing our online presence significantly.
Sandesh ThummarBusiness Owner, Ladder LogixQuestions
Both. WaveContact and Keypear were built as products. Tubo Ventaja and PayRemit are existing platforms where our engineers work inside the client’s team on a sprint cadence.
Yes, when the product needs subscriptions, orders, invoicing, helpdesk or accounting. WaveContact runs subscriptions, orders and its store on Odoo behind a web frontend and a Flutter app. MEP Emart automates a multi-database SaaS subscription lifecycle on Odoo 14 Community with Stripe.
It depends on the product: database-per-tenant with automated provisioning and expiry (the MEP Emart model), or a shared schema with organisation-level isolation and permissions. We decide it in architecture, not after the first enterprise customer asks.
Stripe for recurring subscriptions in most markets. Razorpay and Cashfree for India. Offline plans (bank transfer, cheque) are handled in the same subscription model so finance sees one list.
Yes: that is our staff-augmentation model: Next.js, React Native, Flutter and Odoo developers embedded in your process, with code review, documentation and knowledge transfer built in.
Yes, for what we build: AWS, Docker, CI/CD, Git-based release workflows and self-hosted Odoo Enterprise environments, with documentation so your team owns it.
Next step
Send the architecture you have or the product you want. We'll come back with how we would structure it, who we would put on it and what the first release looks like.