Rightmark vs. Datarade: a 2026 head-to-head comparison

Compare what the owner needs to prepare and what the buyer needs to establish before a license.

Re-check published fees and shares before committing, and confirm the scope and agreement-specific terms in writing.

The seven questions below follow the purchase from the first sample to delivery. Owners can use them to prepare an offering; buyers can use the same questions to compare proposals.

1. Will the sample tell you what you are actually getting?

A buyer looking for changes over time needs more than a handful of complete records. They need to see how the same entities appear across the requested period. That changes what the owner should sample, and what the buyer should test.

Rightmark's buyer workflow starts with a written scope, then representative scrubbed samples under NDA. Datarade's publishing rules make product descriptions and sample quality explicit provider obligations. That gives each conversation a starting point, but the test still has to belong to your request.

For an owner, prepare a description that someone outside your company can understand: what one unit contains, which period it covers, what is missing and which parts you have excluded. Raw volume is unhelpful if the recipient cannot tell whether linked records survived the export or whether a blank field means unknown, removed or never collected. The sample-pack checklist makes those distinctions visible before a buyer sees the material.

For a buyer, write down the acceptance question before choosing a sample. If your requirement depends on relationships between records, inspecting isolated rows will leave it unanswered. If it depends on history, ask how the sample covers that history. Datarade's sourcing guide recommends matching geography, period and attributes when comparing samples. A comparison becomes useful when both candidates face the same question.

Before accepting a sample, decide what would make the full delivery unusable. Missing months, broken links between records and excluded fields call for different checks. Put the check and the consequence of failure in the agreement, then assign someone to run it on receipt. Rightmark describes graded batches and asks buyers to scan again, so ask what the grade measures alongside your own test. A grade can describe the material without predicting how a model trained on it will perform.

Bottom line: Datarade suits comparison of documented products. Rightmark's scope and sample process is useful when the private collection still needs to be defined for a buyer. Choose on the evidence for your test, rather than treating either route's description as the test result.

What to ask both: "Can you show how this sample represents the full licensed material, which gaps remain, and the written test and remedy we will use if a delivered batch differs?" A polished sample without an explanation of its selection leaves the main question open.

2. How does Datarade pricing compare with what Rightmark charges?

An owner needs to know what they will receive after the costs of a license. A buyer needs the total cost of usable data and the rights to use it. A free account, an annual provider plan and a dataset price answer different parts of those questions.

Confirm the fees, payment basis and exit terms in the proposed offer or agreement before committing.

Using the same annual commissionable base and attribution, fees = annual subscription + commission × base.

Fee-only break-even: $60,000 for Commission-only/Bronze; $120,000 for Bronze/Silver, calculated as $6,000 / (30% - 20%) and $6,000 / (20% - 15%). These exclude other charges; listing limits differ.

For Rightmark, the published standard fee rule separates the agreed owner payout from the fee charged to the buyer. The owner keeps that payout, which is not the same as receiving all the money the buyer spends. Premium and bespoke deals have different economics: the homepage states a 75% to 85% owner share, agreed in writing before a sale. Ask which arrangement the proposed offer uses before comparing percentages.

For owners, an offer is only comparable when it buys the same rights and work. An exclusive license can prevent a later sale that a non-exclusive license would leave open. A higher payment can also come with more extraction or update work. Put the term, exclusivity, permitted use, usable volume and delivery duties beside the amount you would receive. Compare those offers before comparing the percentage printed on a pricing page.

Buyers should request the same breakdown from the other side: license, platform fee, preparation, transfer and updates. Have the offer identify who covers extraction, scrubbing and transfer, which work is included and what additional work would cost. Use the Price Index to understand units and source limitations, rather than treating a market range as a quote for this collection.

Bottom line: Compare the written owner receipt and buyer total for the same rights and work. Rightmark's standard fee arrangement is attractive when you want the owner payout agreed separately, but it establishes neither a higher payout nor a lower buyer cost.

What to ask both: "For this dataset, use, volume and term, what will the owner receive and the buyer pay, which amount is subject to fees, and what becomes payable on a sale, renewal or cancellation?" A percentage without its calculation base is an unfinished answer.

3. What may each party share, license and use?

