Free, and it stays free.
Everything that runs on your machine or in your CI against HubSpot's public APIs is free and stays free. The licence will not tighten.
The promise, in writing.
It is in the README and in a decision record, so changing it would be public and on the record.
Free and stays free. The licence will not tighten.
Everything that runs on your machine or in your CI against HubSpot's public APIs is free and stays free. The licence will not tighten.
A hosted service will charge for what a laptop cannot provide. It never charges for a feature the CLI already has, and a feature that runs locally or in CI can never move to the hosted service only.
What each part is licensed under.
Kalup's buyers are agencies, and rival agencies need to trust that the open core stays open. The licences are chosen for that.
- Engine, CLI, client and code generatorsApache-2.0
An express patent grant and a trademark clause. Every published package declares it, with
LICENSEandNOTICEat the repo root. - Blueprint contentMIT or 0BSD
Blueprints come later. They are copied into your repo, so their licence carries no notice obligations.
- What Kalup generates for youYours
Config files, docs and generated code belong to you.
Where the line sits.
If it runs on your machine or in your CI against HubSpot's public APIs, it is on the free side. The hosted service is for teams, it comes later, and it gets its own pages.
Open source
free, always- The CLI and the engine
pull,plan,compare,apply,snapshot,docs- The typed client and code generators
- State on your machine or in your CI
- Every future command that runs locally or in CI
Hosted, later
for teams- Shared state with locking and history
- Scheduled snapshots
It runs the same open engine. It adds what a laptop cannot do.
Sign off, no CLA.
Contributions use a Developer Certificate of Origin: add a sign-off line to each commit. There is no Contributor Licence Agreement. A DCO check in CI makes sure every commit is signed off.
Why no CLA.Apache-2.0 already lets anyone, the maintainer included, build on the code. A CLA would add little, and it is the tool that makes a later relicense possible. Not asking for one is part of the promise.
Before you open a pull request.Read docs/vision.md, docs/architecture.md and the decision records in docs/adr/. Tests never touch the network, fixtures use invented names, and pnpm build && pnpm check && pnpm test passes.
What gets built.The roadmap sets the order. If something is underspecified, open an issue before the code.
git clone https://github.com/scopiousdigital/kalup.git
cd kalup
pnpm install
pnpm build && pnpm check && pnpm test
# sign off every commit (DCO)
git commit -s -m "Describe the change"