hexagon logo

Sneaky Sneaky

We have a -government- customer that wants to buy our code so they can run the program themselves. We are using some code that we consider proprietary in nature (I.E. we developed internally how to obtain results that they seek) We want to hide that or lock their ability to understand what we do, as to retain other programs with said company - but out of good grace sell a program that is obsoleting so they may run it at their pleasure.

What sort of sneaky sneaky tricks do you guys have to bury code deep?
I was thinking of a pulling the code from a text file (have never done this). But I'm also not sure how robust that can be.
Parents Reply Children
  • No doubt, but to them it's proprietary. Our QM has the acceptance of methods that are reliable/repeatable as the standard. I.E. it's written into our standard that the customer accepts the methods we utilize under the assumption due diligence was utilized to ensure it's accuracy. This allows 'proprietary' information to be kept confidential. Whether proprietary in nature or not, I don't have to share my methods unless otherwise agreed upon - therefore everything is 'proprietary'.

    No doubt, otherwise. It's no real big secret.