NakodaX

NakodaX blog/Source Protection·4 min read

Can you ship your source code to a customer without them reading it?

Yes. Source Protection encrypts the files that hold your business logic. The customer runs your software as usual, and the protected code opens only in memory while a valid license is active. Without a license, a copy of the repository is only encrypted data. You can try this yourself with a free sample app.

NakodaX Marketing team

By NakodaX Marketing team

NakodaX ·

A rolled blueprint with a brass key resting on it. The plan fades into a scatter of glowing green squares.
Ship the software. Keep the secret part encrypted until a license opens it.

Some companies sell software that customers run on their own servers. A bank, a hospital group or a large retailer installs it inside its own network.

That is normal. But it often means the customer holds a full, readable copy of your code. The contract may end and the software keeps running. Someone can also copy the code, hand it to a contractor or paste it into an AI tool.

This post explains a simpler way. You ship the software with the important files encrypted. The customer still runs it. Only a valid license can open those files, and only while the program is running.

Why is a readable copy a problem?

When a customer installs your software, the code sits on their servers. Many of their staff, vendors and contractors can reach those servers. You cannot see who opens the files.

Most of the code is ordinary: login screens, forms, logging and settings. A small part is yours alone. It might be your pricing rules, a scoring method or the way you match records. That small part is the reason customers pay, so it is the part worth keeping private.

This situation shows how an install ends up outside your control, and why a readable copy is hard to take back.

How does encrypted shipping work?

Source Protection looks through your repository and suggests the files that hold the most business logic. Your team reviews the list and approves it. Nothing is encrypted before that.

NakodaX then encrypts the chosen files with AES 256 GCM and publishes a protected copy. Your original repository does not change. The protected copy has the same folders and the same file names. Only the chosen files are replaced by encrypted versions.

  1. Choose the files that hold your business logic and approve the list.
  2. Publish the protected copy and ship it to the customer.
  3. The customer installs the NakodaX runtime and starts your software the usual way.
  4. When the software loads a protected file, the runtime asks NakodaX for the key. With a valid license, the file opens in memory.
  5. With no license, or an ended one, the file stays encrypted and the protected part does not run.

There is no license check inside your code that someone could delete. The key is what opens the file. This is the idea behind a protected release.

How can you try it yourself?

We made a small app called LedgerLens and shipped it with its source encrypted. You can clone it from nkx-sample-app on GitHub. Run it without a key and you see a locked screen. Run it with the free trial key that comes with the repository and it unlocks and runs on your own computer in about a minute.

The README lists the exact commands. You need Python 3.10 or newer and the nkx command line tool. The same app also runs in Node.js, and both versions give the same result.

The trial key opens this one app and nothing else, so you can try it without any setup on your side.

Want to see what a fully protected codebase looks like from the outside? Read what an encrypted repository looks like on GitHub.

What can you control after the customer has it?

A license belongs to one customer, team or developer. It can have an end date and a limit on how many copies run at the same time. You can suspend it and bring it back, end it for good, or replace its key. See customer deployments and customer control.

This suits pilots and installs on customer servers, where you want the customer to try the real software while your logic stays private. If a customer must run it with no internet, NakodaX can be installed on their own servers, including offline and air gapped networks.

What does this not do?

Source Protection keeps the protected code out of every copy at rest, such as a copied repository, a backup or an old install. The code opens only in memory, while your licensed software is running.

Ending a license takes effect the next time the software asks for a key.

It works today for Python, JavaScript, TypeScript and SQL, and more languages are planned.

The takeaway

Your customer can run your software without holding a readable copy of the part that matters. You can try the idea yourself, for free, in about a minute.

Related product

NakodaX Source Protection

Let vendors and customers build or run software without receiving selected proprietary source code in readable form.

See how it works

Common questions

Can a customer run my software without being able to read the protected code?
Yes. With a valid license, the runtime decrypts the protected files in memory while the software runs. Nothing readable is written to disk.
Do I need to change how I write my code?
No. You keep working in your original repository, which is not changed. NakodaX publishes a protected copy for you to ship. It works for Python, JavaScript, TypeScript and SQL.
Is the sample app really free to try?
Yes. A free trial key comes with the repository. It opens that one app and nothing else, and it ends on 9 March 2027.

Try this on your own code.

Start a free trial, or tell us what you share and with whom, and we will show you how NakodaX handles it.