Use cases/On premises and pilots
A pilot that ends when you say. An install you can take back.
On premises installs, pilots and trials on the customer's own servers. The parts that make your product yours ship locked, and you keep one switch per customer.
Works withSource

In short
A pilot or an on premises install usually puts a full, readable copy on the customer's servers, and it keeps running after the trial or contract ends. With NakodaX, the parts that make your product yours ship locked and unlock only while you allow it. When a pilot ends, you switch off that customer, and only that customer.
Who it's for
Sales engineers, deployment and customer success teams
What you share
- On premises installs
- Pilot and trial builds
- Releases a partner deploys for you
- Updates you ship to each customer
Has this happened to you?
Real moments where control slips, and the product that keeps it.

On-premise pilots that never expire
A 60-day evaluation, deployed on their infrastructure, three years ago. It’s still running.
Fixed with Source Protection
Software that keeps running after the contract ends
Your software runs on your customers’ servers. The contract ends. The servers don’t.
Fixed with Source Protection
Source code held by an outside dev agency
An outside team helped build your product. The engagement ended. Their copies of your codebase didn’t.
Fixed with Source Protection
How NakodaX helps.
Source Protection covers it.
Protected releases and one switch per customer
A trial that ends when you say, and an install you can take back.
Explore Source ProtectionGo deeper
Articles and a video on the same problem, and how NakodaX handles it.
Blog
Your algorithm is ten files. Everything else is plumbing.
Most of a repository is replaceable. A small part is not. Start by protecting the modules that carry the business logic.
Read moreBlog
When the acquirer wants to see the code
Technical due diligence means sharing source code with a company that may not buy you. Review need not leave an ordinary working copy behind.
Read moreVideo
Source Protection for software deployed outside your business
When software has to run in a customer or vendor environment, see how NakodaX keeps selected proprietary components out of the readable release.
Watch (3:29)
On premises and pilots questions
Can we end a pilot without chasing the customer?
Can we see where our software is running?
Which languages can we protect?
Does switching a customer off stop it straight away?
Tell us what you share, and with whom.
We will show you which product fits, on your own files, data or code.
