9flats Clone Features: Built Around the Host
A short-stay marketplace lives or dies on whether hosts stay. Onboarding, calendars, pricing rules, booking rules and payouts are the spine of this platform, and guests search and book against them. Here is every capability, grouped by who touches it.
Request a Live Demo →See PricingFeature Set by Role
Every capability grouped by who actually touches it - the host listing and getting paid, the guest booking against their calendar, and the operator approving, moderating and settling.
Host Console
- Rich property profiles with gallery and video
- Multiple room types with independent pricing
- Occupancy limits and bed configuration per room
- Seasonal and date-based rate adjustment
- Length-of-stay discounts and extra guest charges
- Minimum and maximum stay, advance booking window
- Cleaning fees and security deposits as extras
- Earnings net of commission, payout requests
Guest App
- Search by location, dates, guests, price and amenities
- Autocomplete on locations and listings, plus map view
- Sort by price, rating or distance
- Star rating, check-in windows and house rules
- Partial payment for deposit-based bookings
- Balance reminders before arrival, invoice generation
- Direct messaging with hosts, read receipts, file sharing
- Reviews, wishlists and booking history
Operator Admin
- More than twenty admin modules
- Host approval and listing moderation
- Granular role and permission system
- Commission set globally or per host
- Coupons with usage limits and minimum totals
- Payout queue with review and completion
- Featured listing placement sold as promotion
- Six further service types, switched on when you want them
9flats vs Miracuves Clone vs Building From Scratch
The same capability, three different paths - weighted toward what a host-led operator actually needs.
| Capability | Original 9flats | Miracuves Clone | Build From Scratch |
|---|---|---|---|
| Apartment and private-room inventory | Yes - the core product | Room types with independent pricing, occupancy and bed config | The part everyone starts with |
| Host onboarding and approval | Yes | Application, moderation queue and per-host commission | Commonly an afterthought, then rebuilt |
| Calendar integrity | Yes | Validated at request time, room-level sync inside a property | Cached availability flags are how double-bookings happen |
| Pricing rules | Yes | Seasonal rates, length-of-stay discounts, extra guest charges, coupons | Where totals start disagreeing between screens |
| Host payouts | Handled by 9flats | Earnings net of commission, host-requested, operator-reviewed | The line item most underestimated |
| Commission control | Set by the platform | Set by you, globally or per host, stored on each booking | Retrospective changes corrupt historical payouts |
| Other inventory types | Stays only | Six more ship switched off - cars, tours, boats, events, flights, spaces | A second booking model per type |
| Languages | European focus | Fifteen pre-configured, per-entity content, RTL for Arabic and Hebrew | Interface strings only, then a retrofit |
| Source code ownership | N/A | Full Laravel 10 source, no encrypted files | Full ownership (you are building it) |
| Price | N/A | $2,499 one-time | Six figures and a year, typically |
The row worth dwelling on is the last inventory one. You can launch as a pure stays marketplace and enable tours or mobility later from the admin, without a rebuild, because all seven types share one booking, payment and payout path.
How It Works, End to End
Follow a host from signup to payout - the path that decides whether they list a second property.
Onboard and list
A host applies, you approve them in the moderation queue, and they build a listing with gallery, video, room types, occupancy limits, bed configuration, house rules and check-in windows. Commission can be set for that host specifically rather than globally, which is how you give anchor supply a better rate without repricing the marketplace.
Set the rules, not just the price
Seasonal and date-based rates, length-of-stay discounts, extra guest charges, cleaning fees and security deposits, plus minimum and maximum stay and an advance booking window. These are the levers a serious host expects, and their absence is the usual reason a host goes back to the incumbent.
The calendar holds
Availability is validated at request time against the per-service date tables and existing bookings rather than a cached flag, and room-level synchronization prevents a clash inside a single property. Where you also sell through OTAs, iCal export keeps external calendars in step.
Guest books and pays
The total resolves once through the pricing engine, any coupon is checked against its usage limit and minimum, and payment runs through one of six gateways or the internal wallet - in full, or as a deposit with an automatic balance reminder before arrival. No card number reaches your database.
The host gets paid
Commission is written onto the booking at the moment it is made. Earnings accumulate net of that stored rate, the host requests a payout from their dashboard, and you review and complete it in the payout queue. Raising your commission later affects future bookings only and never rewrites what a host already earned.
Step five is the one hosts talk to each other about. A platform that recalculates historical earnings when the operator changes a rate loses its supply base quickly, and it is not recoverable.
Every Feature Earns Its Place
Nothing here is on the list because it demos well. Each capability exists because leaving it out costs you hosts.
| Capability | Why it is not optional |
|---|---|
| Commission stored on the booking | Because a rate looked up at payout time means raising your commission silently re-prices every historical booking, and no host will trust your reporting again. |
| Per-host commission | Because your first twenty hosts are worth more than your hundredth, and you need a way to reward them that does not reprice the whole marketplace. |
| Room-level synchronization | Because a property with four room types is four inventories, and a clash inside one property is invisible to a property-level check. |
| Availability checked at request time | Because a cached availability flag is how two guests book the same room, and the host is the one who has to turn someone away. |
| Seasonal and length-of-stay pricing | Because a host who cannot price a peak week or reward a longer booking is being asked to earn less than they do elsewhere. |
| Deposits and partial payment | Because deposit-based bookings are normal in short-stay, and demanding the full amount up front loses both hosts and guests. |
| Host payout queue | Because money moving to a host should have a deliberate, reviewable step, and because a refund after a payout is the question every operator eventually faces. |
| Per-entity translation | Because a localised shell around listings nobody in that market can read converts nothing, and European city markets are multilingual by default. |
| Magic-byte upload inspection | Because hosts upload property documents and photos constantly, and an extension check trusts a filename the uploader controls. |
The Technology Behind the Features
A deliberately mainstream stack: PHP 8.1+ on Laravel 10 as a modular monolith with more than twenty domain modules, Eloquent ORM with parameterized queries throughout, and Sanctum tokens plus JWT for API authentication. Data sits in MySQL 8 or MariaDB across 40+ tables, with a polymorphic booking model spanning all seven service types, composite indexes on the polymorphic pairs and full-text indexes on searchable content. The public marketplace is Blade with Vue.js components in the admin surfaces, mobile is Flutter for Android and iOS from one codebase consuming the same REST API, and realtime messaging runs on Pusher with Chatify. Redis handles cache, session and queue drivers with workers under Supervisor, and media goes to S3 or GCS behind Nginx.
None of this is exotic, and that is the point: any competent Laravel developer can maintain it, so you are not dependent on us to keep it running.
What Is Not Included in the Base Package
Everything above is in the base platform and demonstrable in the live demo. These are not, and we would rather you knew before you bought.
Stated against the feature, not implied away
- Two-way channel managerAn add-on, not base. iCal export ships for one-way calendar sync.
- Dynamic pricingAn add-on rather than a shipped feature.
- Local payment rails beyond the sixA customization, though gateways sit behind a common interface.
- Custom OTA or PMS integrationsScoped and quoted separately.
- ISO 27001We do not hold a certificate and do not claim one.
- Merchant accountsEach gateway you enable needs your own account and approval.
- Listing contentPhotography, descriptions and per-locale copy are yours to supply.
- Custom work beyond the baseQuoted at 2 to 8 weeks depending on scope.
Where a control is configuration rather than shipped, the security documentation says so plainly rather than presenting a clean-looking table - see the Platform Trust section on the Development Company page.
See how Miracuves compares to agencies and freelancers
The deployment process, a named client deployment in Italy, and what to check before you hire anyone - on the Development Company page.
Frequently Asked Questions
Can I launch as a stays-only marketplace?
Can I change the commission rate later?
How does the platform stop double-booking?
How do host payouts work?
Which payment gateways are included?
Can I run this in more than one language?
See exactly what you are getting - before you commit
Request a working demo of the host console, the calendar and the payout queue, or check exact pricing.
Explore the 9flats Clone
Ready to launch a marketplace hosts will stay on?
Deploy in 6 days with the host console, the calendar and the payout pipeline included, full Laravel source on hosting you own.
Talk to Us →