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 PricingFeature Set by Role
Six working surfaces on one Express API and one PostgreSQL schema.
The Buyer
Keyword search across text, make and model, then range filters on price, year, length, beam, draft and engine hours, plus country, state and geospatial radius. Favourites, side-by-side compare, saved searches with named criteria, and daily or weekly alert emails when new matches land. Six display currencies and five UI locales.
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.
The 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.
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.
The Service Desk
Eight adjacent marine modules with their own intake forms, reference codes and operator queues: sell leads, charter, insurance, transport, finance, surveyors, valuations and boat shows. Each captures structured intent and carries a status workflow rather than landing in a shared mailbox.
The Operator
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.
Five role claims sit in the JWT: guest, buyer, seller, dealer or broker, and admin. The service desk above is the operator console's second face rather than a sixth role, and all four authenticated roles have a working login in the live demo.
Clone vs Classifieds Script vs Building From Scratch
The parts that decide whether a marine marketplace survives its first dealer network.
| What decides it | Miracuves YachtWorld Clone | Generic classifieds script |
|---|---|---|
| Time to a working platform | Six working days | Unknown, and largely do it yourself |
| Listing schema | 40+ vessel fields including draft, beam, engine hours and hull material | Title, price and a photo array |
| Search | Technical ranges and geospatial radius in one query path | Keyword and a category dropdown |
| After the inquiry arrives | A lead object with stage, notes, reply and a response timer | An email to whoever owns the inbox |
| Broker CRM | Clients with budgets, notes and curated shortlists per client | Not present |
| Price transparency | Append-only price history with price-drop badges | The current number, and nothing before it |
| Adjacent services | Eight intake modules with reference codes and operator queues | A contact page, if that |
| Operator console | Moderation, plans, taxonomy, settings, disputes and eight queues | Very basic, or missing entirely |
| Source code | Full ownership, no runtime licence, no per-seat fee | Often limited, sometimes encrypted |
YachtWorld itself is the reference for what this category looks like; it is not a product you can buy or self-host. The commercially useful comparison is the second column against the third, and against a custom build, which is covered on the Development Cost page.
How It Works, End to End
One buyer, one vessel, from first search to under offer.
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.
Compare and watch the price
Favourites 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.
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.
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.
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.
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.
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.
Every Feature Earns Its Place
Each row is here because a brokerage stops working without it, not because a competitor lists it.
| Module | Why it is in the base build |
|---|---|
| Response-time endpoint | When 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 questionnaire | A 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 history | Buyers 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 client | Brokers sell alternatives, not the listing that was clicked. Without this the substitution happens over WhatsApp and leaves no record. |
| Geospatial radius search | A vessel's location decides viewing cost and delivery. Radius has to combine with technical ranges in the same query or the filter is theatre. |
| Dealer-association middleware | A 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 queues | Insurance, 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 limits | Listing 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-labelled per deployment through plans, settings and taxonomy.
The Technology Behind the Features
What the platform is built on, and what that means for the team who inherits it.
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.
What Is Not Included in the Base Package
Named here rather than discovered after the invoice.
Live card processing
Plan selection, billing-cycle records, checkout and cancellation are implemented, and the invoice history is a generated six-entry mock. Connecting Stripe, Adyen or another provider is a standard configuration step that we quote with your deployment, not a platform gap - but it is not live in the base build.
Some admin surfaces are presentation only
Only platform-settings round-trips are confirmed persistent. A small number of decorative admin controls are presentation only, and the six-month subscription amount trend is a modelled monthly-equivalent series rather than settled cash. The security handbook names each one individually.
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.
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. Object storage and a CDN for listing media are the documented growth step rather than shipped modules.
The service modules facilitate only
Insurance, transport, finance, survey and valuation intake capture structured demand and route it to a queue. They do not bind insurance, approve credit, guarantee transport or certify surveys, and the platform never claims otherwise. Partner fulfilment workflows are scoped work.
What is built is real
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 maps every control to the file that implements it and marks each as implemented or as a pre-launch hardening item. The named release gates are listed on the Development Company page.
See how Miracuves compares to agencies and freelancers
The deployment process, a modelled 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.
Frequently Asked Questions
Is this a charter booking platform?
How does search handle technical yacht criteria?
Can brokers manage their own inventory and leads?
Is it multi-currency and multi-language?
Does it work on mobile?
What are the eight marine service modules?
Open the demo rather than take our word
Every role has a working login and no setup is required. Search as a buyer, send an inquiry, then pick the same lead up in the broker workspace and watch it appear in the operator console.
Explore the YachtWorld Clone
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 →