CleanTitle Housing

What it is

A recorded title, a move-in receipt, a guest list, a rent history, and an open house you can host — designed to work with the interiors you already run. When a housing dispute erupts, the record settles it. For owners who want property to mean ownership, not a menu entry. Designed for Qbox, QBCore, and ESX Legacy through ForgeCore. Escrow split publishes with the file-level manifest at release. In development; no runtime proof published — pending Shadow bench.

The problem it exists for

Property is the most valuable thing a player owns and usually the least documented. Ownership lives in one table, keys in another, and the sale that transferred it lives nowhere at all — so a dispute about who owns a house is unanswerable and an admin ends up adjudicating from memory. The second failure is quieter and worse: two players buy the same house in the same second, or rent charges twice on one cycle, and nothing in the system can tell you afterwards which of those things happened.

Why we're building it

Ownership only means something if it's provable. We're building housing the way we built the money engine: a record you can reconcile, where a transfer leaves a trail and a restart doesn't quietly change who lives where. The other decision worth stating out loud is what it refuses to own — we are building the ledger, not the building. A housing system that insists on shipping its own interiors collides with the MLO pack and door-lock script half the servers it's sold to already run, so ours is designed to take coordinates and an interior id you supply and stay out of the way.

What it's designed to do

Design intent, not shipped behaviour — none of this has been built yet.

• Designed so ownership and transfer produce a record, not just a state change — a sale you can look up later rather than a row that used to say something else.
• Designed to survive restarts without drift, under the same money discipline as the banking ledger: integer amounts, an append-only trail, and the mutation held long enough that two simultaneous buyers cannot both win.
• Designed so keys, access and ownership are one coherent story rather than three tables that disagree — tiered access for a roommate, a friend and a guest, granted from the same record that says who owns the place.
• Designed to be interior-agnostic: no MLO, shell or interior asset ships with it and none is required, because a property here is a config entry with coordinates and an optional interior id you provide.
• Designed so an organisation can hold property the same way it holds a treasury, with rent as an audited money sink on a schedule rather than a decorative timer.

What is not proven

The section every product page should have and almost none do.

• It is not released and not purchasable. There is nothing to buy or download, and no server of ours to look at it on.
• No runtime proof published — pending Shadow bench. The concurrency claims above — one buyer wins, rent charges once — are exactly the kind that only a bench can settle, and it has not been published.
• No resmon figure — [MEASURED-PENDING].
• $39.99–44.99 is a planned band, not a price, and not a commitment until the studio pricing lock.
• No release date.

What we're building toward

Keys handed over, the door swings open, and a title certificate stamps "CLEAR."

Current status, stated exactly

• resmon [measured-pending]
• escrow manifest — at release
• framework support — decided at build, published at release
• open-vs-escrowed manifest — published at release, file by file

What to verify before buying any player economy resource

This applies to every product in this category, ours included, whenever it arrives. Hold CleanTitle Housing to exactly these when it launches — and if it fails one of them, don't buy it.

• Ask what happens to ownership on a restart mid-transfer. This is the same crash-atomicity question that decides whether a money system is real (see /guides/stress-test-fivem-economy-scripts).
• Ask whether a sale leaves a record, or only changes a row. If the only artefact of a sale is that the owner column now says someone else, every dispute about the price or the terms lands on staff.
• Ask what happens when two players buy the same property at the same moment, and what happens if rent runs while a player is mid-purchase. Vendors who have thought about it will answer immediately; vendors who have not will tell you it can't happen.
• Ask whether it requires its own interiors. A housing script that ships or mandates an MLO is a housing script that will fight the interior pack, the door locks, and the shell system you already run.
• Our July 2026 survey recorded one USD housing price, $58.00, plus a €34.99 listing we did not convert. That's an anecdote, not a market rate — verify current prices yourself (see /guides/fivem-script-prices).

Universally: ask for the measured resmon figure with its method and date, the exact list of which files ship open versus escrowed, a dated changelog, and the refund window. Four answers. Any of them missing is an answer too.