Which frameworks does SitrTech support?

Python: Odoo, Frappe/ERPNext, Django, Flask, FastAPI and Tornado. PHP: WordPress, Laravel and generic PHP projects — nine frameworks in total.

How does SitrTech protect my source code?

Every file is sealed with authenticated AES-256-GCM under its own unique key, then executed by a compiled per-OS/arch/Python native loader. The master key lives only inside that native binary, never in readable code, and each build can be bound to an expiry, domain, IP range, MAC, machine-id, hostname, disk serial or Odoo database.

Will encryption slow down my application?

The impact is negligible. Protected code runs at ordinary Python speed once loaded — there is only a one-time load per module at first import (about 0.1s), and the app then runs fully offline with no per-call cost.

Does my source code get uploaded to SitrTech?

In local mode your source never leaves your machine — encryption runs on your side and only line counts are metered for billing.

Can I lock a protected build to a customer or a machine?

Yes. You can bind a build to an expiry date, a domain, an IP/CIDR range, a MAC address, a machine-id, a hostname, a disk serial or an Odoo database. The rules are enforced locally at runtime and cannot be edited or bypassed.

What platforms does the protected code run on?

Python 3.8 to 3.14 on Linux, macOS and Windows. The same protected build runs everywhere, including fully offline.

Odoo Module Protection & Licensing

SitrTech lets Odoo developers and partners protect custom modules before handing them to clients. Zip your module, encrypt it, and deliver a protected build instead of readable source.

Your .py files are encrypted with AES-256-GCM while __manifest__.py stays readable so Odoo still discovers and loads the module — and you can license each delivery.

It works for Odoo 13 through the latest releases, on both Community and Enterprise, and fits into your existing delivery pipeline.

Built for Odoo partners

Ship protected, license-bound modules without slowing delivery.

Encrypt module .py files; keep __manifest__.py intact so Odoo loads the module
Bind a module to a machine, domain, IP range or expiry date
Community and Enterprise editions supported (Odoo 13 to the latest)
Automate protection in CI/CD before handover

Stop unpaid reuse of your modules

Custom Odoo modules are easy to copy between databases and clients once the source is in hand. Encryption plus licensing means a module only runs on the deployment you delivered it to — copying the folder to another server or database won't make it work.

Common use cases

How Odoo teams use SitrTech.

A partner delivering a paid custom module to a client's on-premise Odoo
A vendor selling the same module to many customers, each license-bound
Time-limited pilots before a client commits
Protecting proprietary business logic inside an otherwise open module

License every delivery

Stop unpaid reuse and redistribution by binding each module to the customer you delivered it to — enforced offline by the loader.

Frequently asked questions

Which Odoo versions are supported?

SitrTech supports Odoo 13 through the latest versions, for both Community and Enterprise editions.

Does the module still load after protection?

Yes — __manifest__.py stays readable so Odoo discovers and loads the module; the Python logic inside is encrypted and executed through the native loader.

Can I lock a module to one client's server?

Yes — bind it to that machine, its domain, an IP range, an expiry date, or a combination, so the module won't run elsewhere.

Will encryption break Odoo's ORM or views?

No — your models and business logic run normally through the loader, and non-Python assets (XML views, data files, the manifest) are left intact.

Can I automate this in my delivery pipeline?

Yes — use the CLI or REST API to encrypt modules as a build step in GitHub Actions, GitLab CI or Docker before handover.

Get started · read the documentation or see the capabilities.