Opairly & Aupairpromax
The challenge
The au pair niche has two sides, both poorly served. The host family struggles with coordination: WhatsApp chaos, lost house rules, hour tracking nobody trusts. The au pair herself struggles with something completely different: she's 22, living in another country for the first time, and searching online for answers nobody around her can give.
The analysis
User moments showed that families primarily need operational clarity, while au pairs need guidance, recognition and community. One generic interface would underserve both groups. The underlying technology could be shared as long as positioning, information architecture and workflows remained product-specific.
The solution
Two products on the exact same tech stack, for completely different people and moments. Opairly is the coordination tool for the host family with dashboard, tasks, house rules, hour tracking, and finances. Aupairpromax is the content and community platform for the au pair herself with a playbook, dispatches from abroad, and a monthly letter. One codebase, two souls, two sides of the same niche.
Why custom software
Opairly needs roles, private data, recurring tasks and financial agreements; Aupairpromax centers on editorial content and community. Custom modeling allowed both to share a maintainable stack without forcing either experience into a generic SaaS template.
Technology
Nuxt and Vue form the shared frontend foundation. Supabase provides data, authentication and access control; Cloudflare handles hosting and performance. The architecture separates reusable building blocks from product-specific workflows.
Results
For families
Opairly: dashboards, planning, house rules, and finances
For au pairs
Aupairpromax: content, community, and soft life rituals
One tech stack
Nuxt, Tailwind, Supabase, and Cloudflare for both products
Both products are live and serve a clearly defined side of the niche. Opairly centralizes family coordination; Aupairpromax publishes support for au pairs. Shared technology reduces maintenance while preserving two distinct product identities.
Need something similar?
Tell me about your project and I'll think along, no obligations.