OverviewTechnical deep dive

Case Study Triply

A marketplace built to scale

End-to-end design and engineering of triply.nz New Zealand's holiday rental marketplace, from zero to 150+ live properties.

Client

Triply Limited

Market

New Zealand

Status

Live triply.nz

Scope

Full-stack product

The Challenge

New Zealand needed its own rental marketplace

The NZ holiday rental market was dominated by international platforms that imposed generic commission structures and offered no local-first experience. Triply's founders wanted a marketplace that put NZ hosts in control with a choice of billing models and direct Stripe payouts.

The scope demanded two distinct host billing plans, a full Stripe Connect marketplace with instant payouts, iCal sync for double-booking prevention across platforms, PMS integrations for professional hosts, and a robust admin layer all built, documented, and deployed to production.

0+

Properties live during marketing phase

0

Requirements specified & built

0

Selenium test suites across P1–P3

What We Built

A complete, production-grade marketplace platform

Forgex delivered Triply from architectural design through to production deployment. We built a dual-sided marketplace guests search and book, hosts list and get paid with every edge case covered: from webhook idempotency to subscription quantity proration.

The platform supports two host billing models an 8% commission plan and a flat NZD $30/property/month subscription with all billing logic centralised into a single activatePlan() function to eliminate duplication. Property status flows through a full admin moderation lifecycle before going live.

Next.js 14 App RouterSupabase + RLSStripe Connect MarketplaceStripe BillingiCal SyncHostaway & Lodgify PMSApify ScrapingResend Transactional EmailReact Leaflet MapsRecharts AnalyticsReferral & Credits EngineAdmin DashboardSEO + JSON-LDMeta Conversions APIVercel Edge DeploymentRow-Level Security

Platform Architecture

How the system fits together

GuestAuth + BookHostDashboardProperty217 reqsStripeConnect + BillingSupabaseDB + Auth + RLSBookingInstant confirmiCal Sync6h cronPMSHostaway · LodgifyAdminReview + Billing

Technical Depth

Engineering decisions that matter at scale

Auth & Security

  • Supabase PKCE flow
  • JWT role injection via custom hook
  • Row-Level Security on all tables
  • requireAuth() under 5ms (local JWT)
  • Stripe Webhook signature verification

Payments

  • Stripe Connect Express (NZ)
  • Instant booking + destination charges
  • 8% commission or 0% subscription
  • Proration on quantity changes
  • Idempotent webhook handlers

Property & Availability

  • 3 creation flows: manual, scrape, PMS
  • Admin moderation lifecycle
  • iCal sync every 6 hours (cron)
  • Double-booking guard at webhook level
  • Blocked dates released on refund

Performance

  • API routes under 800ms p95
  • Promise.all() for all dashboard queries
  • Exchange rate cached 1hr (Next.js)
  • ISR sitemap, Vercel Edge CDN
  • LCP <2.5s on 4G mobile

Outcome

Launched with real traction

Triply went from concept to a live, fully-operational marketplace. Within the marketing phase, 150+ properties were listed across New Zealand validating host demand before the full public launch. The platform handles real bookings, real Stripe payouts, and real subscription billing, all running on a serverless infrastructure designed to scale without re-engineering.

Forgex took a complex, multi-stakeholder marketplace brief and delivered a platform we can confidently run a business on every edge case covered, every integration working.

Triply Limited triply.nz

Building something like this?

We design and engineer complex platforms marketplaces, SaaS products, multi-sided networks from architecture to deployment.

Start a conversation →