An archive can sit on your servers while containing work you cannot license to someone else. Buyers therefore need more than an assurance that the owner controls the files. They need to see how the owner acquired the rights and whether those rights cover the proposed use.

Rightmark's ownership-pack description addresses those questions differently for each kind of asset: IP documents and scan reports for code, authority and scope records for company archives, and releases naming AI training for audio and video. A code scan and a contributor agreement answer different questions; the pack brings them together for counsel to assess. It cannot replace that assessment.

For the owner, the consequential passage may be the warranty rather than the headline about keeping ownership. Rightmark's Trust page says some code agreements leave the ownership indemnity uncapped. It also describes routes where a licensing partner may sublicense, take an own-use license or create derived datasets. Those are substantial permissions to read before signing, especially if the code remains commercially sensitive.

For buyers, say what engineers will actually do with the material. Will they inspect it, train a model on it, retrieve passages from it or create another dataset? A general request for "AI rights" leaves those decisions unresolved. Rightmark's portal materials are for deciding whether to license the collection. The NDA permits that evaluation; training needs the appropriate license.

The same care applies at the end of an engagement. Ask which copy must be deleted, whether the requirement covers derivatives and how the parties will document completion. Rightmark's portal sample deletion, end-of-license deletion and retention of verification or financial records have different rules. Closing access to a portal is not evidence that all downstream material has disappeared.

Bottom line: Keeping ownership is common ground. Rightmark's pack is useful when the owner needs to assemble the evidence for a private collection; Datarade's published requirements give an established provider a disclosure framework. For either route, choose the permission you can support in writing and have counsel assess the unresolved rights and liabilities.

What to ask both: "Which documents establish the right to license this material for our intended use, what downstream uses and liabilities does the agreement allow, and what must each party delete or retain afterward?" Treat an NDA offered in place of a license grant as a reason to keep asking.

4. When does an action need another approval from you?

An owner may be happy to authorize a sample review yet want a separate decision before a license. A buyer may have access to a preview without permission to run the test its engineers have in mind. The useful definition of control names the action, who can authorize it and the document that records that authority.

The distinction matters particularly on Rightmark's code route. Its Trust page describes signing an agreement that can authorize later non-exclusive licenses without a fresh decision for each sale. If choosing every future code buyer is essential to you, settle that requirement before signing. It is not part of the documented standing authorization.

Datarade's terms distinguish provider-published product pages from profiles that may be generated automatically. They also separate the platform relationship from the buyer's product contract. Do not read the existence of a profile as an owner's approval of a particular product, or assume that preview access settles a proposed evaluation.

Read the agreement with the actions your staff will take in mind. Who may approve a public description? Who may release a sample? Does the signature authorize one license or later licenses as well? Record the person or role allowed to make each decision and the document granting that authority. The point is to know when a colleague must come back to you before proceeding.

For a code owner, distinguish stopping new licenses from ending one already granted. Rightmark allows withdrawal of code not yet licensed; existing licenses continue for their term. For either service, ask separately about revoking a connection, delisting a description, deleting an evaluation copy and ending a product agreement. One request should not be assumed to accomplish all four.

Bottom line: Rightmark's standing code authorization fits an owner willing to approve later non-exclusive licenses when signing. Datarade suits a provider that wants to publish the product and negotiate the buyer's agreement. Decide which permissions you are willing to grant once and which must return to you for approval.

What to ask both: "Which actions need a fresh approval from us, which are authorized when we sign, and what happens to future access and existing licenses if we withdraw?" An answer that says only "you keep control" needs more detail.

5. Can you find the material, or the buyers, you need?

A buyer can find a promising category and still lack the right language, period or usable volume. For an owner, reach matters when the audience has a reason to license the particular collection. Count confirmed matches to the requirement before counting the size of a marketplace.

Datarade has a clear advantage for exploring alternatives across providers. You can inspect categories and product formats, then narrow the conversation to a shortlist. Its complimentary sourcing advice and requirement postings also make it useful when you need help developing that shortlist. A buyer does not need to arrive with every procurement question resolved.

Rightmark starts its buyer process with a specification for private material, then replies with what can be sourced, volumes and timing. That can be a useful starting point when the requirement depends on a particular combination of history, content and rights. The reply needs to confirm the collection; a request form is not a supply commitment.

