1. What is and is not ZeRaLD
ZeRaLD, including proprietary application code, interface, branding and documentation produced by SW11 Software Ltd, is proprietary software. A ZeRaLD licence does not convert independently licensed software into SW11 Software property and does not replace the licence that applies to a third-party component.
Third-party software can appear in three different places: components used to build or run the ZeRaLD platform itself; software that ZeRaLD obtains or configures on a customer-controlled server; and dependencies selected by a customer's own project. Those relationships are distinct.
2. Components used by the ZeRaLD platform
The ZeRaLD web application uses third-party framework, Composer/PHP and JavaScript packages. The authoritative dependency inventory for a particular release is the package manifest and lock-file set shipped with that release. Those packages remain governed by their own licences, copyright notices and upstream terms.
SW11 Software maintains a release-level third-party notice inventory for material that must accompany software ZeRaLD redistributes. Where an applicable licence requires preservation of copyright, attribution or licence text, the release process must preserve it.
3. Runtime acquisition — server software, packages and language runtimes
When you authorise ZeRaLD to prepare or manage a server, ZeRaLD can use the server operating system's package manager and relevant upstream software sources to obtain ordinary server components, developer tooling and language runtimes required by the selected project or ZeRaLD server environment.
That software is acquired from the relevant operating-system repository or upstream source and installed onto the server you control. Availability, package contents, updates and licensing are determined by the relevant source. ZeRaLD automates acquisition and configuration; SW11 Software does not claim ownership of software merely because ZeRaLD installed it.
4. Project dependencies selected by customers
A project deployed through ZeRaLD may declare or request packages through Composer, npm or another ecosystem package manager. Those dependencies are selected by the project, not relicensed as part of ZeRaLD, and remain subject to their own licences and provider terms.
Where an AI or developer modifies a customer's dependency manifest, that change remains part of the customer project. ZeRaLD's ability to install or build the project does not constitute a legal review of the compatibility of every dependency licence with the customer's intended distribution model.
5. Separate licences and obligations
Open-source software is not unlicensed software. Permissions and obligations vary between licences. A component may require preservation of notices, source-code availability in particular circumstances, attribution, disclosure of modifications or other conditions. The applicable upstream licence controls those obligations.
The proprietary ZeRaLD licence applies only to ZeRaLD material owned or licensed to SW11 Software under terms that permit that treatment. Nothing in the ZeRaLD Terms is intended to remove rights granted directly to you by the licence of a third-party component.
6. Preserved notices, copyright and attribution
ZeRaLD's internal THIRD_PARTY_NOTICES inventory accompanies the release source and records the distinction between ZeRaLD code, platform dependencies, runtime acquisition and project dependencies. Package-specific copyright and licence information remains available through the relevant package metadata and upstream distribution.
If SW11 Software begins redistributing a third-party binary, library or other component whose licence requires additional bundled material, the release must include that required material before distribution.
7. Third-party services are different from third-party software
ZeRaLD also interacts with services operated by other organisations, including infrastructure, domain/email services and customer-selected AI providers. Those services are governed by their own service terms and privacy arrangements rather than an open-source software licence. Our Privacy Notice explains the current data-processing relationships relevant to ZeRaLD.
A customer-selected AI provider does not become SW11 Software's software licensor or automatically become our subprocessor merely because a customer chooses to send project context to it through AI Handoff.
8. Updates, availability and security
Third-party packages and repositories can change independently of SW11 Software. Upstream maintainers can publish security updates, withdraw packages, change supported versions or alter distribution channels. ZeRaLD may update its compatibility or installation logic to respond to those changes.
ZeRaLD does not promise that every third-party package will remain available indefinitely. Security and compatibility decisions concerning upstream components may require an update, replacement or removal.
9. Customer responsibilities
You remain responsible for the software and licences you deliberately add to your own project and for complying with obligations triggered by how you distribute or use that project. If your project is built for a regulated, proprietary or redistribution-sensitive environment, you should assess the licences of the dependencies you choose.
ZeRaLD's automated deployment of a project is not a representation that every third-party licence in that project is suitable for every commercial use.
10. Changes to this notice
This notice is maintained as the ZeRaLD dependency and runtime model evolves. Material changes to how ZeRaLD redistributes or acquires third-party software must be reflected in the release notice inventory and, where relevant, the Terms & Conditions.
