By Pallav Boonlia
Founder & CTO, NakodaX ·
NakodaX blog/Source Protection·2 min read
Share only what the buyer needs and set an end date. With NakodaX Source Protection, the files that carry your business logic are encrypted and run only with a license that has an end date. If the deal fails, you revoke it and the protected files stop working at the next key request.
By Pallav Boonlia
Founder & CTO, NakodaX ·

Diligence should allow a real review and give you a defined end to access if the deal does not close.
A serious buyer asks to review the code. That is reasonable. It is also a moment when a company can hand a competitor a copy it cannot take back. The deal may close. If it does not, what is left on the other side?
A repository invitation, a screen share and a zip in a data room each trade speed for exposure. Once readable code is copied out, nothing changes that if the deal fails. A review needs a full look at the product. It does not need an endless, readable handover.
Before the review, choose the files that carry your real advantage and publish a protected release. The buyer's engineers can run and test the product under a license you set, with an end date. The rest of the code stays open and readable.
When diligence ends, you revoke or let the license end. The protected files stop working at the next key request, instead of relying only on a repository invitation that you remove.
Decide that on purpose and keep it narrow. Reading the logic line by line is a separate decision from running the product. Make it a defined step with a named person and an end, and keep the activity record. NakodaX records every key request and license change.
No control can take back what a person has already copied, photographed or learned. While the product runs on a licensed machine, the protected code is readable in memory. The value is in removing the ordinary leftover copy.
Share properly, and decide in advance what happens when the process ends.
Related product
Let vendors and customers build or run software without receiving selected proprietary source code in readable form.
See how it worksStart a free trial, or tell us what you share and with whom, and we will show you how NakodaX handles it.
Real situations, and the video where there is one, on the same problem.
Video
Ship software to customers, vendors and agencies without giving away how it works. NakodaX Source Protection finds the code only you could have written, locks it, and gives you an off switch for each customer.
Watch (1:51)Situation
Big customers want your software inside their own environment. That means handing them a full, working copy of your code, and you have no way to switch it off when the contract ends.
Read moreSituation
You installed a 60 day pilot on a prospect’s servers. The deal stalled. A year later, they are still using it, and they have a full copy of your code.
Read more
New to NakodaX? Watch the overview
A full walkthrough of how NakodaX helps a business keep control of documents, business data and source code after they are shared, moved or deployed.
Watch the video (8:49)
Source Protection · 3 min read
Turning off a contractor's access does not remove the clone on their laptop. Here is how to protect the key files so they stop working when the contract ends.
August 20, 2026

Source Protection · 7 min read
How NakodaX finds the code worth protecting, gives developers stand ins to build against, ships a protected release and decrypts the code only in memory.
October 13, 2026

Source Protection · 4 min read
Customers who run your software on their own servers usually get a readable copy of the code. Here is how to ship it encrypted, and a free app you can unlock yourself.
October 26, 2026