Topic
Data licensing
Licences for internal use, embedding and redistribution.
- How to evaluate a company data vendor in ten questionsTen questions for any vendor of company data, from coverage to change management, each with a document to request and a test to run on a sample. Our own answers are included, each with the public document behind it.
- What a data licence covers: internal use, embedding, redistributionA data licence grants a use, not a dataset. This guide places common plans under internal use, embedding or redistribution and lists what to settle for each before you sign.
- Enriching company records in your data productEnrichment starts with a match and ends with a licence. Here is how to match records on domain, which fields to add, how to refresh them and what to settle for embedding.
- Redistributing company data to your customers under licenceA working list for platforms and product teams that deliver licensed company data onward: what the data carries, what you can promise customers and which questions to put in writing.
- Data sharing in Oracle Autonomous Database, explainedVersioned and live shares, Delta Sharing as provider and as recipient, and the controls a licensing team needs to map: who receives the data, for how long, and what is logged.
- Delta Sharing, explained for data licensing teamsThe open protocol behind Databricks Marketplace: how providers, shares and recipients work, what changed in its name in 2026, and what a licensing team should settle when data is shared.
- Governing licensed data with Unity CatalogA worked Unity Catalog design for licensed data: a catalog per agreement, group grants, licence tags, lineage and share checks, with the limits of each control stated.
- OneLake shortcuts and external data sharing in Microsoft FabricShortcuts point to data without copying it, and external sharing opens it to another tenant. Here is what each does and what to settle in a data licence before you use them.
- Snowflake Secure Data Sharing, explained for licensing teamsWhat is copied, who pays, how access ends and what a licence must still say, whether data reaches you as a Snowflake share, a listing, a reader account or as files you load.
- What it takes to list a data product on Snowflake MarketplaceA provider-side guide for data teams deciding whether to list on Snowflake Marketplace: prerequisites, listing fields, review, regional delivery, duties after publication and the licence questions to settle first.
- Building crawlers vs licensing company dataA crawler framework fetches pages, and company data needs more work after the fetch. What building takes, what a licence delivers in its place, and how the two combine.
- Data marketplace vs direct licensingA marketplace can find, bill and deliver a dataset, but the terms of use still come from the provider. What each route settles at each stage, and how to test the data on either.
- Datarade vs Snowflake Marketplace: two kinds of marketplaceOne marketplace introduces you to a provider and leaves the contract to the two of you. The other puts the provider's tables in your account and sends the invoice. How to use each, and what both leave open.
- Delta Sharing vs Snowflake Secure Data SharingOne is a protocol that any client can speak, the other a feature inside one platform. A comparison built on two questions a licence turns on: who can be a recipient, and what ends access.
- Alternatives to building your own company data crawlersFour routes to rows of company data from the web: your own crawler, a managed scraping service, open datasets or a licensed feed. What each takes off your hands, and what stays with you.
- Crunchbase alternatives for company data licensingCrunchbase records who funded a private company, round by round. Here is what it licenses, which databases cover the same ground, and the job that dated company signals do beside a funding database.
- Data licenceThe contract that gives a buyer the right to use a dataset, and sets its limits. Internal use, embedding and redistribution, the terms to settle and how terms travel.
- Data manifestA data manifest is the file that describes one delivery of data. This entry shows what it holds, how to check a load against it and what Fokals states in its own.
- Data marketplaceA data marketplace is a venue where providers list datasets and buyers acquire them. This entry separates its two kinds and lists what to check beyond the listing.
- Data sharingData sharing gives another organisation read access to tables you hold without sending a copy. This entry explains how it works and what it means for licence terms.
- Redistribution licenceA redistribution licence lets a buyer pass licensed data on to its own customers. This entry sets it beside internal use and embedding and lists the terms to settle first.