PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project

White-label

Yacht marketplace, white-labelled for you

A customizable yacht charter and sales marketplace. Original code, finished under your branding, scoped in writing before any build starts.

What it typically includes

How white-labelling works

Related reading

Scope areas for this kind of build

Overview

Every Lead Has a Clock

  • Each enquiry is logged with its source, stage and first-reply time, so a slow broker shows up on the dashboard.

Specs Deep Enough for a Yacht

  • Ready to put a yacht marketplace under your own name?

Moderation, Plans, Service Desks & Reporting

  • Where the platform is governed: users and brokerages, listing moderation, plan editing with activate switches and subscriber counts, taxonomy and settings, the eight marine service desks, articles and FAQs, tickets, disputes and the analytics dashboard.

Expo Build - The Same Marketplace in Your Pocket

    Modelled Reference - A Brokerage Group on Its Own Marketplace

    A modelled reference showing how the platform is set up for a brokerage group running its own branded marketplace. It is not a client engagement, and every figure describes the software rather than a result a customer reported.

    Marine Sector Branded Brokerage Marketplace

    What Is a White Label Yacht Marketplace?

    A white label yacht marketplace is a finished marine marketplace you publish as your own. Buyers filter vessels by make, length, draft, engine hours and location, line up a shortlist side by side, save searches that email fresh matches, and send enquiries that arrive as structured leads rather than loose emails. Brokers keep their stock current, move each lead through stages, answer inside a thread and attach alternatives from their own client files. The operator moderates supply, sets the plans and runs eight marine service desks.

    More Than a Listings Grid

    • A listings grid is the easy part. What this adds is the lead lifecycle, the broker's client records and the service desks - the pieces a classifieds template leaves you to invent.

    Owned, Not Licensed

    • The whole monorepo, the Drizzle schema and its migrations transfer to you. There is no seat fee, no dependence on our roadmap, and plain PostgreSQL underneath.

    Built Around the Vessel

    • Hull material, keel, rig, displacement, berths and engine hours are real fields with their own filters. It is neither a property template relabelled for boats nor a charter booking tool.

    Marketplace First, Charter Second

    • This category is hard in a few specific places, and those are the places already solved here: a listing record detailed enough for a seven-figure asset, search that mixes technical ranges with a map radius, a lead that keeps its history as it passes between people, and a console someone without an engineering background can run.
    • Specification-rich vessel listings with media, video and price history
    • Technical, geographic and status search with facets and sorting
    • Structured inquiry pipeline with response-time measurement

    Features - Vessel Listings, Search, Leads, Broker CRM & Services

    Accounts & Roles

    • Sign-up with a chosen role, JWT sessions, bcrypt-hashed passwords, reset and email verification for buyers, sellers, brokers and admins.
    • Sign-up with name, email and a chosen role
    • Bcrypt-hashed passwords and JWT sessions lasting seven days
    • Password change, plus forgot and reset with an expiring token

    Two-Factor & Data Rights

    • Title, make, model, year, price and listing currency
    • Length overall, beam, draft and displacement
    • Condition, type, category, fuel and hull material
    • Engines: description, count, hours and horsepower

    The Vessel Record

    • More than forty real fields covering identity, dimensions, machinery, accommodation, performance, tankage, rig and location.
    • Photos in a set order with captions and a cover image
    • Multipart uploads checked for size and file type
    • A video tour link that plays inside the gallery

    From Active to Sold

    • Three sale states with sold price and date, a price history that only appends, price-drop badges and upgrade flags that expire.
    • Keyword search over text, make and model
    • Filters for type, category, condition and make
    • Ranges on price, year, length, beam, draft and engine hours

    Technical Search

    • Keywords, taxonomy, numeric ranges and a map radius in one query, with facet APIs, sorting and stable paging.
    • Favourites to add, remove and review
    • Side-by-side compare on web and mobile
    • Named saved searches stored as JSON criteria

    Saved Searches & Alerts

    • Favourites, compare, named saved searches with an alert rhythm, the job that finds new matches, and recommendations.
    • Enquiry capture with rate limits and guest contact details
    • Subject, message, source and intent on every lead
    • Status, stage, private notes and reply fields

    Lead Pipeline

    • Rate-limited capture with source and intent, stages, private notes, a kanban board and a measured first reply.
    • Messages kept inside each enquiry, with conversation summaries
    • A signed-in inbox with unread counts and mark-as-read
    • Sender, role, name and time on every message

    Threads & Live Updates

    • Threads tied to each enquiry, an inbox with unread counts, a live SSE stream with heartbeat, and Web Push once VAPID is set.
    • Brokerage directory and profile pages with branding, bio and contacts
    • Regions served, specializations and languages
    • Ratings, review counts and a verified badge

    Qualification & Market Data

    • LeadSmart qualification with an adjustable intent threshold, listing scores, response-time benchmarks, valuations and sold comparables.
    • Public plan pages with tier and intended audience
    • Monthly and annual prices, display order and a popular flag
    • Listing and featured-slot limits stored in plan JSON

    How a Yacht Marketplace Earns - Plans, Upgrades, Leads & Licensing

    A yacht marketplace earns from several lines at the same time, and each one is modelled on its own so you can adjust one without disturbing the rest. Broker subscriptions and listing upgrades carry the most weight: the first is recurring and predictable, the second grows with how much stock brokers want pushed to the front.

    Broker Subscription Tiers

    • Tiers aimed at a chosen audience, with listing limits and featured slots set in plan JSON. Subscription records hold status, period and billing cycle, and the console edits plans and counts subscribers.

    Featured & Spotlight Placement

    • Spotlight and enhanced placements with start and end dates, shown in search and on the listing page. The per-listing upsell that sits beside the recurring plan.

    Marine Service Referrals

    • Charter, insurance, transport, finance, survey, valuation and boat-show intake can be charged as referral fees, per-lead prices or lead bundles. The software supplies the intake and the desk; the commercial terms are yours.

    Boat Show Packages

    • Show pages with RSVP and interest capture feed an operator desk, which is what organizers sell exhibitor presence and lead packages against.

    Paid Broker Tooling

    • LeadSmart, the optimizer, response-time reporting and market reports fit naturally into upper broker tiers instead of being handed to every level.

    Regional Licensing

    • Brand, taxonomy, plans, content, currency, language and active modules are all settings, so selling branded regional instances is a sales job, not an engineering one.
    • Where commerce stops: choosing a plan, billing-cycle records, checkout and cancellation are built, and invoice history is a generated six-row mock. Connecting a live provider such as Stripe or Adyen is a standard configuration step rather than a gap, and we quote it with your deployment.

    Operator Console - Supply Moderation, Plans, Service Desks & Reporting

    The console covers users and brokerages, listing moderation, plans and packaging, taxonomy and settings, all eight service desks, content, trust cases and reporting. It is the part most marketplace builds postpone and never quite finish.

    Headline Totals

    • Total and active listings, brokerages, users, enquiries, messages, views and subscriptions, on one dashboard.

    Six-Month Trends

    • Six months of user and listing growth, calculated from stored records rather than a separate reporting copy.

    Broker League Table

    • Listings, enquiries and plan value compared broker by broker, which makes performance reviews concrete.

    Users & Brokerages

    • Find, page, edit and remove users, plus brokerage records and the moderation of their listings.

    Supply Moderation

    • Every listing in one collection, with moderation actions for stock that should not go public yet.

    Tiers & Subscribers

    • Create and edit plans, switch them on or off, see subscriber counts, and review broker and user subscriptions.

    Eight Service Desks

    • Insurance, transport, finance, charter, survey, valuation, boat-show and sell leads, each with its own status workflow.

    Content, Settings & Taxonomy

    • Articles, FAQs, help pages, platform settings, and the taxonomy for boat types, categories, conditions and features.
    • Users: list, search, page, edit and remove
    • Brokerages: list, edit and moderate their listings
    • All listings with moderation actions

    Tickets & Disputes

    • Tickets with category, priority, owner, attachments and threaded replies, plus disputes with evidence and a ruling from the operator.
    • Desks for insurance, transport, finance, charter, survey, valuation and events
    • Articles and FAQs with create, edit, delete and publishing
    • Surveyor and boat-show management

    What an engagement can include

    What transfers is a complete, deployable platform: the application source, the schema underneath it and the documents a technical buyer will ask for. Ownership is full, with no runtime licence, no seat fee and no tie to our roadmap.

    Web Marketplace

    • The React and Vite single-page app: 46 routes, TypeScript, Tailwind and generated query hooks.
    • A React and Vite web app with 46 routes
    • TypeScript end to end with a Tailwind component library
    • Public, account, marketplace, service and dashboard routes

    Mobile App

    • The Expo React Native app with tab navigation, detail screens and EAS build profiles.
    • TanStack Query hooks generated by Orval from the OpenAPI file
    • Zod schemas generated from the same contract
    • One shared fetch layer that injects the token

    Operator Console

    • The admin-only surface for moderation, plans, taxonomy, service desks and reporting.
    • An Expo React Native app using Expo Router tabs
    • Screens for listings, brokers, charter, boat shows, surveyors and valuations
    • A dashboard each for buyer, seller, broker and admin

    API & OpenAPI Contract

    • An Express 5 API: 203 handlers in 35 route modules
    • JWT auth with role and brokerage middleware
    • A global rate limit plus tighter limits per route
    • Structured Pino logs with query strings redacted

    PostgreSQL Schema

    • Forty PostgreSQL tables in thirty Drizzle modules, with JSONB only where a flexible shape earns its place.
    • Thirty schema modules, JSONB for flexible fields
    • Price history that only appends, and dated listing views
    • The background job behind search alerts

    Deployment Kit

    • Docker, Compose, Nginx, PM2 and EAS profiles, so launch is a configuration task rather than a packaging project.
    • A multi-stage Docker image on Node 24 with pnpm
    • Compose running the app beside Nginx
    • Nginx with gzip, long-lived static caching and baseline headers

    Ten-Document Set

    • Ten documents: requirements, data model, API surface, security posture and compliance.
    • EAS profiles for development, preview and production
    • A health endpoint for probes and monitoring
    • A written path to scale rate limits, SSE and storage

    Post-Launch Support

    • The full source, owned outright, with no runtime licence
    • A product requirements document and an ERD
    • A schema reference and an API collection
    • A developer and security handbook and a VAPT posture paper

    Who Is a White Label Yacht Marketplace For?

    It fits operators who sell high-value stock to buyers who decide over months, not minutes, and who need that long decision to stay inside one system from first search to offer.

    If your margins depend on lead quality, on how fast brokers reply, and on service demand that currently leaks to partners with no record, an owned yacht marketplace becomes a lasting asset instead of a brochure site with a contact form.

    Use Cases - Brokerages, Aggregators, Service Desks & Boat Shows

    Which module leads decides what kind of operator you are. A brokerage group leans on stock, pipeline and client records. An independent marketplace leans on plans and upgrades. A services business leans on the eight intake desks. All three are configuration, not separate builds.

    Since taxonomy, plans, content, currency, language and active modules are all in the operator s hands, one codebase can appear as a premium single-brand portal in one deployment and a neutral multi-dealer marketplace in the next.

    Why Own a Yacht Marketplace in 2026?

    Generic classifieds software has served premium marine poorly for years. A yacht is not a stock item: photos, technical specs, service records, survey evidence, provenance and the broker s name all carry weight, and a platform that squeezes all of that into a price and three pictures leaves buyers unsure and brokers slow.

    Buyers Take Months

    • Buying a yacht takes months. The platform that holds the buyer's attention through saved searches, alerts and a broker relationship is usually the one that closes the sale.

    Response Speed Wins

    • The same boat often sits on several portals at once. What sets an operator apart is how fast a lead is qualified and answered, which the pipeline and response-time metric track.

    One Sale, Several Services

    • Every vessel sale pulls in insurance, transport, finance, survey and valuation. Capturing that in one system turns a single deal into several revenue events.

    Buyers Cross Borders

    • Yacht buyers shop across borders. Six display currencies and five interface languages are in an initial scope rather than a phase-two project.

    Keep the Buyer Data

    • Pushing stock to other portals rents you reach and leaves the data with them. An owned platform keeps the searches, saved criteria and conversations.

    Broker Hours Are Margin

    • An hour spent rebuilding context from an inbox is margin gone. Client records, shortlists and a staged pipeline give that hour back to selling.

    The Build in Numbers

    • The slow part is building the layer that handles this properly: a listing record rich enough for the asset, search that mixes technical ranges with a map radius, a lead that survives changing hands, and a console a non-engineer can run. Each is unglamorous, necessary and slow to get right.

    Technology options we may propose

    A marketplace like this needs a schema indexed for the searches people actually run, one contract that keeps three clients in step, and deployment files nobody has to reinvent. This is what sits underneath.

    For technical buyers: the code is laid out so your team can extend it without a fight. Each of the 35 route modules owns its handlers and schema, the OpenAPI file regenerates both clients, and every integration point (payments, SMTP, VAPID, exchange rates, object storage) is a documented seam rather than a hard-wired vendor.

    How It Works - Search, Enquire, Qualify, Close

    From the outside it looks like a grid of boats. Underneath, it is a sequenced pipeline of discovery, qualification, conversation and oversight. This is the route from a first search to a vessel under offer.

    From First Search to a Vessel Under Offer

    • A buyer arrives from search or an alert and narrows a large catalogue down to a handful of candidates.
    • Keyword search across text, make and model with facet APIs for make, type and location
    • Range filters on price, year, length, beam, draft and engine hours
    • Country, state and geospatial radius filtering with sorting and pagination

    How we would approach the architecture

    The Listing at the Centre

    • Photos, price history, views, upgrades and enquiries all attach to the listing, so a broker dashboard, a search facet and a price-drop badge need no outside joins.

    Realtime on Its Own Route

    • SSE is mounted ahead of the main router with its own heartbeat and disconnect cleanup. Delivery is process-local on purpose, and the move to shared pub/sub is written down.

    Typed Queries Throughout

    • Drizzle provides a typed schema and parameterized queries over all forty tables, with JSONB kept to the few places that need a flexible shape.

    Authorization in the API

    • JWT role claims and brokerage middleware guard the broker side, and hiding a button is never treated as a permission check.

    Scaling - Search Indexes, a Stateless API & a Written Growth Path

    Ordinary at the edges and specific where a high-consideration marketplace needs it: a stateless API tier, a relational model indexed for real search queries, and a written route from a single-node launch to horizontal scale.

    Search That Holds Up as Stock Grows

    • One query path handles keywords, taxonomy filters, numeric ranges and a map radius together, and that query shape decides whether a marketplace feels quick at ten thousand listings or at two hundred thousand.
    • Make, type and location facets come from their own endpoints, so changing a filter does not force a full recount of results.
    • Ranges on price, year, length, beam, draft and engine hours
    • Separate facet endpoints instead of counting in the browser

    An API That Keeps No State

    • The only thing held in memory is the SSE connection map, which is why the written scale path swaps it for shared pub/sub instead of pinning users to one node with sticky sessions.
    • Rate limiting runs in-process at launch and moves to a shared store once there is more than one instance. The documents say so rather than presenting a single node as endlessly elastic.
    • Bearer tokens instead of server-side sessions
    • A shared rate-limit store as the first step to more instances

    When Media Outgrows the Server

    • Listing photos and video are the first thing to outgrow an application server. Uploads pass through one endpoint that checks size and file type, and the written next step is S3-compatible storage behind a CDN.
    • Because every upload already uses that one endpoint, moving storage is an adapter change, not a rewrite of every listing form.
    • One upload seam for web, mobile and admin
    • Object storage and a CDN as the planned growth step

    Hardening Before Real Traffic

    • The handbook lists these as pre-launch tasks rather than leaving an incident to reveal them.
    • Foreign keys, check constraints and status enums throughout
    • Indexes measured on the columns search filters by
    • Backups with rehearsed restores and monitoring

    Indexes Where Search Looks

    • Hardening adds foreign keys, checks, status enums and indexes measured on the columns buyers actually filter by.

    No Sticky Sessions

    • Tokens instead of server sessions, so growing means adding instances, not adding sticky routing.

    Media Moves Out First

    • One upload endpoint that checks size and type, with object storage and a CDN as the planned step when media grows.

    Scale Steps in Writing

    • A shared rate-limit store, shared pub/sub for SSE and object storage, named plainly instead of hidden behind the word cloud-ready.

    Containers or PM2

    • Compose with Nginx, PM2 on a virtual machine, or your own Kubernetes manifests. Files for the first two are included.

    Security and privacy requirements we can design for

    Buyer and broker records carry contact details, budgets and private notes, which makes subject-rights handling a launch requirement rather than a later project. Export and erasure are implemented and the remaining privacy work is named.

    Buyer accounts, broker workspaces, admin access and media uploads are all reached through the same contract, so authentication is enforced at the API rather than in the interface. UI visibility is never treated as an authorization boundary.

    Sign-In & Access

    • Bcrypt at cost 12, JWT sessions that expire after seven days, TOTP two-factor with a sign-in challenge, and role plus brokerage middleware.

    Parameterized Data Access

    • Parameterized Drizzle queries everywhere and allowlists on editable routes, so an unexpected field can never turn into a write.

    Redacted Logs

    • Structured Pino request logs with query strings redacted, so tokens and personal data stay out of log tools.

    Published Release Gates

    • The pre-launch gates are published, not hidden, which is the gap between an open foundation and a surprise in procurement. No certification or vulnerability-free claim is made.
    • For serious operators: the handbook ties every control to the file that implements it and marks each as built or as pre-launch hardening. The named release gates include removing the fallback JWT secret, finishing object-level ownership checks on every route that takes an identifier, encrypting TOTP secrets, hashing reset tokens, making scanned uploads private and a full privacy review across all forty tables. We would rather give you that list than have an outside tester find it.

    Add-Ons - Live Payments, Partner Hand-Off, Enterprise & Scale

    Payment Provider Hookup

    • Wiring Stripe, Adyen or a regional provider into the existing plan and subscription records, with hosted fields, webhooks, settlement, refunds, tax and real invoices replacing the mock history.

    Partner Hand-Off

    • Passing insurance, transport, finance, survey and valuation leads into partner systems with contracts, SLAs and status callbacks, instead of stopping at the operator desk.

    Object Storage & a CDN

    • Shifting listing media from the app server to S3-compatible storage with a CDN in front, usually the first change once media volume climbs.

    Staff SSO & Audit Trail

    • SAML or OIDC sign-in for staff, tamper-proof audit logs and access-review evidence for operators whose procurement asks for them.

    Dedicated Search Index

    • Moving faceted search to a dedicated engine once catalogue size and query load outgrow relational filtering.

    Catalogue Migration

    • Bringing across your current listings, media library, brokerage records and past enquiries from the platform you use today.

    Portal Feeds In & Out

    • Sending your stock out to other marine portals and taking broker feeds in, on whatever schedule and format each partner needs.

    Regional Instances

    • Separate regional instances or one multi-tenant deployment, each region with its own taxonomy, default currency and active service modules.

    Describe your Yacht marketplace

    Tell us your market and audience, and we will respond with a practical read on scope.

    team@omnistu.com

    More pages on this build

    4 pages describing this proposed build.