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

Feature scope - proposed scope

White Label Fractional Real Estate Platform Features: AED, USD, GBP

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.

Scope areas for this kind of build

Fractional Ownership Features for Investors in Several Countries

Six capabilities that separate a platform serving three markets natively from one that shows a dollar system through a currency picker.

Each market keeps its own base currency

  • Currency lives on the country profile, so a Dubai offering whose price, rent roll and payouts are all in dirhams stays in dirhams from listing to statement. Nothing is stored in dollars and re-expressed for the screen, which means the figure an investor subscribes at is the figure your books carry.

A wallet per currency, balances from the ledger

  • A co-owner may earn in dirhams, save in dollars and file taxes in sterling. The wallet keeps a balance for each currency, computes every one of them from ledger entries, and quotes conversions from a bounded rate cache, with deposit and withdrawal flows on each.

Tickets and eligibility set country by country

  • The UAE, the United States and the United Kingdom arrive as preset profiles. You decide each market's minimum ticket and the investor test that applies there, so a lower entry amount for Gulf retail buyers and a stricter gate somewhere else are settings, never a second codebase to maintain.

A single owner register for every jurisdiction

  • Every fraction allocated is appended to one register and backed by a certificate, audit search and double-entry books. When a regulator in one country or a buyer of your business asks who held a building on a past date, you run a query instead of stitching several systems back together.

A portal where developers submit buildings

  • Developers and brokers feed properties into your pipeline through their own portal: a submission, a relationship record and a draft property that underwriting takes over. Across the Gulf, supply tends to arrive through relationships, and this screen is where those relationships land instead of an inbox.

One Building, Investors in Two Currencies, Listing to Payout

The order in which a cross-border deployment works, with the platform refusing to skip a stage.

Configure the market

  • From the console you create or edit a country profile: the currency that market prices in, its minimum ticket, its investor test and which of the eight locales appear there. No developer is involved, so launching a second or third country is a business decision with a settings screen behind it.

Receive and underwrite the building

  • A developer or broker enters the property through the partner portal, which opens a relationship record and a draft listing. Your team loads assumptions, reads bear, base and bull outputs, and records the investment committee decision as its own evidence. Investors see nothing until that decision exists.

Clear the investor for their country

  • Sign-up creates the user, the investor, a wallet and a ledger account in one transaction. A KYC case goes to the verification vendor you connect during delivery, accreditation and a risk questionnaire set suitability, and investor class together with country profile decide which offerings that person may buy and the smallest ticket allowed.

Pay rent pro rata in one run

  • Rent received and expenses roll into a single distribution batch showing gross, tax, fee and net per holder. A holder in another currency is converted inside that run from a bounded rate quote. Compliance reviews, finance approves, and execution posts balanced entries with statements attached.

Give holders a way out

  • Three governed routes exist: list the fraction on the secondary market with an investment memo, negotiated offers and atomic transfer; request redemption in a scheduled exit window that checks holding period and eligibility; or vote, weighted by shares, on selling the whole building. Every route writes to the same register, so the cap table never goes stale.
  • All six stages share one domain of 77 models behind 229 API routes. A holder's statement in sterling, a payout report in dirhams and an audit search in the console therefore describe the same facts, with no reconciliation step between them.

The Stack That Makes Several Markets Possible

Serving three currencies and two text directions is settled in the architecture, not on a preferences screen. This is where each piece sits.

Each layer is a mainstream hire in the Gulf and elsewhere, and the schema moves to any PostgreSQL host. That counts for a lot here, because the platform has to outlast every holding recorded on it.

Boundaries we state in writing for your build

A cross-border investment platform invites assumptions about licensing, client money and readiness. Here is where each one stops, beginning with the one that decides whether you can launch at all.

Permission to operate in each market

  • Buying and deploying the software is not a regulatory step. Selling fractional property interests is regulated in the UAE, the US, the UK and most other markets, under securities, crowdfunding or collective investment rules that differ by country. You obtain the license, registration or exemption for every market you accept investors from, and you set up the legal structure of each property. We supply software, not permission to operate.

Custody of investor money

  • The platform records money; it never holds or safeguards it. Client-money and custody arrangements sit with a bank, trustee or licensed institution you appoint, and no feature replaces that. A vendor claiming otherwise should be asked which institution actually holds the funds.
  • The build's own security review says it is not production-ready. Admin surfaces rely on one binary role check despite a thirty-role catalog, payment callbacks use a custom digest that falls back to a sandbox secret, the KYC callback accepts a fixed sandbox signature, and the advertised lockout and password policy is inert. All four are closed during delivery hardening, and no investor should meet the platform before then.

Sanctions and PEP screening

  • Nothing screens anyone at runtime, and nothing on this page implies it does. Connecting a screening provider, deciding how matches are handled and building the review queue is a defined project, and most regulators will expect it in place before you operate.

Several brands per install, or staff SSO

  • There is no tenant isolation, so one deployment carries one operator brand: yours. Running more brands means separate deployments or scoped architecture work, and putting console access behind your own identity provider is an add-on that institutional diligence usually raises.

Choosing who supplies a cross-border platform

  • Questions to put to any fractional property software provider, the answers that should end the conversation, how our delivery runs, and a modelled Gulf operator serving three currencies, all on the Provider page.

Three markets, one register, your source.

The platform underneath the fractional property clones: country profiles, Arabic right-to-left, wallets in AED, USD and GBP, and one append-only register behind every market, on your brand with the code in your hands.

Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by GetStake , Stake, Fundrise or any other fractional property investment platform.

Discuss this scope by message

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

team@omnistu.com