PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project
Omnistu logoOmnistu
Engagement scope - proposed scope

9flats Clone Development Company: How to Choose One

This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product, a fixed bundle or a fixed price.

Build scopeConfirm servicesDefine the features and exclusions
Delivery planAgree milestonesNo fixed launch duration implied
Source rightsWritten termsCheck licences and handover
OperationsTest before launchAgree acceptance and support
01 / Scope areas

Scope areas for this kind of build

The areas below are condensed from our earlier product specification for this category. They describe proposed scope we can build for you, not a finished product for sale, and no live system is implied. The exact list is agreed in writing for your project before any build starts.

02 / Compare routes

Agency vs Freelancer vs Omnistu

Three ways to get this kind of platform built. The Omnistu column describes the proposed base and delivery approach - proposed scope, not a standing price list. The other columns are the questions worth asking any provider you compare us against.

CriteriaFreelancer / generic scriptProposed Omnistu baseCustom dev agency
Time to launchAsk for a written timeline with milestonesDeployment timing agreed in writing before work startsScoped per build; ask for milestones
Host onboardingAsk how hosts are vetted and approvedProposed: application, moderation queue, per-host commissionAsk how hosts are vetted and approved
Calendar integrityAsk how double-bookings are preventedProposed: validated at request time, room-level sync inside a propertyAsk how double-bookings are prevented
Pricing tools for hostsAsk which pricing rules hosts can setProposed: seasonal rates, length-of-stay discounts, extra guest charges, depositsPriced per rule you specify
Commission handlingAsk whether the rate is stored per bookingProposed: stored on each booking; changing your rate never rewrites historyAsk whether the rate is stored per booking
Payout pipelineAsk how hosts request and receive payoutsProposed: earnings net of fees, host-requested, operator-reviewed queueAsk how hosts request and receive payouts
Room-level inventoryAsk whether rooms price independentlyProposed: independent pricing and occupancy per room typeAsk whether rooms price independently
Source code ownershipAsk whether you receive full, unencrypted sourceComplete source proposed, no encrypted files, upgrade scripts includedUsually yes; confirm it in the contract
CostAsk for a written quoteFixed figure, quoted in writing before work startsQuoted per scope

Swipe sideways to see all columns.

03 / Typical scoping questions

Typical scoping questions

Show me a host getting paid

  • Booking to bank account, including the review step. Then ask what happens to a refund after a payout has already been made - the answer tells you whether the ledger is real or decorative.

Can commission differ per host?

  • Your first twenty hosts are worth more than your hundredth. If the rate is global only, you cannot reward anchor supply without repricing everyone.

What happens inside one property?

  • A four-room property is four inventories. Ask specifically about room-level synchronization - property-level checks miss clashes inside a single listing.
04 / A proposed launch process

A proposed launch process, without time promises

Define the first service area

  • Where you operate, what you charge inside it, and any limits such as cash-on-delivery ceilings. The first zone usually becomes the template for the ones that follow.

Apply your branding

  • Name, logo, colour scheme and invoice layout applied across the storefront and apps. Which parts are configuration and which are build work is confirmed in the written scope.

Set the commercial rules

  • Commission or subscription structure, discount responsibilities, delivery pricing per zone, tax rules and payout preferences, recorded in the written scope.

Connect your own accounts

  • Payment gateways, store listings, maps and notification services stay under your own accounts, with access arranged before build work starts.
05 / Walk away

Red Flags and Fit Checks

Eight things worth pinning down with any provider - including us. Some are genuine warning signs; others are legitimate choices you should weigh deliberately rather than walk away from automatically.

What to listen for

  • Ask where the commission rate lives - stored on each booking, or looked up at payout time?
  • Ask whether commission can differ per host or is one global rate - and whether that fits how you will recruit supply.
  • Ask what happens to a refund after a payout has been made - the answer tells you whether the ledger is real.
  • Ask how availability is validated - checked at request time against the data, or read from a cached flag?
  • Ask which pricing rules hosts can set - one nightly rate, or seasonal and stay-length rules too.
  • Ask whether pricing includes a per-booking fee or a percentage of your commission, and weigh that against a fixed figure.
  • An ISO 27001 claim they cannot show you the certificate for.
  • Ask whether you receive complete, unencrypted source, and whether an annual licence is needed to keep it running - then weigh that fit.
06 / What a Short-Stay Platform

What a Short-Stay Platform Has to Get Right

