Open source
The parts of pendlooq that touch your keys and files are open. The cloud that runs our business is not.
What is open
| Part | Code | License |
|---|---|---|
| Client: interface and local API | Open | FSL-1.1-ALv2 |
| Runner | Open | FSL-1.1-ALv2 |
| Cloud: sync, thread tracking, notifications, billing, teams | Closed | Proprietary |
The public repository opens with the first public release.
Why open
You trust pendlooq with passwords, tokens, folders and conversations. Open code makes that trust verifiable, above all for the runner, which holds the keys and runs commands.
Why the FSL
The code is open to read, build, use and run yourself. The one thing it does not allow is building a competing product or service on it. Every version converts to Apache 2.0 two years after release.
Contributing
Contributions are welcome under a Contributor License Agreement (CLA), which keeps the licensing of the project in one hand.
The name
You may fork the code, but not call the fork pendlooq.
Self-hosting
Running the whole stack yourself is technically possible, since the code is open, but it is not supported or documented. Running your own runner with the pendlooq cloud is.
pendlooq builds only on permissively licensed components (MIT, Apache 2.0 and similar); GPL and AGPL dependencies are excluded by an automated license check.