On this page
Start with the deliverable
Rightmark's Trust page Rightmark, (opens in a new tab) and buyer process Rightmark, (opens in a new tab) explain the model.
SimpleClosure AssetHub is worth evaluating when asset recovery sits alongside a company wind-down. Operating companies can participate too. Its buyer proposition emphasizes startup-origin code and workspace records. That gives it a relevant place on the shortlist without making it the automatic answer for every archive or buyer requirement.
We publish this comparison at Rightmark. The task here is choosing a data transaction. A data license, an asset sale and a service for closing a company are different decisions, with different agreements and costs.
| Decision | Rightmark | SimpleClosure AssetHub |
|---|---|---|
| Owner starting point | Scope a supported licensing route and its economics | Assess licensing or sale opportunities |
| AI-buyer starting point | Define the dataset requirement and review evidence/samples | Startup-native asset sourcing |
| Transaction to compare | The actual grant, payment event and continuing obligations | Use the same fields for the proposed agreement |
| Before sharing raw material | Establish scope, authority and the approved review path | Ask what evidence is sufficient for the initial assessment |
| Unresolved authority or rights | Preserve evidence and resolve the issue before committing | Apply the same stopping condition |
AssetHub and Rightmark overlap on code and workspace data
AssetHub's initial scope includes source code and workspace records. SimpleClosure's April 14, 2026 guide SimpleClosure, (opens in a new tab) describes full Git repositories, production code and operational documents. Its September 3 analysis distinguishes licensing by operating companies, which can keep using the underlying assets, from outright sales during wind-down. Analysis, September 3, 2026 SimpleClosure, (opens in a new tab).
Rightmark has separate code and company-archive routes. Its buyer page, updated October 21, 2026 Rightmark, (opens in a new tab), describes sourcing against a requirement and an ownership pack for the applicable route. This comparison focuses on the overlap rather than assuming that either provider can supply every kind of training data.
Write the specific asset before requesting an offer. 'The company archive' could mean a particular set of repositories, a defined workspace period or an approved combination. A useful inventory identifies the entity, systems, versions, dates and exclusions. It should also say what is not yet known.
For a buyer, source context can help decide what to investigate, but the intended task still needs its own specification. Startup-origin records are not automatically the right records for every model. For an owner, the existence of an archive does not mean everything in it belongs in the proposed grant.
Ask both: Which repositories, systems, period and entity are included in this particular proposal?
Compare a license with a license, and a sale with a sale
A transaction label is not enough to evaluate what remains under the owner's control. Read the proposed rights and obligations. The comparison becomes more useful when both providers answer against the same asset rather than different bundles.
Rightmark distinguishes standing non-exclusive code agreements from company-archive terms. On the code route, signing can authorize later non-exclusive licenses without another approval each time, and withdrawal applies to code that has not been licensed yet. Company archives usually go to one buyer for a term. The Trust page, updated October 18, 2026 Rightmark, (opens in a new tab), sets out those differences.
Use the following fields for the actual agreement:
| Field | Question to resolve |
|---|---|
| Ownership after the transaction | What remains owned by the company? |
| Permitted use | Which training, evaluation or other uses are included? |
| Recipient and onward use | Who may receive or reuse the material, and on what terms? |
| Term and exclusivity | How long does the grant run, and what other uses are restricted? |
| Derived materials | Which transformations or new assets are covered? |
| Continuing obligations | What reporting, support, warranties or other duties continue? |
| Exit | What stops, and what rights survive expiry or withdrawal? |
These are comparison questions, not conclusions about a particular company's legal position. A broader grant can change the economics, so a larger headline offer is not necessarily a better offer on otherwise equal terms. First establish whether the terms actually are equal.
Ask both: After this transaction, what do we still own, what can the recipient do, and which obligations continue if the company closes?
Owner economics depend on the fee basis and payment event
Rightmark's standard licensing model makes its fee buyer-paid, with no deduction from the owner's payout. Its premium and bespoke share is agreed in writing. The homepage also states that owners pay nothing upfront. These are useful starting points for a transparent offer, not proof of a higher final payment than any competing proposal. See the published fee model Rightmark, (opens in a new tab) and route terms Rightmark, (opens in a new tab).
Ask AssetHub to set out the fee payer, any deductions, included work and payment trigger in its proposal. SimpleClosure's October 1 guidance tells founders to identify who signs, who owes the payment and where the funds come from. Guidance, October 1, 2026 SimpleClosure, (opens in a new tab).
Rightmark's affirmative case is its visible standard fee payer and scoped licensing process. Compare both written offers on that basis. An unanswered fee question is a point to resolve, not evidence of an unfavorable charge.
For the owner, record proceeds payable, any deduction or separate charge, the calculation basis and the event that makes payment due. Ask whether any condition remains after signing or transfer. For the buyer, record the complete quote for the deliverable, including preparation or additional work if it is separately charged.
Do not compare an AssetHub data fee with the advertised cost of a shutdown service. They answer different purchasing questions. Likewise, do not compare a payment for an outright asset transfer with a narrowly defined license without showing the grant difference beside the amount.
Ask both: Which party pays each cost, how is any percentage calculated, and what exact event triggers payment?
Preserve the evidence before making a provider commitment
A company approaching closure needs to distinguish protecting the archive from authorizing a transaction. Rightmark's wind-down guide, updated October 18, 2026 Rightmark, (opens in a new tab), separates preservation, ownership paperwork, scope and signing authority. Its full export and authority checklists belong there; this comparison adds the information needed to assess two provider proposals consistently.
Start with an authorized inventory of what exists. Record the source systems, export or preservation status, known gaps and who is responsible for access. Keep evidence about ownership and authority available to the people who must review it. Do not send raw archives merely to demonstrate that the asset exists.
Having administrator credentials is not the same as establishing who can approve a license or transfer. The answer depends on the company's current state and the relevant records. If that answer is unclear, preserve the evidence through the authorized process and ask the responsible professional to resolve it before making a commitment. This is general preparation guidance, not insolvency advice.
A provider can help assess a proposed asset, but the commercial recommendation cannot substitute for the authority record. The same boundary applies whether the company is continuing, planning to close or already in a formal process.
Ask both: What minimum inventory and authority evidence lets you assess this asset before any raw files are shared?
Buyers need source permissions as well as a dataset label
Longpre, Singh, Cherep and colleagues' Data Provenance Initiative research identifies differences between dataset-level licenses and upstream-source restrictions. The February 19, 2025 version Data Provenance Initiative, (opens in a new tab) studies public datasets, not these providers. Its useful lesson is to examine the permission chain rather than rely on one label.
Apply that distinction to the proposed acquisition by separating three questions. Where did the records originate? What evidence supports the person's authority to approve the transaction? What does the proposed grant allow your team to do? One document may help answer several questions, but none should disappear behind a reassuring summary.
Rightmark's ownership-pack description Rightmark, (opens in a new tab) is organized by route, while its wind-down guidance Rightmark, (opens in a new tab) distinguishes access from signing authority. Treat those as a way to organize the review. They are not a guarantee that every potential dataset already meets your requirements.
Ask for the scope and exclusions alongside the source evidence. A useful packet can identify a gap or excluded subsidiary as clearly as an included source. The buyer needs to know the boundary of the proposed delivery, not just that records exist.
The same test applies to a startup's operating history. A company-origin story does not, by itself, answer every contributor, client or source-permission question. Request evidence for the intended grant, and obtain the appropriate professional review where the transaction requires it.
Ask both: Which records connect the original asset, the person authorizing the transaction and our intended training or evaluation use?
Make sample acceptance and full delivery explicit
SimpleClosure's AssetHub launch describes connecting source-code owners with buyers, managing diligence and facilitating the transaction. Launch announcement, April 16, 2026 SimpleClosure, (opens in a new tab). Ask what criteria, shortlist, sample permission and delivery steps apply to the asset under discussion. Rightmark starts with a written scope, route ownership evidence and representative scrubbed samples under NDA for evaluation. Its buyer process Rightmark, (opens in a new tab) separates that review from signing the license.
Give the technical reviewer a specific job. For example, ask whether the sample includes the relationships, fields and formats needed for the intended use. Keep the check bounded: inspecting a small subset may reveal a format problem without establishing the coverage or quality of every record in the collection.
Rightmark's sample guide, updated October 18, 2026 Rightmark, (opens in a new tab), makes that limit explicit. A sample does not guarantee a license, price, acceptance or full-collection quality. Its permission should also specify what the recipient can do during review; evaluation access is not an assumed training grant.
Before final commitment, name the delivery version, manifest, acceptance rule, reviewer and process for a mismatch. Ask what happens if the delivered collection differs from the agreed scope. Do not substitute a good first impression for terms neither side has written down.
Ask both: What can we test before purchase, who decides acceptance, and how will a scope or delivery mismatch be handled?
Carry one asset disposition packet to both providers
Use the same asset summary for each proposal. This prevents a comparison from drifting into different records, grants or assumptions. The register below references the preservation work rather than repeating the full export checklist.
Copy it into an internal document. Keep private documents, names, credentials and raw records out of the public example. Record references and responsible roles in the working version. This is a decision aid, not a legal template or a data-upload form.
| Decision / evidence | Preserved asset summary | Rightmark proposal | AssetHub proposal | Unresolved item / role |
|---|---|---|---|---|
| Entity and authority | [State/authority record reference] | [Required evidence] | [Required evidence] | [Fill in] |
| Asset scope | [Systems, repositories, dates, exclusions] | [Agreed boundary] | [Agreed boundary] | [Fill in] |
| Preservation | [Verified export, gaps, storage owner] | [Assessment needs] | [Assessment needs] | [Fill in] |
| Source permissions | [Contributor/client/source evidence] | [Restrictions] | [Restrictions] | [Fill in] |
| Disposition | [Proposed license or sale] | [Grant and retained rights] | [Grant and retained rights] | [Fill in] |
| Use and obligations | [Intended use and constraints] | [Recipients, term, ongoing duties] | [Recipients, term, ongoing duties] | [Fill in] |
| Evaluation material | [Inventory/report, approved sample] | [Permission and access path] | [Permission and access path] | [Fill in] |
| Acceptance | [Task, checks, known gaps] | [Manifest and mismatch process] | [Manifest and mismatch process] | [Fill in] |
| Economics | [Comparable scope] | [Owner proceeds; buyer full quote] | [Owner proceeds; buyer full quote] | [Fill in] |
| Commitment | [Authorized role and evidence] | [Remaining conditions] | [Remaining conditions] | [Fill in] |
An illustrative scenario: a verified repository export makes the inventory row complete, but the authority record is unresolved. That does not make the archive ready to license. Keep the gap visible and resolve it before a commitment. This is not an actual customer or insolvency case.
When is SimpleClosure AssetHub the better fit?
Consider AssetHub when asset recovery belongs within a wind-down plan. Buyers specifically seeking startup code or workspace histories can evaluate its supply process. Request the exact data agreement, current availability and sample conditions, then compare them against the same packet.
Do not assume a broader company-closing service is included in the data transaction. Confirm the service boundaries and responsible parties instead of treating a recognizable brand as a substitute for scope.
When is Rightmark the better fit?
Choose Rightmark first when the priority is a focused licensing decision with a defined scope, explainable fee basis and published assessment boundaries. Code owners can begin with Repo Check Rightmark, (opens in a new tab), which runs locally and does not upload source in that initial step. It remains a readiness aid, not proof of title, buyer demand or a final price. Other supported owners can start with the appraisal.
For AI buyers, Rightmark is a strong fit when you can specify the required dataset and want to evaluate a written sourcing proposal, ownership evidence and a permitted sample. Use the buyer request path Rightmark, (opens in a new tab) with the asset scope and acceptance questions. A request does not guarantee available supply or a quote, and Rightmark does not accept health data yet.
If essential authority or source rights remain unresolved, neither provider choice fixes that problem. Preserve the evidence, resolve the boundary and then compare the offers on terms both sides can understand.
Sources
- Rightmark: Buyer process (opens in a new tab)
- Rightmark: route terms (opens in a new tab)
- SimpleClosure: How to Sell Your Startup's Assets Before You Close (opens in a new tab)
- SimpleClosure: What Your Assets Are Worth (opens in a new tab)
- Rightmark: See the published fee model (opens in a new tab)
- SimpleClosure: How Real Are Those Million-Dollar Data Offers? (opens in a new tab)
- Rightmark: wind-down guidance (opens in a new tab)
- Data Provenance Initiative: Bridging the Data Provenance Gap Across Text, Speech and Video (opens in a new tab)
- SimpleClosure: Introducing the SimpleClosure Asset Hub (opens in a new tab)
- Rightmark: sample guide, updated October 18, 2026 (opens in a new tab)
- Rightmark: Repo Check (opens in a new tab)