Licensing
We own the core and license it on perpetual terms. A licensee builds on it with confidence that its business never depends on a single supplier.
What each side holds
What a licensee receives
- A perpetual, irrevocable licence to the Shared Core Engine
- Source access, with the source held in escrow
- Its own deployment, tenants, encryption keys and ledger
- Ownership of the packs it builds for its own market
- Every core improvement, on a published release schedule
What Distribution Networks keeps
- Ownership of the core code, data model and event catalogue
- The core roadmap, versioning and architecture review
- Repositories, cloud and AI accounts in our legal name
- No rights in any client's data, which stays with the client
The principles every solution signs up to
Solutions plug in through one Solution Contract
A third solution can be added without touching Be or BCS.
The core is never forked
A capability one solution needs is added to the core for every solution.
Shared code, never shared data
Separate deployments, keys and ledgers; consent for anything that crosses.
One name, one meaning
Engines, services and packs carry the same names in code, screens and contracts.
The core is versioned on its own
Each solution pins a core version and moves to the next one deliberately.
Questions licensees ask first
Who owns the data?
The client does. Distribution Networks holds no rights in any client's data. Each solution runs in its own deployment with its own keys, and data crosses between solutions only with recorded consent.
What if we need a change to the core?
The core is never forked. A capability one solution needs is added to the core for every solution, and it reaches every licensee on the published release schedule.
What protects us if the supplier is not there?
Licences are perpetual and irrevocable, source is held in escrow, and step-in rights mean a licensee's business does not depend on a single supplier.
Can we keep a release stable?
Yes. Each solution pins a core version and moves to the next one deliberately, when it chooses to.
Who owns what we build?
The licensee owns the packs it builds for its own market: rules, workflows, content and configuration.