Host trust in the numbers

  • Commission stored on the booking, so a rate change applies to future bookings rather than what a host already earned. One retrospective recalculation and your supply base talks to each other about it.

Calendar reliability

  • Validated at request time against date tables, with room-level sync inside a property. The host is the one who turns a guest away at the door, and they only do it once.

Payout predictability

  • Host-requested, operator-reviewed, with a deliberate human step before money moves. Slow or opaque payouts are the single fastest way to lose hosts to a competitor.

Money safety

  • The proposed design keeps card data off your database and calls for signature-verified payment webhooks - an unverified webhook marks bookings paid for anyone who finds the endpoint. Proposed controls, to be verified in the delivered build.

Upload safety

  • Magic-byte validation on host document and photo uploads rather than trusting an extension. Hosts upload constantly, and a filename is controlled by whoever sends it.
07 / Host Money

Host Money, Guest Data and What We Will Not Claim

Commission that stays as recorded

  • The rate is stored on each booking when it is made, and host earnings accumulate net of that stored rate. Payouts are host-requested and operator-reviewed, so a deliberate human step sits between a booking and money leaving your account.

No card data stored

  • The proposed design has the gateway take card details on its side, keeping the heaviest part of payment compliance off your infrastructure, with signature-verified payment webhooks - proposed controls, to be verified in the delivered build.
  • Guest personal data and host payout details are the parts that carry real risk in European markets, and they are the parts the proposed design documents most carefully - privacy designed in rather than bolted on before an audit.

Layered authentication and granular roles

  • The proposed design calls for strong password hashing, two-factor authentication, scoped API tokens, and a role system granular enough that an operations assistant is not one click from the payout queue - proposed controls, to be verified in the delivered build.

Parameterized throughout

  • The proposed design calls for parameterized queries throughout, HTML purification on rich content, and magic-byte validation on the property documents and photos hosts upload daily - proposed controls, to be verified in the delivered build.
08 / A partner who says

A partner who says what is configuration

Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by 9flats.

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

09 / FAQ

Frequently Asked Questions

Answers describe the proposed platform design and our delivery approach. Project-specific pricing, timelines and support terms are agreed in writing.

Is the platform secure enough for a real marketplace?

The proposed design carries bcrypt password hashing, two-factor authentication, role-based access control, API tokens, HTML purification on rich content, parameterized queries throughout, magic-byte file validation and signature-verified payment webhooks, with card data kept off your database. These are proposed controls to be verified in the delivered build, not claims about inspected code. We build to the controls the common frameworks require and say plainly what is configuration rather than shipped - we do not hold an ISO 27001 certificate and do not claim one.

Do you publish the mobile apps to the stores?

Yes, as a proposed service. Android and iOS builds would ship branded with your name, icon, splash screen and colour scheme, and store submission support - including review responses and the metadata reviewers ask for - is proposed as part of publishing support. What is included is confirmed in the written scope before work starts.

What support comes with it?

Support, bug fixes and updates are proposed options, with duration, response targets and cost agreed in writing before work starts.

How is this different from your Airbnb Clone?

Same proposed underlying platform, different framing. The Airbnb Clone page is written for operators leading with breadth - seven bookable service types on one engine. This page leads on the host: onboarding, calendars, pricing rules and payouts, with the other six types proposed as switched off until you want them. Choose by which description fits your business; the proposed source handover is identical for both, with the exact contents confirmed in the written scope.

Am I locked in to you after launch?

No, and the stack choice is deliberate. The proposed handover is the complete source with no encrypted files, plus schema, migrations and upgrade scripts, on your own hosting - the exact contents are itemized in the written scope before work starts. The proposed stack is mainstream on purpose, so any competent Laravel team can take it over. The proposed commercial scope has no runtime licence and no per-booking fee that would give us leverage over you later; your written quote states the actual terms.

Can you integrate the OTAs we already sell through?

Partly in the proposed base, partly scoped. One-way calendar sync (iCal export) is proposed in the base, which keeps external calendars in step for many small operators. A two-way channel manager is an add-on, and custom OTA or PMS integrations are scoped separately and quoted in writing before they start.

11 / Next step

Discuss your scope by message

Tell us what you want to launch and where. We reply by email with a scoped proposal - no calls required, no phone numbers collected.

PREVIEW ONLY - nothing you enter is submitted to or stored by Omnistu. The compose button tries to copy your scope text and open your own email app; if the copy does not work, the text appears below the button so you can copy it yourself. Nothing is sent until you press send in your own email app.
Email the team instead