YachtWorld Clone · Features

YachtWorld Clone Features: The Listing Is Not the Asset

In brokerage the same vessel is usually listed on several portals at once, so supply is not what separates you. What you actually own is the buyer relationship, the qualification data and the response discipline, and all three live in software. Here is what ships, grouped by who touches it, with every third-party account and deployment decision named against the feature rather than implied away.

Request a Live Demo →See Pricing
203 API handlers
40+ vessel spec fields
6 days to deploy
The lead
An object, not an email
What One Inquiry Actually Touches
01Captured with guest contact context
02Qualified by the LeadSmart answers
03Staged on the broker kanban
04Answered in inquiry-scoped threads
05Enriched with a curated shortlist
06Timed against a response metric
203
API Handlers Shipped
40
Relational Tables
46
Web Application Routes
8
Charter and Service Modules
Split by Audience

Tools for Each User Type

Six working surfaces on one Express API and one PostgreSQL schema.

01

The Buyer

Search covers keywords matched against text, make and model; range filters for engine hours, draft, beam, length, year and price, along with country, state and geospatial radius. Also included: favorites, side-by-side comparison, saved searches that carry named criteria, and alert emails sent daily or weekly once new matches appear. Display works in six currencies and five UI locales.

02

The Private Seller

A sell-lead intake capturing the vessel, contact details and price expectation as structured fields rather than a contact-form message. Listing create, update and delete, ordered photo management with captions and a primary flag, a video tour URL that plays inside the gallery, and a printable specification sheet.

03

The Yacht Broker

A listing manager with photo and upgrade control, a kanban inquiry pipeline carrying status, stage and private notes, inquiry-scoped messaging with conversation summaries, and a response-time endpoint that turns first-reply speed from a habit into a number on the dashboard.

04

The Dealership

A dealer directory and detail page with slug, branding, bio, contacts, geography, specializations and languages. A CRM holding clients with email, phone, budget, status and private notes, curated listing shortlists attached per client, and dealer-association middleware gating every dealer route so leads reach the right desk.

05

The Service Desk

Adjacent marine services come as eight modules, each with an intake form, reference codes and an operator queue: surveyors, finance, valuations, transport, charter, insurance, sell leads and boat shows. Every module records structured intent and follows a status workflow, instead of ending up in a shared mailbox.

06

The Marketplace Admin

User and dealer administration, listing moderation, plan CRUD with an activate toggle and subscriber counts, taxonomy control over boat types, categories, conditions and features, platform settings, articles and FAQs, support tickets and disputes with assignment and resolution, and all eight service queues in one console.

The JWT carries five role claims: admin, dealer or broker, seller, buyer and guest. Rather than a sixth role, the service desk above is a second face of the operator console, and each of the four authenticated roles can log in to the live demo.

Compare

Clone vs Classifieds Script vs Building From Scratch

The parts that decide whether a marine marketplace survives its first dealer network.

What decides itMiracuves YachtWorld CloneGeneric classifieds script
Time to a working platformSix working daysUnclear, with most of the work falling to you
Listing schema40+ vessel fields including draft, beam, engine hours and hull materialTitle, price and a photo array
SearchOne query path handles technical ranges together with geospatial radiusKeyword and a category dropdown
After the inquiry arrivesA lead object with stage, notes, reply and a response timerAn email to whoever owns the inbox
Broker CRMClients with budgets, notes and curated shortlists per clientNot present
Price transparencyAppend-only price history with price-drop badgesThe current number, and nothing before it
Adjacent servicesEight intake modules with reference codes and operator queuesA contact page, if that
Operator consoleModeration, plans, taxonomy, settings, disputes and eight queuesVery basic, or missing entirely
Source codeFull ownership; neither a runtime license nor a per-seat fee appliesOften limited, sometimes encrypted

YachtWorld stands as the reference point for the category, but it is not something you can buy or host yourself. What matters commercially is how the third column stacks up next to the second, and both next to a custom build, which the Development Cost page covers.

Quay to Quay

The Whole Yacht Marketplace Flow, End to End

One buyer, one vessel, from first search to under offer.

Step 1

Search and shortlist

The buyer filters on the criteria that actually matter for a vessel, saves a search with named JSON criteria, and sets an alert to daily or weekly. Distinct facet APIs for make, type and location serve the filter UI, so refining a filter does not force a full result recount.

Step 2

Compare and watch the price

Favorites and a side-by-side compare view on web and mobile, and on each listing an append-only price-history trail with price-drop badges. A price-drop-only toggle in search exists because on a seven-figure asset a reduction is the single strongest buying signal there is.

Step 3

Inquire, and get qualified

