Shipping daily
Nov 1DATAAll 646 projects re-verified: 6,419 developer claims tested against registers, courts and pressNov 1DATAMalaysia TEDUH and Philippines DHSUD licence checks: expired licences and approved delays foundNov 1DATAThailand ONEP register: 2 condos found selling before environmental approvalNov 1DATAMexico PROFECO contract register checks: one sales registration belonged to a laundryNov 1DATAAbu Dhabi ADREC inspections and RAK RERA permit list added: % built straight from the regulatorNov 1SHIPPEDNew stage filter: completed but still sellingNov 1SHIPPEDPublic database page: verification levels, disclosure distribution, every marketNov 1DATA+212 projects in one day, round 3: USA, Caribbean, Gulf, Africa, Japan, AustraliaNov 1SHIPPEDStage on every case: off-plan or under constructionOct 31SHIPPEDVerification level per check on every case card: registry, independent, developer, contradicted
Changelog →

Kolaboro / Data / Licence

Research and data licence

Most of what we collect is free to reuse. Some deeper material is shared on request. Either way, a few rules protect buyers, developers and the people named in public records.

Free for everyone

Open data under CC BY 4.0

You can copy, share, adapt and publish it, including for commercial work, as long as you credit Kolaboro and say if you changed it.

API

Open API

JSON endpoints for projects and markets, no key needed. Fields and limits are in the open data API docs.

CSV

Spreadsheet downloads

Projects CSV and markets CSV, plus the full JSON file the site runs on.

Feeds

Change feeds

The RSS feed of what we ship, per-market change feeds such as Bali, and the alerts feed for overdue or unapproved projects.

Licence text: Creative Commons Attribution 4.0 International. Data is offered as is, with the verification level of each check stated, and without any warranty.

On request

For researchers and funds

Academic researchers, journalists, consumer groups and investment funds sometimes need more than the open files. We can share some or all of the following.

Full change history

Every recorded change to what a project published, with dates. The open file carries only recent changes.

Page fingerprints

SHA-256 fingerprints of the developer pages we read, by date, so you can show what a page said and when. The open file carries the latest one.

Research notes

The notes our research agent and reviewers keep on each check: which source was opened and what it said.

Weekly snapshots

A frozen copy of the full dataset for each week, for studies that need a fixed point in time.

How to ask. We have not set prices or standard terms for this yet. Tell us who you are, what you are studying and what you need, and we will reply honestly about what we can share and on what terms. Contact us through the press page.

Material shared on request stays anonymous in the same way as the open data, unless a project has already been named publicly after a finished verification.

Attribution

How to credit us

Name Kolaboro, link to the source, name the licence and give the date you took the data. Short is fine.

In a report or article

Source: Kolaboro (kolaboro.com), data under CC BY 4.0, retrieved 1 November 2026.

Under a chart

Data: Kolaboro open data, CC BY 4.0. Our calculations.

On a web page

Data: <a href="https://kolaboro.com/database/">Kolaboro</a>, <a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>

In academic work

Kolaboro (2026). Off-plan disclosure database. https://kolaboro.com/database/ (accessed 1 November 2026). Licensed under CC BY 4.0.

Responsible use

Rules that come with the data

These apply to the open data and to anything we share on request. Breaking them ends any on-request access.

  • Do not de-anonymise projects. Do not try to work out which developer or building an anonymous record belongs to, by matching it with other data, contacting people or any other means.
  • Do not use it to harass individuals. Not developers, their staff, agents, buyers or anyone named in a public record. Criticise practices, not people.
  • Do not present it as legal or financial advice. It is a record of what was published and what other sources say, with a verification level for each check.
  • Keep the verification level. A claim made only by a developer is not a confirmed fact, and a contradiction is not proof of wrongdoing. Do not drop that context.
  • Do not imply we endorse your work. Crediting us is required; saying we approved or partnered with you is not allowed unless we have said so in writing.
  • Do report errors. If you find a mistake, send it to corrections and we will fix it and log the change.
Protect my purchase