The buyer request brief is useful here because it makes room for an unanswered requirement. List the language, subject, date range, format, volume, exclusions and delivery conditions, then mark each as known, needing evidence or unavailable. A collection that covers only part of the requested period may still be worth buying. Your team should make that decision explicitly, before someone prices it as a complete match.

Rightmark lists several private-data families, but its lots labeled in preparation are unavailable. It does not accept health or children's data. Those boundaries matter more than whether a category appears in a navigation menu. Owners should also distinguish permission to offer an asset from evidence that someone intends to license it.

Bottom line: Start with Datarade when broad supplier comparison is the job. Start with Rightmark when a private collection needs to be scoped against your request. In either case, a useful response identifies the material that is available, the part still being sourced and the dependency that could stop delivery.

What to ask both: "For this language, period, format and volume, what is available now, what still needs sourcing, and what could prevent us from licensing it?" A category page or future lot does not answer a question about current supply.

6. Which work will your team still have to do?

Who will answer a buyer who asks why an attribute disappeared between two exports? Who can approve removing a sensitive field? Those people may differ from the person negotiating the price, so the workload comparison needs to include all of them.

Datarade's Lead Inbox guide distinguishes contact requests from sample views. Accepting a contact request opens a deal where the provider can message the buyer; viewing a sample does not establish an intention to purchase. That distinction helps an owner decide who needs an answer now and who has only begun looking.

Providers can also respond to buyer postings. The response links a relevant product to the requirement; once accepted, it opens a conversation about delivery, pricing and terms. That is a concrete reason to keep the catalog and the person answering inquiries close together: the conversation begins with a particular product, whose details the provider must be able to explain.

With Rightmark, identify who will do the preparation for your particular collection. Its published process allows scans and scrubbing on the owner's side or in a licensing partner's pipeline. Even when the buyer funds preparation, someone at the owner company must supply rights documents, identify exclusions and approve the sample. Budget that person's time alongside the technical work.

For each task, write down four things: who does it, what access they need, what they deliver and who accepts it. An extraction task might need an administrator, while a decision about client-owned code needs someone who can establish the relevant permission. Giving both tasks to a vague "data team" leaves the handoff unresolved.

Buyers need a handoff between the people who test the sample and those who receive the files. Give the receiving team the agreed checks and the authority to reject a failed batch. Name the person who can accept a replacement, a smaller delivery or a changed field. For recurring deliveries, decide which checks run again each time. That is where a seemingly simple purchase can become ongoing work.

Bottom line: Datarade's workflow fits a team operating its own catalog and commercial conversations. Rightmark is relevant when assembling a private licensing opportunity is part of the job. Buy the named work in the scope; neither a dashboard nor a process diagram tells you that every preparation and support task is included.

What to ask both: "For preparation, rights evidence, delivery and acceptance, who does the work, what access do they need, what do we receive, and which tasks remain with our team?" Ask for those answers even when the proposal says the service handles everything.

7. What proves this route fits a transaction like yours?

A clear process helps you understand an offer, but it is different evidence from a completed license. Owners want to know what was licensed and received; buyers want to know what was delivered and accepted. The comparison needs both sides of that record.

Datarade's company history dates incorporation to 2018 and the marketplace launch to 2020. That establishes an operating history. It does not establish that a particular provider has delivered the material you need. Feedback about a supplier and feedback about the marketplace answer different questions too.

Rightmark's published ownership-pack examples are illustrative, redacted materials. They help you see what a review could contain, but they are not a customer transaction you can use to forecast your own result. Ask for a comparable reference that can be shared with permission; do not substitute the value of a deal elsewhere in the market.

Ask an owner reference how much preparation remained with their team, which rights they granted and what they actually received after charges. Ask a buyer reference what arrived, which checks it passed and how a mismatch was resolved. A smaller transaction with similar files and permissions may tell you more than a large deal whose only disclosed detail is its price.

If no relevant reference can be shared, you can still evaluate the sample and proposed agreement. Decide how much you are willing to commit on that basis and what must be demonstrated before proceeding further. Be clear with colleagues about the difference: you have assessed this proposal, rather than verified a history of similar successful transactions.

