Source-Code Protection for Python & PHP
SitrTech is a hosted platform that protects your source code so you can deliver software to customers without exposing your intellectual property. It encrypts Python and PHP projects file-by-file with AES-256-GCM and runs them behind a compiled native loader.
Instead of shipping readable source, you ship a protected build. Static analysis and reverse-engineering become far harder and impractical, and each build can be licensed and bound so it only runs where and when you allow.
You can protect code three ways — upload to the platform, call the REST API from your pipeline, or run the local CLI so your source never leaves your machine — and the protected output runs fully offline.
How SitrTech protects your code
Protection is applied per file and enforced at runtime by the compiled loader, so it travels with the build.
- AES-256-GCM authenticated encryption of every source file
- A native compiled loader that decrypts in memory at import — no per-call overhead once loaded
- License binding by hardware, domain, IP range or time window
- Per-customer key isolation, so one customer's build can't unlock another's
- Offline runtime — protected code runs without phoning home
Encryption vs. obfuscation — why it matters
Obfuscation renames variables and mangles structure, but the original logic is still present in the shipped files and can be recovered with enough effort. SitrTech encrypts the source itself: without the loader and the key, the files are ciphertext. That is a materially stronger protection model for code you hand to customers.
Who uses it
Teams that deliver software to third parties and need their IP to stay protected after handover.
- Software vendors shipping on-premise builds to customers
- Agencies and freelancers delivering client work they don't want resold
- Odoo / Frappe partners protecting custom modules before delivery
- Product teams issuing time-limited trials or per-customer licenses
Frameworks we protect
Odoo, Frappe, Django, Flask, FastAPI, Tornado, WordPress, Laravel and plain PHP — encrypt any of them with a single command or one API call.
Frequently asked questions
Does the protected code run at the same speed?
Files are decrypted once at import, then run at native speed — there is no per-call overhead. There is a small one-time startup cost and a slightly larger build size.
Does my source code leave my machine?
In local (CLI) mode your source never leaves your machine — only a line count is sent to authorize the operation. On the hosted platform you upload the project to be encrypted on our servers.
How is this different from a minifier or obfuscator?
A minifier or obfuscator still ships your real logic in a disguised form. SitrTech encrypts the source with AES-256-GCM, so the shipped files are ciphertext that only the licensed native loader can run.
Can I stop a customer from reselling my build?
Yes — bind each build to a machine, domain, IP or expiry. The rules are encrypted inside the files and enforced by the loader, so a copied build won't run outside its license.
Which languages and frameworks are supported?
Python (Odoo, Frappe, Django, Flask, FastAPI, Tornado) and PHP (WordPress, Laravel and plain PHP) — nine frameworks in total.
Get started · read the documentation or see the capabilities.