Technology
A Next.js front end is only as good as what stands behind it. Every Next.js system on this page talks to a real backend we also built or run: an ERP, a CMS, a payment platform. That is the part most agencies leave to someone else.
Reviewed by Bhavesh Selarka, COO & Co-Founder, Heliconia Solutions · Odoo 16 Functional Certification · Odoo Partner · Updated
Businesses that run on what we built
The short answer
Next.js fits when you need a fast, indexable web experience with real application behaviour behind it: authentication, personalised data, search, content and transactions. It is the right tool for storefronts, member portals, dashboards and content-heavy products that must be quick on first load and dynamic afterwards. It is the wrong tool for a five-page brochure site, and for anything where the team has no appetite for a JavaScript build pipeline.
We build Next.js as the presentation layer over systems that hold the data: Odoo for commerce and operations, Payload CMS for editorial content, and APIs for everything else. That split is deliberate. It keeps the business logic where it can be audited and lets the interface change without a migration.
The four projects named on this page are all running in production, and each one solves a different problem: a multilingual association portal, a direct-to-consumer storefront, a workforce payments platform and a remittance product. None of them would work if the front end didn't have something solid behind it.
What we deliver
Stated as outcomes, each with the project it comes from.
Freiburger Bund runs a Next.js 15 portal for a medical association: news, community, jobs, learning and a medical-journey section, in German, English, French and Arabic, with live messaging and full-text search.
LittleQ sells through a Next.js storefront on GraphQL with Odoo behind it for catalog, stock, orders and customers, plus Cashfree payments and Shiprocket shipping.
Tubo Ventaja got HRIS, timekeeper, e-wallet and face-recognition interfaces built into its Next.js workforce-payments product by our engineers working inside its sprints.
Tubo Ventaja moved from the pages directory to the App Router with authentication rebuilt in the process, shipped incrementally rather than as a rewrite everyone waits for.
Freiburger Bund pairs Next.js 15 with Payload CMS 3, so editors publish in four languages and the front end stays a front end. This website runs the same pattern.
MeiliSearch for instant full-text search across thousands of records, S3-compatible object storage for sensitive documents, and Firebase Cloud Messaging for push, all wired into the same Next.js app at Freiburger Bund.
The pattern
The same shape on every project: Next.js renders and orchestrates, the systems of record stay authoritative, and the boundary between them is an explicit API rather than a shared database.
Visitors and members
Public pages, authenticated portals and dashboards on the web.
Mobile apps
React Native or Flutter clients calling the same APIs as the web.
Editors
Content teams working in Payload CMS, not in the codebase.
Next.js application
App Router, server components for data-bound pages, client components only where interaction needs them. Rendering chosen per route: static where it can be, server-rendered where it must be.
API layer
GraphQL or REST against the systems of record, with authentication, caching and rate limits. This is the contract, and it is versioned deliberately.
Content
Payload CMS for editorial structures, localisation, media and preview, running next to the app rather than as a separate SaaS dependency.
Systems of record
Odoo for commerce, inventory, orders and finance, or the client’s existing platform. The front end never becomes the place business rules live.
Honest positions
Framework choice should follow the system, not the other way round. These are the calls we actually make.
| Your situation | What we would recommend | Why |
|---|---|---|
| A storefront or portal with real data behind it | Next.js | Fast first load, indexable, and dynamic once the user is in. This is the case it was designed for |
| A marketing site with a few dozen pages | Astro, as this site uses | No client framework to ship, simpler hosting, and the content team gets the same CMS either way |
| An internal tool used by staff who are already in the ERP | Build it in Odoo | A separate front end adds an integration and an auth model you would otherwise not need |
| A mobile-first product | Flutter or React Native, sharing the same APIs | A responsive web app is not the same as an app. Decide deliberately rather than by default |
| Your team is a Rails, Laravel or .NET shop with no JS capacity | Stay where your team is strong, or hire for it properly | A framework nobody on your side can maintain is a liability, however good the launch looks |
We build in Astro, Odoo and Flutter as well, so this is not a recommendation we make to fit what we sell.
How we work
Evidence
Four systems, four different problems. Each one names its stack and what it does.
| Project | Industry | Odoo | Key capabilities | Technology |
|---|---|---|---|---|
| Freiburger Bund | Healthcare association & career portal | Odoo 18 Enterprise | Freiburger Base · Freiburger Community Portal · Freiburger Info & News Portal · Freiburger Job Portal | Odoo 18 Enterprise · Python · PostgreSQL · Next.js 15 · React 19 |
| 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 |
| PayRemit | FinTech: digital payments & remittance | Odoo | Agent Management · Employer Management · Commission Management · Payment History Reports | Odoo · Python · PostgreSQL · Next.js · Flutter |
Read the projects
A four-language association platform, a headless storefront on Odoo, and engineers embedded in a client product team.
Healthcare association & career portal
A medical association platform where Odoo 18 Enterprise is the business backend behind a Next.js 15 web portal, React Native (Expo) iOS/Android apps, a Socket.IO messaging server and MeiliSearch: in German, English, French and Arabic.
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.
Two ways to work with us
This page is about delivering a system. If what you need is Next.js capacity inside your own team, working in your repository and your sprints, that is a different engagement and it has its own page.
What clients say
Heliconia transformed our business with Odoo. They implemented a dynamic website with e-commerce capabilities, enhancing our online presence significantly.
Sandesh ThummarBusiness Owner, Ladder LogixHeliconia provided a unique canteen solution, saving us valuable ordering time. Their innovative approach has been invaluable to our operations.
Pradeep LakhaniBusiness Owner, Avasar AgencyQuestions
Yes, and it is one of the architectures we build most often. Odoo exposes the data over GraphQL or REST, Next.js renders it, and the business rules stay in the ERP where they can be audited.
LittleQ sells through exactly this: a Next.js storefront on GraphQL with Odoo running catalog, stock, orders and customers.
App Router on anything new. For an existing product, migrate incrementally rather than rewriting: both routers can run in the same application while you move route by route.
We did that for Tubo Ventaja, rebuilding authentication as part of the migration and shipping through normal sprint releases rather than a freeze.
Payload CMS, in most cases. It is TypeScript-native, runs alongside the Next.js app rather than as a separate SaaS, and gives editors localisation, preview and media without the front end becoming a content store.
Freiburger Bund runs Next.js 15 with Payload CMS 3 in four languages. This website runs the same pairing.
Yes, and often that is the better engagement. Our engineers joined Tubo Ventaja’s product team, worked in its repository and sprint cadence, and delivered the App Router migration alongside new HRIS and e-wallet features.
On any Node-capable host: your own cloud account, a container platform or a managed Next.js host. We build without assuming a specific vendor, because hosting lock-in is a decision that should be made openly rather than inherited from a template.
Often not. If the site is mostly content with little application behaviour, a static-site framework ships less JavaScript and is simpler to host. This site is built in Astro for that reason, with Payload CMS behind the blog.
We will tell you when that is the better answer.
Next step
The front end is the easy half. Send us the systems it has to talk to, who uses it and what it has to stay fast under, and we will propose an architecture with the boundaries drawn.