Bottom line: Datarade's history establishes how long its marketplace has operated; Rightmark's ownership-pack examples show what a review can contain. Neither proves that your proposed delivery will work. If your procurement process requires a comparable completed transaction, obtain that reference before committing.

What to ask both: "Can you provide a dated, attributable example for this data type and use that separates the provider's work, the platform's contribution, the owner's receipt and the buyer's accepted delivery?" A success story about a different product leaves this request unanswered.

• An appraisal before files change hands. The free appraisal uses answers about type, volume, history and rights to suggest possible routes and preparation needs. Its result is indicative, not an offer or a buyer commitment.
• A written scope for private material. The buyer workflow puts families, filters, formats, volume and delivery cadence into a written scope before evaluation. That gives your team a common reference for the sample and the proposed license, subject to confirmation that the requested material can be sourced.
• Evidence organized around the asset. A code ownership pack asks different questions from one for a company archive or media collection. The pack brings the relevant documents and reports together for counsel, with the remaining gaps still visible.
• Standard owner payout separated from the buyer fee. On standard licenses, Rightmark charges its fee to the buyer on top of the agreed owner payout. Premium and bespoke deals instead use an agreed share, with the homepage stating 75% to 85% for the owner; every fee should be visible before signing.
• A code report the owner can inspect locally. Repo Check measures the repository on the owner's machine and produces a shareable file of counts and fixed-vocabulary inputs, without code, paths or email addresses. This describes the report stage: after signing, a code route can use a licensing partner's preparation pipeline and authorize later non-exclusive licenses without another per-sale approval, with withdrawal limited to unlicensed code.

Choose Datarade when you want to compare a broad field of providers or put a documented data product in front of buyers. Its marketplace is a sensible first stop for discovering alternatives before committing to a particular supplier. Previews and sourcing advice help develop the shortlist, while the selected provider still has to answer the sample, rights and delivery questions.

On the owner side, it fits a registered business that can maintain its offering and respond to inquiries. Treat the plan as a distribution expense, weighed against licensing receipts and the work each sale requires.

Rightmark is a useful starting point for an owner who has a private collection but has not yet turned it into a data product. The appraisal begins with a description of what you own. The next questions concern what can be included, which rights documents support it and what a buyer could inspect before agreeing to a license.

For a buyer, its appeal is starting with the material your team needs: particular content, history, formats and permitted uses. Rightmark's written specification, sample and ownership pack give you several opportunities to catch a mismatch before delivery. A missing contributor assignment may mean excluding some code. A sample that omits the required history may mean changing the request. The process is valuable when it helps the parties resolve those concrete problems.

There are clear reasons to stop or choose differently. Rightmark excludes health and children's data, and a lot in preparation is unavailable. An owner who requires fresh approval for every code buyer must settle that requirement before accepting standing authorization. The standard buyer-paid fee may suit the proposed deal, but compare the owner receipt and buyer total against another offer for the same rights and work.

Consider a third option if...

If you already know the counterparty and have a settled requirement, evaluate a direct license with the same diligence on rights, acceptance and cost. An intermediary needs to add useful work to that arrangement; dealing directly does not make preparation or review unnecessary.

If the owner cannot establish title, define the collection or prepare an appropriate sample, the next job may be internal preparation or a narrowly scoped specialist engagement. Neither an appraisal nor a marketplace account supplies the missing rights. Waiting can be the correct commercial decision.

If the requirement is really a new collection project or specialized preparation, evaluate that service on its own terms. Discovery may help you find a provider, but ask the provider to substantiate fulfillment before treating it as an answer to the request.

Relevant reading: Rightmark vs. Defined.ai.

For owners, the choice is whether to prepare a private collection for licensing or distribute a data product you already maintain. Buyers face the matching choice: compare providers' existing offerings, or ask for private material that meets a written specification. Datarade is a strong starting point for provider comparison; Rightmark helps owners appraise private collections and buyers define what to source.

Take the seven questions above into both conversations. Put the proposed files, permitted uses, owner receipt, buyer total and named responsibilities side by side. Then choose the offer you can explain and justify to the people who will approve, prepare and use the data.

Start with the data your team needs.

Describe the data family, intended use, format and volume. Use the request to clarify what can be sourced and which evidence is needed before a license.

Request data