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 the architecture document, 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 and CLI, and later the client and code generatorsApache-2.0
An express patent grant and a trademark clause. Both packages,
kalupand@kalup/core, already declare it in theirpackage.jsonand ship theLICENSEandNOTICEkept at the repo root. - Blueprint contentMIT or 0BSD
kalup addcopies a blueprint into your config files, so a permissive licence keeps notice obligations out of your repo. Kalup ships no blueprint content of its own yet; the first will carry this licence. - What Kalup generates for youYours
Config files and docs, and later any 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, comes after pipelines, schema writes and association labels, and gets its own pages.
Open source
free, always- The CLI and the engine, with
init,pullandvalidate0.2 compare,plan,snapshotanddocs0.2apply, and state on your machine or in the repository0.2- A CI recipe for
apply, with state on a branch per portalRecipe - Blueprints and
blueprint upgrade0.2 - The typed client and code generatorsLater
- Every future command that runs locally or in CI
Hosted, for teams
Later- Shared state and coordination, with history
- Scheduled observations of client portals
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. The pull request template asks you to confirm 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 AGENTS.md and docs/architecture.md. 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"