Skip to content
@nakodax

NakodaX

Documents, data and code travel encrypted and ask your permission every time they open. Withdraw that permission and every copy stops working, wherever it is.

NakodaX

Control documents, data, and code after you send them

NakodaX helps you keep control of sensitive work after you share it.

It protects documents, data pipelines, media, email attachments, and software with encryption and permission checks at the point of use. You can change, limit, or revoke access at any time, including after content has been shared, downloaded, or forwarded.

🔗 Website: nakodax.com
💼 LinkedIn: linkedin.com/company/nakodax
🐦 X: x.com/nakodax
📘 Facebook: facebook.com/NakodaX
📸 Instagram: instagram.com/nakodaxtech
✉️ Support: nakodax.com/support

What we build

Traditional sharing relies on trust once content has been sent. NakodaX keeps content protected after delivery, so you can decide who can access it, what they can see, how long access lasts, and when it ends.

NakodaX does not store or access the readable version of your content. Documents are encrypted before upload, data stays in your environment, and source code remains protected inside your own software.

Our products

Document protection

Protect contracts, presentations, PDFs, spreadsheets, photos, and other sensitive files.

Learn more · Open the platform

Source protection

Let customers run your software on their own infrastructure without giving them a readable copy of your source code.

Learn more · Open the platform

Data Pipelines

Extract data from your warehouse, apply protection, and securely share it with vendors, partners, and customers.

Learn more · Open the platform

What NakodaX can protect

Documents

Works with Google Drive, Microsoft SharePoint, OneDrive, Google Photos, and Dropbox.

  • Revoke access after a file has been sent
  • Set an expiry date for access
  • Limit how many times a document can be opened
  • Share selected pages, slides, rows, or columns
  • Encrypt files in the browser before upload
  • Let recipients open protected files without creating an account
  • See document level analytics for opens and usage

Email attachments

Encrypt attachments before they leave your device. A forwarded, archived, or leaked email does not automatically grant access to the protected attachment. You can revoke access to the attachment independently of the email.

Photos and video

Choose who can view a photo or video, set how long access lasts, limit views, and revoke access whenever needed.

Data Pipelines

Extract data from a warehouse, protect it, and share it with the people who need it.

  • Share all data or only selected data
  • Filter rows for each recipient
  • Hide, mask, or encrypt selected columns
  • Give vendors, partners, and customers their own controlled view
  • Set an expiry date for access
  • Set and enforce retention periods
  • End access when policy requires it, not only when a contract ends
  • Load protected data into a destination warehouse
  • Work with Snowflake and Databricks without requiring Enterprise editions
  • Keep data in your environment without storing it on NakodaX servers

AI access

AI tools can access NakodaX protected content only during an authorized open. If access is revoked, the content can no longer be opened by people or AI tools.

Source code and intellectual property

Source code is often shared with developers, vendors, and customers so they can build, maintain, deploy, or run software. Once someone receives a readable copy, it can be copied, backed up, or retained after an engagement ends.

Contracts define what should happen to that code. They do not show you who still has a copy or prevent it from being reused.

AI makes this risk larger. A copied codebase can be uploaded for analysis, generation, or refactoring. It can be reshaped into a similar product, shared with another party, or used to help build a competitor.

NakodaX lets software run on customer infrastructure while your proprietary logic remains protected and access stays under your control.

  • Deploy software without handing over readable source code
  • Keep proprietary code encrypted at rest
  • Decrypt code only when the software runs
  • Control access for each customer deployment
  • End access for one customer without affecting others
  • End software access automatically when a contract ends
  • Reduce reliance on contracts alone to protect valuable source code

How it works

  1. Protect at the source. Documents are encrypted in the browser, data is protected before sharing, and source code remains encrypted until the software runs.

  2. Share as needed. Send protected content through email, cloud storage, a data pipeline, or NakodaX.

  3. Check permission at use time. NakodaX confirms that access is still allowed.

  4. Change access anytime. Revoke, limit, extend, or expire access after sharing.

Follow our work

This organization is where we share NakodaX projects, product components, and technical work.

Explore our repositories or visit nakodax.com to learn more.

Pinned Loading

  1. nkx-cli nkx-cli Public

    nkx CLI — public binary releases for the Nakodax runtime SDK/CLI (source stays in nakodax/nakodax)

  2. .github .github Public

    Documents, data and code travel encrypted and ask your permission every time they open.

  3. homebrew-tap homebrew-tap Public

    Homebrew tap for nkx (brew install nakodax/tap/nkx)

    Ruby

Repositories

Showing 3 of 3 repositories

People

This organization has no public members. You must be a member to see who’s a part of this organization.

Top languages

Loading…

Most used topics

Loading…