The inquiry is rate-limited, captures guest contact context, and carries a subject, message, source and intent. The buyer then answers the LeadSmart questionnaire, which is scored against a dealer-configurable intent threshold, so what arrives at the desk is a qualified lead rather than a name.

Step 4

Stage it and answer it

The lead lands on the broker kanban with status, stage and private notes. Replies happen in inquiry-scoped threads with sender identity, role, name and timestamp on every message, and a per-user server-sent event stream delivers it with a thirty-second heartbeat.

Step 5

Curate the alternatives

The broker attaches listings to the client record with their own notes, which is how a good broker actually works: the vessel the buyer asked about is rarely the one they buy. The client record holds budget and status, so the shortlist is built against a number rather than a guess.

Step 6

Under offer, then sold

Listing status moves through active, under offer and sold, with a sold price and date recorded. Those become the comparables behind market evaluation and the public market reports, which is what makes the next valuation conversation evidence-based rather than anecdotal.

Step 7

The services that follow

A vessel sale drags insurance, transport, finance and survey demand behind it whether or not you capture it. Each has its own intake form, reference code and operator queue, which turns adjacent demand into a recorded lead rather than a referral you never see again.

Web and mobile run the same flows against the same API, so an inquiry sent on a phone appears in the broker pipeline without a second integration.

Justified

Only Features That Matter

Each row is here because a brokerage stops working without it, not because a competitor lists it.

ModuleWhy the base build ships with it
Response-time endpointWhen the same vessel sits on four portals, the differentiator is who replies first with context. Measuring it per dealer makes an invisible habit manageable.
LeadSmart questionnaireA brokerage gets few leads and cannot afford to treat them identically. A scored intent threshold tells a broker which conversation to have first.
Append-only price historyBuyers on a months-long decision watch the price. An immutable trail is both a buying trigger and the evidence behind a later valuation.
Curated shortlists per clientBrokers sell alternatives, not the listing that was clicked. Without this the substitution happens over WhatsApp and leaves no record.
Geospatial radius searchWhere a vessel sits decides the cost of viewing it and of delivery. A radius filter must combine with technical ranges in a single query, otherwise it is theatre.
Dealer-association middlewareA multi-office group needs leads routed to the right desk on day one, enforced on the server rather than hidden in the interface.
Eight service queuesInsurance, transport, finance and survey demand arrives with every sale. Captured, it is a second revenue line; uncaptured, it is a gift to a partner.
Plan and upgrade limitsListing and featured limits held in plan feature JSON are what make a subscription tier mean something rather than being a price with no boundary.

Everything above is white-label and can be enabled, disabled or re-labeled per deployment through plans, settings and taxonomy.

Stack

The Tech Powering the Features

What the platform is built on, and what that means for the team who inherits it.

API and dataAn Express 5 API with 203 handlers across 35 registered route modules, over PostgreSQL with Drizzle ORM: 40 relational tables across 30 exported schema modules, JSONB for plan features, listing features and saved-search criteria, and parameterized queries throughout.
Web applicationReact and Vite with TypeScript across 46 routes grouped into public, auth, marketplace, service and dashboard surfaces, a Tailwind component library, skeletons, empty states and error boundaries, and SEO canonical, social metadata and JSON-LD on public pages.
One contract, two clientsThe OpenAPI YAML is the single source for both clients. Orval generates the TanStack Query hooks for web and Zod schemas keep validation in step, with the mobile app carrying its own copy of the spec and generated client. The runtime stays authoritative and spec parity belongs in CI.
Mobile buildExpo and React Native with NativeWind, Expo Router tabs for Home, Search, Favorites, Messages and Account, plus listing, dealer, charter, boat-show, surveyor and valuation screens, role dashboards, JWT persistence via Expo SecureStore, and EAS development, preview and production profiles.
Security controlsBcrypt hashing, bearer JWT with a seven-day expiry, role and dealer-association middleware, TOTP two-factor with enable, verify, disable and a login challenge, a global 100-per-15-minute IP limiter plus route-specific limits, Pino logging with query redaction, upload size and extension checks, and a GDPR JSON export.
DeploymentA Docker image built in multiple stages on Node 24 with pnpm, Compose publishing the app alongside Nginx, an Nginx reverse proxy with gzip, immutable static caching and baseline headers, and a PM2 fork configuration for operators who prefer a process manager to containers.

Thirty-five route modules each own their handlers and schema, and every integration point - payments, SMTP, VAPID, exchange rates, object storage - is a documented seam rather than a hard-coded provider.

Plain Words on Launch Readiness

What the Base Package Excludes

Listed up front so they do not surface after the invoice arrives.

01

Live card processing

