One foundation, two brands
A single codebase deployed for both operators. Same templates, same components, same routes; only the content and identity change.
Aviation · Helicopter · In production
Two helicopter operators, one platform.
Monacair and Héli Sécurité share the same operational reality. One Next.js + PayloadCMS codebase, two domains, 144 and 116 bilingual URLs, online booking.
- Client
- Monacair × Héli Sécurité
- Sector
- Aviation · Helicopter
- Year
- In production
- Role
- Full-stack development
- 144 bilingual URLs — Monacair
- 116 bilingual URLs — Héli Sécurité
- 28 destinations
- 9 events
- FR / EN
Context
Monacair operates the Monaco heliport and carries around 50,000 passengers a year. Héli Sécurité, founded in 1992 in Grimaud, is one of the Riviera's leading charter operators. Both brands belong to the same group and share a fleet, destinations and an international clientele.
Two brands, two domains, two histories — but one operational reality: the same aircraft, the same destinations, the same booking journey.
The challenge
- 01Maintain a catalogue of 28 destinations, 15 experiences and 9 events in two languages without doubling the editorial effort.
- 02Make conversion happen on the destination page and the booking widget, not on the homepage.
- 03Hold a luxury image: speed, restraint, no friction.
What I built
PayloadCMS as the back office
Shared collections, centralised media, admin disallowed to crawlers. Content is entered once and served on both domains.
Static rendering and CDN
Incremental static regeneration on Vercel: pages are served from cache and regenerated in the background. The booking widget stays native to the page.
Structured SEO
hreflang FR/EN + x-default, LocalBusiness JSON-LD, complete sitemaps. 144 URLs for Monacair, 116 for Héli Sécurité.
Architecture
- 01
PayloadCMS — shared collections
- 02
API & media
- 03
Next.js — incremental rendering
- 04
Vercel CDN
- 05
monacair.mc · helisecurite.fr
Stack
- Next.js
- PayloadCMS 3
- PostgreSQL
- Vercel
- TypeScript
What's next
Gradually differentiate the editorial content of both brands to reduce duplication, and industrialise event pages ahead of each seasonal peak.
Transparency
No performance figures are published: audience and conversion data belong to the clients. The technical facts cited — versions, volume, languages — are verifiable.
A similar project?
Describe your context. I'll tell you what I would do, what I wouldn't, and in what order.
Next case study
JetHouse — A business aviation operator that publishes without a developer.