NakodaX

Industries/Data providers and marketplaces

Sell the feed. Keep control of every file you deliver.

Daily feeds, licensed datasets and customer exports. Each subscriber gets the columns it pays for, and access ends with the subscription.

Works withDocumentsData

A wide data table on a screen, with a few columns lifted out into three separate glowing tables.

In short

A data provider usually delivers plain files, and every subscriber keeps everything it ever received, whatever the licence says. With NakodaX, protection runs inside your own pipeline: each file goes out with only the columns that subscriber may have, under its own licence, and keys stop being released when the subscription ends. NakodaX never holds the data.

Who it's for

Data providers, data marketplaces and software companies that deliver data exports to their customers

What you share

  • Daily and weekly data feedsData Protection
  • Licensed datasetsData Protection
  • Data exports for your customersData Protection
  • Samples and methodology for prospectsDocument Protection

What NakodaX does for data providers and marketplaces.

Use one product, or all of them. Each covers a different thing you share.

Document Protection

Samples and methodology for prospects

A prospect agrees to your NDA before the sample opens, and it stops opening when the trial ends.

Explore Document Protection
Data Protection

Feeds and datasets for subscribers

Each subscriber gets one view made for it, under its own licence, and access ends with the subscription.

Explore Data Protection

Data providers and marketplaces questions

Does the protection run on our side or yours?
On yours. The libraries run inside your own pipeline, in Python, Node, Java or Spark, and protect CSV, JSON and Parquet as they are written. NakodaX never holds the data, only keys and licences.
What does a subscriber need to read the files?
A licence key and the same libraries, or the reader in the console for opening a protected file in the browser.
Does a daily feed need a new grant for every subscriber every day?
No. You grant a dataset to a subscriber once. Every run gets its own keys, so a leaked key opens one day, not the archive.
What about files a subscriber already opened?
They keep what they already opened. Ending a licence refuses their next request for a key, within the hour even for a long running job. So deliver each subscriber only its columns, and watch the activity for every read.

Tell us what you share, and with whom.

We will show you which product fits, on your own files, data or code.

Use cases for data providers and marketplaces

Other industries