Copyright of custom pyrevit

Hello,
How you manage your copyright when you sail to a company your pyrevit custom plugin ?
Because this is open source this is easy to divulgate your plugin. Do you right something about this in your contract ?

If you are developing commercial - then you need to go full adding with C# and .Net and build in a licensing system.

Python isn’t the language for commercial apps. All you need is notepad to copy it.

It seems you can compile you python code in something difficult to recover with reverse engineering. Maybe there is a way like this.

You can use a bytecode compile *.pyc file, but this is simple to decompile.
Best you can do is make dll files for pyRevit and try and work some licensing into your system. But without a licensing system, all you need to do is copy files from one system to another.

Nice idea the dll but the licence seems to be difficult to deploy.
I have a crazy but simple idea. At the beginning of my script I create an IF with the date of delivery + one year. If the date expire I print « your licence is expired » and I exit the script.
They can always copy the script but at least it will works only one year !

1 Like

Since plugins can be easily copied, the real protection comes from contracts and licensing terms, not just copyright law.

1-Specify whether the company gets an exclusive or non-exclusive license.
2-Define scope, internal use only, no redistribution and no resale.
3-State clearly that you retain copyright in the plugin.
4-The company is only buying a license to use it, not ownership of the code.

1 Like

I can say that with the Development of AI, there are companies out there SPECIFICALLY marketed themselves to modify private codes “Just enough” to avoid a lawsuit.

but also with the same argument, with the help of AI converting python code to C# wouldn’t be a hindrance anymore.

1 Like