NakodaX

Source Protection/Runs at the customer

Runs on their servers. Readable only while it runs.

Your customer deploys as normal. The locked parts open for the running software and nowhere else.

Contact usSign in

How it runs at the customer.

A protected release runs on the customer's own servers. When the software starts, a small runtime checks the customer's key and opens the locked parts in memory only. Nothing readable is written to disk, and a copy of the repository is only locked files.

They add a small package

The customer adds the NakodaX runtime to the app and starts it the usual way.

You hand them one page with the steps and the key.

The software checks in

When it starts, it asks NakodaX whether the key is good. If it is, the locked parts open for that running process.

Open in memory only

The code is readable while the software runs, and only there. Nothing readable is left on their disk.

No key, no code

Without a valid key the locked files stay locked. A copied repository is only locked files.

The software checks in when it starts and at regular intervals, so it suits connected customers.

Who uses it.

  • Software vendors whose customers want it in their own data centre

    Say yes to on premises without handing over how it works.

  • Sellers to banks, insurers and other regulated customers

    The software runs inside their walls with your logic locked.

  • Companies running their software at partners and resellers

    A partner runs it, and you hold the key.

Watch how it worksSource Protection for software deployed outside your businessWatch (3:29)See it in a real situationThe install you can’t take backRead the story

Runs at the customer questions

Does the customer need an account with NakodaX?
No. They use the key you give them.
Which languages work?
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.
Can it run offline?
The software checks in with NakodaX when it starts and at regular intervals, so it suits customers who are connected.

More Source Protection features

Find the crown jewelsWe find the code worth protecting.Protect and publishA protected copy, ready to ship.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 ProtectionYour algorithm is ten files. Everything else is plumbing.Source ProtectionThe licensed code problem

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