NakodaX

NakodaX blog/Source Protection·2 min read

How do you share source code in due diligence safely?

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.

Pallav Boonlia

By Pallav Boonlia

Founder & CTO, NakodaX ·

A sealed glass archive suspended between two dark platforms by a fine teal light path.
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?

What is the risk in code due diligence?

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.

What does NakodaX change?

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.

What if the buyer needs to read the protected files themselves?

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.

What else is shared in diligence?

Contracts, financial models, architecture papers and customer information. Each needs its own recipient, expiry and revoke decision. Document Protection can do this for documents.

What does this not do?

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.

The takeaway

Share properly, and decide in advance what happens when the process ends.

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 buyer review my product without keeping my code?
They can run and test it under a license with an end date. When it ends, the protected files stop working.
What happens if the deal falls through?
Revoke the license. The protected files stop working at the next key request.
Does this cover contracts and financials too?
Not Source Protection. Use Document Protection for those, with expiry and revoke.

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.