AB-1002 · example listingWithin 30 days
Types of data
Issue trackers
Every bug, feature and decision a team logged while building its product.
- Issues with the code change that closed them
- Discussion threads that show how a team reasoned
- Years of history across products and releases
- The trackers you use and the years they cover
- Whether code or tickets sit alongside them
- Who holds the rights: the company, or an administrator if it has closed
- Names, emails and handles of staff and customers
- Customer details pasted into issues
- Secrets such as keys and passwords left in comments
- Estimate: A market estimate in about two minutes, worked out from public prices. No email asked.
- Check the rights: We confirm who holds the rights and who can sign for them, before anything else.
- Clean: Personal data is taken out first, along with anything bound by another contract.
- Preview set: A small anonymised preview set is shared under a non-disclosure agreement, only with the owner's agreement.
- License: The owner agrees the terms. The licensed copy goes straight from the owner to the buyer.
Systems it usually lives in
JiraGitHubGitLabLinearAzure DevOps
Example listings
Every listing here is an example, made to show how the catalogue reads. The catalogue opens to approved buyers; no listing, buyer or deal shown here is real.
GitHubJira
AB-1012 · example listingWithin 90 days
Product codebase with its history, fintech
GitHubJira
AB-1022 · example listingReady now
Product codebase with its history, manufacturing
GitHubJira
Three ways to work with ABURA
Whether you hold data, need it, or know a company that holds it.
01
Owners
License the records your company already holds, on your terms. Free to list.
02
Buyers
Company data that has never been published, with the rights checked and personal data taken out first.
03
Agents
Introduce a company you know. Your reward comes out of ABURA's fee, never from the owner, and is set out in our written agent terms.



