Run it on your own network
ZyncTools has no backend. Every tool runs in the browser, which means the whole suite is a folder of static files — and a folder of static files can live on your intranet, behind your firewall, with no route to the outside world at all.
The problem this solves
If you handle documents that belong to somebody else — a client contract, a patient record, a tax return, a signed offer letter — you are usually not allowed to upload them to a third-party website to be processed. Not because the website is untrustworthy, but because sending the file is itself the disclosure.
So the work gets done some other way: an expensive desktop licence for everyone who might occasionally need to merge two PDFs, or a shadow-IT habit of using a free site and not mentioning it.
There is no upload step to review. The file is opened by the browser, changed by the browser, and saved by the browser. Nothing is transmitted, because there is nowhere for it to be transmitted to.
What deploying it actually involves
It is a static site. There is no database, no runtime, no container, no scheduled job and nothing to patch on a server.
- Copy the folder onto any web server, file share or intranet host.
- Serve it over HTTPS so the browser grants clipboard and file access.
- That is the deployment.
A handful of tools reach out to a public CDN the first time they are used, to fetch a library for a heavier job like OCR or PDF rendering. Those files can be vendored locally instead, so an air-gapped install never makes a single outbound request. Ask and we will point you at the list.
Licensing
ZyncTools is published under AGPL-3.0-or-later. You do not need our permission to run it, and for a great many organisations that licence is perfectly fine — take it, deploy it, done.
The AGPL does carry obligations. If you modify it and make it available over a network, you have to offer your changes back under the same terms. Some legal departments will not accept copyleft on internal software at all. A commercial licence exists for those cases.
- Every tool, no feature gates
- Unlimited users and installs
- Community support via GitHub
- Source available, modify freely
- No copyleft obligation on your changes
- A signed agreement your legal team can file
- Written answers for security review and DPIA
- A fully offline build with no CDN calls
- Named contact and an agreed response time
Who this tends to suit
Law firms and in-house legal, clinics and hospital departments, accountancy practices, HR teams, schools, and anyone working to a public-sector procurement rule that treats an upload as a data transfer.
Talk to us
We are looking for a small number of design partners — organisations willing to deploy it, tell us what breaks and what their security review asked for, in exchange for a permanent licence at the partner rate. If that sounds like your organisation, get in touch.
Nothing on this page is legal advice, and it does not replace your own review. It describes how the software works so that your review has something accurate to look at.