YachtWorld Clone App - White-Label Yacht Marketplace & Brokerage Platform

The launch-ready white-label build starts from $4,299. That covers the complete platform: 46-route web application, Expo mobile app, admin console, 203 API handlers across 35 modules, the 40-table PostgreSQL schema, deployment assets and the full documentation set, with deployment in six working days. Cost increases with payment-provider integration, partner fulfilment workflows, data migration from an existing inventory system and infrastructure complexity.

Plan selection, billing-cycle records, checkout and cancellation are implemented, and the invoice history is a generated six-entry mock. Connecting a live payment provider such as Stripe or Adyen is a standard configuration step, and we quote it as part of your deployment. We state this plainly rather than implying live card processing ships in the base build.

Not primarily. This is a brokerage marketplace for buying and selling vessels, with dealer CRM and a lead pipeline at its centre. Charter is one of eight adjacent service modules and has its own catalogue and date and party-size inquiry flow. If charter booking is your core business, the Dream Yacht Charter Clone or GetMyBoat Clone is the closer fit and we will tell you so.

Five: guest, buyer, seller, dealer or broker, and admin. Role claims sit in the JWT and dealer association is enforced by middleware on dealer routes. Each role has its own dashboard, and all four authenticated roles have a working login in the live demo above.

Sell leads, charter, insurance, transport, finance, surveyors, valuations and boat shows. Each ships with a public intake form, a reference code where implemented, a status workflow and an operator queue in the admin console. They facilitate leads; they do not bind insurance, approve credit, guarantee transport or certify surveys, and the platform never claims otherwise.

Yes. Dealers get a listing manager with photo and upgrade control, a kanban inquiry pipeline with status, stage and private notes, inquiry-scoped messaging, a CRM holding clients with budgets and notes, curated listing shortlists per client, LeadSmart questionnaire review with a configurable intent threshold, listing optimizer scoring and a response-time endpoint.

Yes. The Expo React Native build uses Expo Router with tabs for Home, Search, Favourites, Messages and Account, plus listing, dealer, charter, boat-show, surveyor, valuation, compare and role-dashboard screens, all running against the same API as the web app. EAS build profiles are included. App-store distribution requires your own developer accounts and signing, which is a standard prerequisite rather than a platform blocker.

Six display currencies ship in the base build: USD, EUR, GBP, AUD, CAD and AED, backed by a cached exchange-rate API whose provider you configure. Five UI locale dictionaries ship: English, Spanish, French, German and Italian. Both are operator-configurable defaults.

Per-user server-sent events deliver typed events with a 30-second heartbeat and disconnect cleanup, and Web Push fan-out is supported once you configure VAPID keys. SSE delivery is process-local rather than a durable queue, and the documented scale-up path is shared pub/sub. We name that limitation rather than describing it as enterprise messaging.

Yes. The monorepo transfers with full ownership: the React and Vite web app, the Expo mobile app, the Express 5 API, the Drizzle schema across 40 tables and 30 schema modules, the OpenAPI contract with its generated clients, the search-alert job and the Docker, Nginx, PM2 and EAS deployment assets. No runtime licence, no per-seat fee, no revenue share and no dependency on our roadmap.

Bcrypt hashing, bearer JWT with role and dealer-association middleware, TOTP two-factor, global and route-specific rate limiting, parameterized Drizzle queries, update allowlists, request logging with query redaction, password-confirmed deletion and upload size and extension checks. The security handbook maps each control to its source file and publishes the pre-launch hardening list rather than hiding it. No certification or vulnerability-free claim is made.

Yes. Branding, taxonomy for boat types and categories, plan tiers with limits and displayed amounts, articles and FAQs, currency and locale defaults, support categories and dispute reasons, and which service modules are enabled at all are operator-controlled. Deeper brand and workflow changes are customization services and we scope them with you.

Six working days for the ready-made build on your infrastructure. Custom work sits at two to eight weeks depending on scope, and anything larger is scoped and quoted in writing before it starts.

Tell us. The base build is a foundation, not a ceiling. Data migration from your current inventory system, feed syndication to third-party portals, partner fulfilment workflows, a dedicated search engine, enterprise SSO and object storage are all things we have scoped before. Some get included in the deployment and others are quoted, but the conversation starts with what your brokerage actually needs.