Checkout, cancellation, plan selection and billing-cycle records are implemented; the invoice history, however, is a generated mock with six entries. Stripe, Adyen or any other provider can be linked with a routine configuration step we price along with your deployment, and not a gap in the platform - though the base build does not have it live.

02

Some admin surfaces are presentation only

The only thing confirmed as persistent is the platform-settings round-trip. Some decorative admin controls are for presentation only, while the subscription amount trend over six months is a modeled monthly-equivalent series, not settled cash. Each item is individually named in the security handbook.

03

Realtime is process-local

Server-sent events deliver typed inquiry and message events with a thirty-second heartbeat and disconnect cleanup. Delivery is process-local rather than a durable queue, so a second instance needs shared pub/sub before every user sees every event. Rate limiting is in-process at launch for the same reason.

04

Three integrations need your accounts

Search-alert emails need SMTP configured, Web Push fan-out needs VAPID keys, and the six display currencies are backed by a cached exchange-rate API whose provider you supply. A CDN and object storage for listing media come as the documented growth step, not as shipped modules.

05

The service modules facilitate only

The intake flows for valuation, survey, finance, transport and insurance record structured demand and sends it to a queue. None of them binds insurance, approves credit, guarantees transport or certifies surveys, and the platform never says it does. Workflows for partner fulfillment count as scoped work.

06

Shipped functionality only

203 handlers across 35 modules, 40 tables, 46 web routes, 40+ vessel specification fields, eight service modules with their own queues, six currencies, five locales, TOTP two-factor, GDPR export, append-only price history, and Docker, Nginx, PM2 and EAS deployment assets - all demonstrable in the live demo.

The developer and security handbook ties every control to the file implementing it and marks each as implemented or as a pre-launch hardening item. You will find the named release gates on the Development Company page.

Development Company

Miracuves Versus Agencies and Freelancers

The deployment process, a modeled reference deployment for a brokerage group, the named release gates and the nine questions worth asking before you hire anyone - on the Development Company page.

See the comparison →
FAQ

Functionality Queries

Does it work as a charter booking site?
Not primarily. At its center sit dealer CRM and a lead pipeline, in a brokerage marketplace where vessels are bought and sold. Charter is one of eight adjacent service modules and has its own catalog and a date and party-size inquiry flow. If charter booking is your core business, the Dream Yacht Charter Clone or the GetMyBoat Clone is the closer fit and we will tell you so rather than sell you this.
How are technical yacht specifications searched?
Filtering by range works on engine hours, draft, beam, length, year and price. Next to it sit hull material, fuel, make, condition, category and boat type, plus geospatial radius, state and country, and toggles for with video, under offer and price drop. Separate facet APIs cover location, type and make and feed the filter UI, which lets refinement avoid a full recount.
Do dealers get tools for their own listings and leads?
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 review with a configurable intent threshold, listing optimizer scoring and a response-time endpoint.
Is it multi-currency and multi-language?
The base build carries six display currencies (USD, EUR, GBP, AED, CAD and AUD), with exchange rates cached by an API that talks to a provider of your choice. It also carries five UI locale dictionaries: English, Italian, German, French and Spanish. Operators can set both as defaults, which means no separate build per deployment.
Is there a mobile version?
Yes. The Expo React Native build uses Expo Router with tabs for Home, Search, Favorites, Messages and Account, plus listing, dealer, charter, boat-show, surveyor, valuation, compare and role-dashboard screens, all against the same API as the web app. EAS build profiles are included. The query cache is offline-tolerant for reads, not offline mutation sync, and app-store distribution needs your own developer accounts and signing.
Which eight marine service modules are included?
The modules cover boat shows, surveyors, charter, valuations, finance, sell leads, transport and insurance. Each module has its own public intake form plus a status workflow, a reference code where implemented, and an operator queue inside the admin console. Their job is to facilitate leads; none binds insurance, approves credit, guarantees transport or certifies surveys.

Open the demo rather than take our word

A working login exists for every role, with no setup needed. Search as a buyer and send an inquiry, then open the same lead in the broker workspace and see it show up in the operator console.

Explore

Tour the YachtWorld Clone Listings

Five pages on this product. You are on Features.

A brokerage platform, not a listing grid

Specification-rich listings, technical and geographic search, a lead object that survives being handed between people, a broker CRM and eight marine service queues, with the full source on infrastructure you own.

Talk to Us →
Miracuves · YachtWorld Clone Features Feature set, stack and stated limitations cross-verified against the hub, 2026-09-03
Disclaimer

Miracuves is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by YachtWorld.

Title background note

“YachtWorld Clone” is used descriptively. It is how the software industry refers to building a platform with functionality similar to YachtWorld, and how clients search for it.

Page credits note

The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from the YachtWorld website or applications.

Trademarks

YachtWorld and all other third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.