A premium rental marketplace asset built to be acquired.
QIX Rentals is offered at $2.5M as a luxury marketplace codebase with host tooling, service commerce, sponsor inventory, Stripe rails, Supabase integration, AI surfaces, and a production deployment path already in place.
Repository depth, product surface, and transfer scope.
The package is organized around reviewable product areas: marketplace routes, account surfaces, host operations, admin review, API handlers, payment routes, Supabase integration, tests, and deployment gates.
App Router pages
77
Public, auth, guest, host, admin, and onboarding surfaces
API route handlers
30
Checkout, Connect, messages, search, Mapbox, admin, host, AI
Test files
7
Search, pricing, auth redirects, admin access, messaging, URLs
Quality scripts
8
Lint, typecheck, test, build, Stripe check, scans, audit, deploy gate
Included code and operating assets
Operating systems already separated for buyer review.
The codebase is not a single landing page. It includes marketplace, host, admin, payment, trust, discovery, and AI surfaces that can be inspected independently during diligence.
Systems ledger
Implemented stack
Authentication and role flow
Supabase SSR/browser clients, sign-in/sign-up/reset flows, host-intent onboarding, dashboard redirects, owner-admin gating, and protected account/workspace layouts.
Payment and payout flow
Stripe Checkout for stays, services, host plans, boosts, advertiser packages, and donations; Stripe Connect account link, status sync, payout settings, portal, and webhook routes.
Marketplace operations
Listing forms, media handling, host service submissions, service approvals, support intake, message validation, booking pricing, search filters, recent views, and concierge request action.
Trust and request protection
Shared API guard for same-origin checks, JSON enforcement, body-size limits, per-route rate limits, Zod validation, safe redirect helpers, and production request URL handling.
Location and discovery
Mapbox static map route, location suggestion route, language/country handling, predictive search, destination pages, collection pages, and seeded luxury listing inventory.
AI readiness
AI virtual agent surface and host listing optimizer route are present, with server-side provider key gating so generated copy is not fabricated before provider configuration.
Asset groups
Marketplace product
Premium rental discovery, listing detail pages, collections, destinations, checkout flow, concierge entry points, and editorial content structure.
Host operating system
Host dashboards for listings, pricing, reservations, services, payouts, analytics, reviews, boosts, Pro Host membership, and AI optimization.
Revenue rails
Stripe checkout patterns for bookings, services, host subscriptions, boosts, advertising packages, donations, and Stripe Connect payout readiness.
Admin and trust layer
Admin approvals, flagged listings, service approvals, support workflows, owner-admin gating, audit-oriented API routes, and trust-first UX copy.
Technical foundation
Next.js App Router, TypeScript, Tailwind CSS, Supabase integration, Mapbox routes, Vercel deployment, security headers, sitemap, robots, and tests.
Brand and content system
QIX visual language, luxury page templates, listing media, editorial articles, sponsorship inventory, service marketplace copy, and buyer-ready positioning.
Close around code, accounts, and verified transfer scope.
The buyer should review exactly what transfers, which accounts require fresh buyer-owned credentials, and which third-party services need configuration before close.
Product and brand package
Buyer review should include the public marketplace, account surfaces, host workspace, admin routes, editorial pages, service marketplace, core visual language, copy system, and buyer-facing positioning assets.
Technical handoff package
Transfer planning should cover repository access, Vercel project setup, environment variables, Supabase configuration, Stripe configuration, Mapbox usage, AI provider settings, and deployment workflow.
Operating transition package
A closing plan can include an asset schedule, account checklist, launch priorities, known configuration requirements, diligence notes, and transition support for buyer engineering or operations teams.
Offer console
Structured paths
Clean acquisition
$2.5M cash purchase
Buyer receives the codebase, brand materials, deployed application setup, data/content assets, and transition support subject to final asset schedule.
Structured consideration
$2.5M purchase plus 1.5% revenue share
A 1.5% share of gross platform revenue may be included for up to 36 months, subject to a negotiated cap and final purchase agreement.
Strategic earn-out option
Negotiated closing payment plus milestone upside
Lower closing cash with defined performance payments tied to launch, inventory onboarding, transaction volume, or advertising sales milestones.
Handoff requirements
Review tracks before final signature.
The offer should be reviewed like an acquisition, with records and counsel. The valuation is anchored to the asset package and should be supported by buyer diligence, legal review, and a clear schedule of transferred assets before final terms are signed.
Review tracks
Diligence file
Financial diligence
Any revenue, traffic, customer, booking, host, advertiser, or pipeline claim should be validated separately with buyer-requested records before final valuation is confirmed.
Legal and IP diligence
Buyer counsel should confirm source-code ownership, brand rights, image usage, domain control, account transferability, third-party service terms, and any exclusions from the final asset schedule.
Technical diligence
Buyer engineering should review the repository, deployment path, environment requirements, database assumptions, payment routes, security posture, and any production-readiness items before close.
Closing checklist
Request the diligence packet and asset schedule.
Serious buyers should review the repository, deployment, environment requirements, transfer list, account ownership, and legal asset schedule before submitting final terms.