Terms of licence

The shape of the deal, before the clauses: you buy once, you own the licence forever, updates are included, support is a separate purchase. There is no subscription to cancel, no tier to upgrade, no renewal date. Any language below that appears to assume otherwise is a defect — report it.

PURCHASE

ONE-TIME

LICENCE

PERPETUAL

UPDATES

INCLUDED

SUPPORT

SOLD SEPARATELY

SUBSCRIPTION · TIERS

NONE · NONE

DRAFT — PENDING LEGAL REVIEW

The structure below is checked against how the product is actually sold. The clause wording has not been reviewed by qualified counsel; §7 (governing law) is deliberately left open rather than guessed.

§1 The licence

A licence is purchased once, per deployment, and is perpetual: it does not expire, does not renew, and does not depend on any service from us to keep working. The software runs entirely in your infrastructure and performs its licence check offline — if we disappeared tomorrow, your deployment would not notice. The licence covers the versions released during your update entitlement (§2) and every version you already run, forever.

§2 Updates

Updates — including security fixes — are included with the purchase. They are delivered as signed artefacts you pull and apply yourself; nothing auto-updates and nothing phones home to check. Applying them is your operational decision on your schedule.

§3 Support

Support is sold separately, as engagements — it is not a tier, not a subscription, and not required for the software to function. What a support engagement involves, including how diagnostic material is handled, is described in the privacy policy, B.2. Community and documentation access require no purchase.

§4 Permitted and not

Permitted: running the deployment for your organisation, extending it with custom connectors via the SDK, modifying configuration, and moving the deployment between your own environments. Not permitted: reselling, sublicensing, or operating the software as a service for third parties, and removing or defeating the licence mechanism. Extending via the published SDK is expressly intended use, not a grey area.

§5 Warranty and liability

The software is warranted to materially conform to its documentation. Because you operate it in infrastructure we cannot see, remedies centre on fixes and workarounds delivered as updates. Liability caps and statutory exceptions are exactly the kind of wording that must come from counsel, not a website — the reviewed clause will replace this paragraph.

§6 Termination

There is no subscription, so there is nothing to cancel and no renewal to miss. The licence can end only one way: material breach of §4 that remains uncured after notice. Ordinary ending of use is simpler — stop running it; nothing needs to be told to anyone.

§7 Governing law and jurisdiction

OPEN — WITH COUNSEL

Governing law and venue for a maintainer outside the EU selling to EU organisations is a real legal question, not a blank to fill with a plausible city. This clause ships only after review. Procurement teams that need it settled before purchase: raise it in the licence conversation.