NakodaX

Source Protection/Find the crown jewels

We find the code worth protecting.

Point us at a repository. We rank the files by how much only you could have written and suggest what to lock. You review the list.

Contact usSign in

How we find them.

Finding the crown jewels means ranking the files in a repository by how much unique logic they hold, so you lock the small part that makes your product yours and not the whole codebase. NakodaX suggests the files, and you review and change the list before anything is protected.

Connect a repository

Pick the repository and the branch on GitHub, GitLab or Bitbucket.

Your own repository is read, never changed.

We rank the files

Each file is scored by how much real decision making it holds and how unusual it is. Boilerplate, generated code and borrowed libraries score low.

A large repository with several services? Choose the folders to look at.

You review the list

See what we suggest, add files, take files off. Nothing is locked until you say so.

Save the map

The list becomes the map for every release you publish. Change it whenever your product changes.

Who uses it.

  • CTOs deciding what is worth protecting

    Start from a ranked list instead of a workshop, and adjust it.

  • Heads of engineering with a large repository

    Pick the services that matter and leave the rest alone.

  • Founders before a first on premises deal

    Know what you are locking before the customer asks.

Watch how it worksSource Protection for software deployed outside your businessWatch (3:29)See it in a real situationThe dev agency that built it with youRead the story

Find the crown jewels questions

Does AI pick the files?
No. The ranking looks at the code itself, and you make the final choice.
Which languages can it look at?
Python, JavaScript, TypeScript and SQL today. Java, Go, C#, PHP, Ruby and Rust are planned. Tell us what you build with and it shapes what we add next.
Does it change my repository?
No. We read it and publish a protected copy somewhere else. Your repository stays as it is.

More Source Protection features

Protect and publishA protected copy, ready to ship.Runs at the customerRuns on their servers. Readable only while it runs.One switch per customerEnd one customer. Nobody else notices.Stand insLet people build without letting them read.Approved changesChanges to the crown jewels need a second pair of eyes.Every deploymentKnow where your software is running.

Watch and read

Source ProtectionWhen the acquirer wants to see the codeSource ProtectionThe licensed code problemSource ProtectionYour algorithm is ten files. Everything else is plumbing.

Ship the software. Keep the secret.

Tell us what you deploy and where it needs to run. We will show you how it would work. Already a customer? Sign in to your console.

Contact usSign in