An ApocOS unit is an aggregation. Alongside FlatCoder's proprietary ApocOS software, it bundles open-source system software (under GPL / LGPL / permissive licences), open map & knowledge data (OpenStreetMap, Wikipedia, and others) and language models — each under its own licence, which the ApocOS licence and EULA do not override.

APOCOS THIRD-PARTY SOFTWARE, DATA AND CONTENT NOTICES

Name: ApocOS Node
Brand: ApocOS
Price: 599.99 GBP
Availability: InStock

ApocOS is built using third-party software, open-source software, datasets, language models, documentation and other materials supplied under their respective licences.

This document identifies the principal categories and significant third-party components that may be distributed with ApocOS.

The exact components included depend on:

ApocOS version and build;
processor architecture;
selected edition;
whether desktop support is included;
whether local AI models are included;
installed map and knowledge packs;
optional security components; and
subsequent updates or additional packages installed by the user.

This document does not replace the licence applicable to any third-party component.

Where there is any conflict between this document and the licence supplied with a third-party component, the applicable third-party licence governs that component.

1. APOCOS PROPRIETARY SOFTWARE

Software developed by FlatCoder Ltd specifically for ApocOS is proprietary unless a particular file or component expressly states otherwise.

This includes, where applicable:

ApocOS services and daemons;
the aios command-line interface and ApocOS-specific commands;
ApocOS user interfaces and dashboard;
orchestration and integration software;
ApocOS-specific installers and configuration systems;
hardware detection and management software;
knowledge, mapping and data integration software authored by FlatCoder Ltd;
ApocOS-specific scripts and utilities;
ApocOS documentation authored by FlatCoder Ltd; and
other original FlatCoder Ltd source code and executable software.

These components are governed by the:

APOCOS PROPRIETARY SOFTWARE LICENCE

and the applicable:

APOCOS END-USER LICENCE AGREEMENT (EULA)

They are not open-source software merely because they are distributed alongside or operate with open-source components.

See:

LICENSE EULA.md

2. DEBIAN GNU/LINUX

ApocOS is based on Debian GNU/Linux.

Debian consists of software from many independent projects and copyright holders and is not distributed under one single software licence.

Individual Debian packages may be licensed under terms including, but not limited to:

GNU General Public License (GPL);
GNU Lesser General Public License (LGPL);
Apache License 2.0;
MIT / Expat licences;
BSD licences;
Mozilla Public License;
Python Software Foundation licences;
ISC licence;
Artistic licences; and
other free and open-source software licences.

The licence and copyright information applicable to an installed Debian package can generally be found at:

/usr/share/doc/<package>/copyright

Common licence texts supplied by Debian can generally be found under:

/usr/share/common-licenses/

The installed package database may be inspected using Debian package-management tools including:

dpkg -l

The rights granted by the respective licences of Debian components are not restricted by the ApocOS Proprietary Software Licence or EULA.

3. LINUX KERNEL

ApocOS includes the Linux kernel supplied through Debian.

The Linux kernel contains code contributed by numerous copyright holders and is distributed principally under the GNU General Public License version 2, together with applicable exceptions and other licensing information for particular files.

The authoritative copyright and licensing information for the Linux packages included in a particular ApocOS build is supplied with those packages.

Where source-code availability obligations apply, see:

GPL-SOURCE-OFFER.txt

4. GNU AND OTHER SYSTEM SOFTWARE

ApocOS includes GNU utilities, system libraries, boot software, filesystem utilities and other components supplied through Debian.

Each component remains subject to its respective licence.

Nothing in the ApocOS proprietary licence changes the rights granted under those licences.

Package-specific notices are available under:

/usr/share/doc/<package>/copyright

5. PYTHON AND PYTHON PACKAGES

ApocOS uses Python and may include Python packages installed from Debian repositories and/or other upstream package sources.

Python itself and each third-party Python package remain subject to their respective licences.

The precise Python dependency set may vary between ApocOS releases.

Third-party Python packages are not covered by the ApocOS Proprietary Software Licence merely because ApocOS services import or otherwise use them.

ApocOS release builds should retain or provide applicable licence and attribution information for third-party Python dependencies distributed with the product.

6. RUST AND RUST DEPENDENCIES

Parts of ApocOS are implemented using Rust.

ApocOS builds may incorporate third-party Rust crates into compiled ApocOS binaries.

Those crates remain subject to their respective licences.

The proprietary status of FlatCoder Ltd’s original ApocOS source code does not remove or alter licence notices or obligations applying to third-party Rust dependencies incorporated into ApocOS software.

The exact Rust dependency set is determined by the dependency lock file used for the corresponding ApocOS release.

ApocOS release records should preserve the dependency versions and applicable licence information for third-party crates used in each distributed build.

7. OLLAMA

ApocOS editions providing local artificial-intelligence functionality may include Ollama.

Ollama is third-party software and is not owned by FlatCoder Ltd.

Ollama is distributed under its applicable upstream licence.

The version distributed with ApocOS may vary between releases.

The licence applicable to Ollama governs Ollama itself independently of the ApocOS Proprietary Software Licence.

8. LANGUAGE AND EMBEDDING MODELS

ApocOS may include local artificial-intelligence models and embedding models.

Depending on the selected build, these may include models from families such as:

Qwen;
Qwen Coder;
Nomic Embed; and
other models selected for a particular ApocOS release.

AI model licences are separate from the licence of the software used to run them.

The fact that a model can be downloaded or executed through Ollama does not mean that the model is licensed under the Ollama software licence.

Each model remains subject to the licence, acceptable-use terms and other conditions specified by its model publisher or rights holder.

Before a model is approved for inclusion in a commercially distributed ApocOS image, FlatCoder Ltd should verify and record:

exact model name;
exact model/version or digest;
publisher;
source;
applicable licence;
commercial-use permission;
redistribution permission;
attribution requirements;
notice requirements; and
any use restrictions.

Only models approved for redistribution as part of the relevant ApocOS release should be included in commercial builds.

9. OPENSTREETMAP

ApocOS map and geographic functionality may contain data derived from OpenStreetMap.

OpenStreetMap data is made available under the Open Data Commons Open Database License (ODbL) 1.0.

OpenStreetMap contributors retain rights in the underlying database.

Where ApocOS distributes an OpenStreetMap-derived database or displays maps or other produced works derived from OpenStreetMap data, the applicable ODbL attribution and other requirements must be observed.

Appropriate attribution should be presented within the ApocOS mapping interface and/or associated legal information as required for the relevant use.

OpenStreetMap data is not owned by FlatCoder Ltd.

10. ELEVATION AND TERRAIN DATA

ApocOS may include digital elevation model (DEM), terrain or related geographic datasets.

The exact datasets included depend upon the geographic data pack used for a particular ApocOS release.

These datasets may originate from organisations including:

NASA;
USGS; and
other public or open-data providers.

Each dataset remains subject to its own terms, attribution requirements and applicable copyright or public-domain status.

The exact source, dataset version and applicable terms should be recorded when the data is incorporated into an ApocOS release.

11. SOILGRIDS

ApocOS may include soil information derived from SoilGrids, provided by ISRIC — World Soil Information.

SoilGrids data remains subject to the licence and attribution requirements specified by its provider for the particular dataset/version distributed with ApocOS.

FlatCoder Ltd does not claim ownership of the underlying SoilGrids dataset.

Where SoilGrids data is transformed, clipped, indexed or incorporated into an ApocOS geographic data pack, this does not remove the applicable third-party licence or attribution requirements.

12. CHELSA

ApocOS may include climate information derived from CHELSA datasets.

CHELSA data remains subject to the terms applicable to the particular dataset/version incorporated into the relevant ApocOS release.

Where the applicable dataset is released under CC0 or another open-data licence or dedication, those terms govern the underlying data.

FlatCoder Ltd does not claim ownership of the underlying CHELSA data.

13. WIKIPEDIA, WIKIMEDIA AND ZIM CONTENT

ApocOS may distribute offline knowledge archives in ZIM format.

These archives may contain material derived from Wikipedia, Wikimedia projects or other content sources.

Wikipedia text is generally made available under Creative Commons Attribution-ShareAlike terms and may also be subject to additional applicable licensing terms depending on the material and its history.

Images and other media contained in Wikimedia projects may have licences that differ from those applicable to article text.

ZIM is a storage/archive format and does not itself determine the copyright licence of the content contained within a ZIM archive.

Accordingly, every ZIM archive approved for commercial ApocOS distribution should have its:

source;
archive name;
creation/version date;
content provider;
applicable licence(s); and
attribution requirements

recorded as part of the release manifest.

FlatCoder Ltd does not claim ownership of third-party encyclopaedic or Wikimedia content merely because it is indexed, searched or displayed by ApocOS.

14. DEVDOCS AND OFFLINE DOCUMENTATION

ApocOS may include offline programming or technical documentation sets.

Such documentation remains subject to the copyright and licence applicable to the original documentation.

Packaging documentation into an offline archive, indexing it or embedding it into the ApocOS knowledge system does not alter its licence.

Each documentation set approved for distribution should therefore be recorded individually in the corresponding release manifest.

15. DESKTOP SOFTWARE

Desktop-enabled ApocOS builds may include a graphical desktop environment and supporting software supplied through Debian.

This may include components such as:

graphical display infrastructure;
desktop/window-management software;
login/session-management software;
web-browser components;
fonts;
themes;
graphics drivers; and
associated libraries.

These components remain subject to their respective upstream and Debian licences.

Package-specific copyright information is available under:

/usr/share/doc/<package>/copyright

16. FIRMWARE

ApocOS builds may contain firmware required to support hardware such as:

wireless adapters;
graphics hardware;
storage controllers;
network adapters; and
other devices.

Firmware may be distributed under licences that differ from conventional free and open-source software licences.

The inclusion of firmware in ApocOS does not place that firmware under the ApocOS Proprietary Software Licence.

The applicable firmware licence governs each firmware component.

16A. NVIDIA GPU DRIVER

ApocOS builds may include the NVIDIA proprietary graphics/compute driver (the NVIDIA kernel module, the CUDA driver library, and associated utilities), so that hardware with an NVIDIA GPU can use accelerated local artificial-intelligence functionality.

The NVIDIA driver is third-party software and is not owned by FlatCoder Ltd.

It is distributed under the NVIDIA Software Licence (a non-free licence that permits redistribution for hardware enablement but does not permit modification of, or distribution of source for, the binary components). Its licence governs the NVIDIA driver independently of the ApocOS Proprietary Software Licence.

Its inclusion is a hardware-enablement convenience: on a machine without an NVIDIA GPU the driver has no effect. A build produced with --no-nvidia omits it entirely.

17. SECURITY EDITION

Certain ApocOS releases may be produced as an optional Security Edition.

The Security Edition may contain additional third-party security, network-analysis, wireless-analysis, password-auditing, reverse-engineering, software-testing and related tools.

These tools remain subject to their individual licences.

Their inclusion in ApocOS does not imply that FlatCoder Ltd owns or relicenses those tools.

The installed package-specific licence information remains available through the Debian copyright files where the tools are supplied as Debian packages.

The Security Edition is intended only for lawful and authorised use as described in the applicable ApocOS documentation and EULA.

18. SECURITY DATA PACKS

Optional ApocOS Security builds may include additional third-party security datasets or archives.

These may include resources such as:

SecLists;
ExploitDB;
SearchSploit-related data;
password/wordlist data; and
other security research datasets.

Such datasets may have licences, copyright terms and redistribution requirements that differ from the software packages that consume them.

Each security dataset must therefore be independently approved for commercial redistribution before inclusion in a shipping ApocOS image.

The relevant release manifest should identify the dataset, source, version/date and applicable licence.

19. ROCKYOU AND OTHER WORDLISTS

Some optional security builds may contain password wordlists or other research data.

The provenance, copyright status and redistribution rights of such datasets must be verified independently before commercial distribution.

A file being widely available on the Internet does not, by itself, establish that FlatCoder Ltd has permission to redistribute it commercially.

Any wordlist for which redistribution rights cannot be established should not be included in a commercial ApocOS release.

20. BOOTLOADERS AND UEFI SOFTWARE

ApocOS supports multiple processor architectures and may include third-party bootloaders, UEFI components and related firmware/software.

These may include software supplied through Debian and, for particular hardware platforms, separately obtained UEFI or firmware implementations.

Each such component remains subject to its respective licence.

Hardware-specific firmware distributed separately from ApocOS may also have separate redistribution terms that must be checked before bundling it with a commercial product.

21. THIRD-PARTY TRADEMARKS

Names including Debian, Linux, GNU, Ollama, OpenStreetMap, Wikipedia, Wikimedia, Qwen, SoilGrids, CHELSA and other third-party project or product names may be trademarks or otherwise protected identifiers belonging to their respective owners.

Use of those names within ApocOS documentation is for identification, interoperability and attribution purposes.

Unless expressly stated otherwise, inclusion or reference does not imply sponsorship, certification, endorsement or affiliation with FlatCoder Ltd or ApocOS.

22. SOURCE CODE AVAILABILITY

Certain third-party licences require source code or corresponding source code to be made available to recipients.

FlatCoder Ltd provides information concerning those obligations in:

GPL-SOURCE-OFFER.txt

Where required by the applicable licence, FlatCoder Ltd will make corresponding source and other required materials available in accordance with that licence.

This source-code availability obligation does not automatically extend to independently authored ApocOS Proprietary Software.

23. TECHNICAL PROTECTION AND THIRD-PARTY RIGHTS

ApocOS products may employ technical protection measures including device binding, TPM-based mechanisms, storage-device identification, licence partitions, signatures, integrity verification and other copy-protection systems.

These mechanisms protect the proprietary ApocOS software and licensed ApocOS installation.

They are not intended to remove rights that applicable third-party licences grant in relation to third-party software or data.

Where an applicable open-source licence requires recipients to be able to modify, install or execute modified versions of a covered component in particular circumstances, FlatCoder Ltd will comply with those obligations to the extent required by that licence.

24. RELEASE-SPECIFIC LICENCE MANIFEST

Because ApocOS is assembled from many independently versioned components, this document is not intended to serve as the complete package-by-package inventory for every ApocOS release.

Each commercial release should have a reproducible release-specific third-party manifest generated from the software and data actually distributed.

The manifest should record, where applicable:

ApocOS release/build identifier;
architecture;
edition;
Debian package name and version;
package copyright/licence information;
Python dependency and version;
Rust crate and version;
Ollama version;
AI model name, version/digest and licence;
ZIM archive name/version and content licence;
OpenStreetMap extract/date;
geographic dataset source/version/licence;
security dataset source/version/licence;
firmware components; and
other independently licensed material.

The release manifest forms part of the third-party compliance records for that ApocOS release.

25. NO RESTRICTION OF THIRD-PARTY RIGHTS

Nothing in:

this document;
the ApocOS Proprietary Software Licence;
the ApocOS EULA;
ApocOS copy-protection systems; or
any other FlatCoder Ltd terms

is intended to remove, restrict or replace rights that a recipient receives directly under the applicable licence of a third-party component.

The proprietary restrictions applying to ApocOS Proprietary Software apply only to software and other materials to which FlatCoder Ltd has the legal right to apply those restrictions.

26. FURTHER INFORMATION

For the licence governing proprietary ApocOS software:

LICENSE

For end-user terms:

EULA.md

For corresponding-source information:

GPL-SOURCE-OFFER.txt

For general copyright and ownership information:

NOTICE

For package-specific Debian licence information:

/usr/share/doc/<package>/copyright

For open-source compliance enquiries:

FlatCoder Ltd United Kingdom

Email: gary@flatcoder.co.uk

Third-party software, models, datasets, documentation and other materials remain copyright of their respective rights holders and are distributed under their respective terms.

Written offer for GPL / LGPL source

WRITTEN OFFER FOR CORRESPONDING SOURCE CODE
GPL / LGPL AND OTHER SOURCE-AVAILABILITY COMPONENTS
===================================================

ApocOS is built upon Debian GNU/Linux and includes third-party software distributed under the GNU General Public License ("GPL"), GNU Lesser General Public License ("LGPL"), and other free and open-source software licences.

Certain of these licences give recipients the right to obtain source code for the corresponding software.

This notice explains how to obtain source code for third-party components distributed with ApocOS where FlatCoder Ltd is required by the applicable licence to make that source available.

# SCOPE OF THIS OFFER

This offer applies only to third-party components distributed with ApocOS for which the applicable licence requires FlatCoder Ltd, as a distributor of the relevant binary or object code, to provide or offer corresponding source code.

Depending on the ApocOS release, such components may include:

```
the Linux kernel
GNU utilities
system libraries
systemd
boot and filesystem utilities
cryptographic utilities
and other GPL/LGPL or similarly licensed packages.
```

The exact software included in an ApocOS release may vary.

Package names and installed versions can be inspected on an ApocOS system using the Debian package-management tools, including:

```
dpkg -l
```

Copyright and licence information supplied with installed Debian packages can generally be found under:

```
/usr/share/doc/<package>/copyright
```

# CORRESPONDING SOURCE CODE

For components covered by this offer, FlatCoder Ltd will provide the complete corresponding source code required by the applicable licence for the version of the component distributed with the relevant ApocOS release.

Where required by the applicable licence, this will also include material necessary to build, modify or install the covered component to the extent required by that licence.

The scope of "Corresponding Source" or equivalent source-code obligations is determined by the licence applicable to the particular component.

# HOW TO REQUEST SOURCE CODE

To request corresponding source code, contact:

```
FlatCoder Ltd
United Kingdom

Email: gary@flatcoder.co.uk
```

Please identify, where reasonably possible:

```
• the ApocOS product or edition;
• the ApocOS release/build version;
• the relevant package or component; and
• the version of that package or component.
```

If you do not know the exact package or version, provide sufficient information to identify the ApocOS release or Unit concerned and we will use reasonable efforts to identify the applicable source.

# METHOD OF DELIVERY

Where permitted by the applicable licence, corresponding source may be supplied electronically, including by download.

Where an applicable licence or the circumstances of distribution require fulfilment of a written offer by physical distribution, FlatCoder Ltd will provide the required corresponding source on a durable physical medium customarily used for software interchange.

Any charge for physical fulfilment will not exceed the reasonable cost of physically performing the source distribution, to the extent required by the applicable licence.

Electronic access to source code may be provided without charge.

# DURATION OF OFFER

Where a component has been distributed under licence terms requiring a written source-code offer to remain valid for a specified period, this offer will remain valid for at least that required period.

For GPL components distributed under terms requiring a three-year written offer, this offer is valid for at least THREE (3) YEARS from the date of the relevant distribution, and for any longer period required by the applicable licence.

Where the applicable licence requires source availability for longer, that longer requirement applies.

# DEBIAN SOURCE ARCHIVES

Many third-party components distributed with ApocOS originate from Debian.

Debian publishes source packages corresponding to its binary packages, including historical versions through Debian archive and snapshot infrastructure.

These resources may provide a convenient additional way to obtain source code.

For example:

```
https://www.debian.org/distrib/packages
https://snapshot.debian.org/
```

On a suitably configured network-connected Debian system, source packages may also be retrievable using Debian package-management tools such as:

```
apt source <package>
```

These third-party services are provided for convenience.

Where FlatCoder Ltd has an independent obligation under an applicable licence to provide corresponding source code, the availability of source from Debian or another upstream project does not remove that obligation.

# MODIFIED THIRD-PARTY COMPONENTS

If FlatCoder Ltd distributes a modified version of a third-party component and the applicable licence requires source code for those modifications to be provided, the corresponding source supplied under this offer will include those modifications to the extent required by that licence.

FlatCoder Ltd will not substitute unmodified upstream source where doing so would omit modifications that form part of the corresponding source required for the binary actually distributed.

# INSTALLATION INFORMATION

Some open-source licences may require additional information enabling installation or execution of modified versions in particular circumstances.

Where such an obligation applies to an ApocOS product or Unit, FlatCoder Ltd will provide the installation information required by the applicable licence.

Nothing in ApocOS device binding, TPM integration, storage protection, secure boot configuration, licence enforcement or other technical protection measures is intended to remove rights that recipients have in relation to third-party components under their applicable licences.

# APOCOS PROPRIETARY SOFTWARE

This source-code offer DOES NOT apply to FlatCoder Ltd's proprietary ApocOS software merely because that software is distributed alongside open-source software.

FlatCoder Ltd's original ApocOS proprietary components are licensed under the:

```
APOCOS PROPRIETARY SOFTWARE LICENCE
```

and the applicable:

```
END-USER LICENCE AGREEMENT (EULA)
```

Those proprietary components are not licensed under the GPL, LGPL, Apache License 2.0 or another open-source licence unless a particular file or component expressly states otherwise.

Source code for ApocOS Proprietary Software is therefore not included in this offer except where FlatCoder Ltd is independently required by an applicable third-party licence or applicable law to provide particular source code.

Nothing in this paragraph limits any rights granted under an applicable third-party open-source licence.

# THIRD-PARTY LICENCE RIGHTS

Each third-party component remains subject to its own licence.

This document does not replace, modify or restrict those licences.

Where there is any conflict between this notice and rights or obligations imposed by the applicable licence for a third-party component, the terms of that third-party licence govern that component.

# ADDITIONAL INFORMATION

For further information concerning third-party software included with ApocOS, see:

```
THIRD-PARTY-NOTICES.md
```

For the licence applicable to FlatCoder Ltd's proprietary ApocOS software, see:

```
LICENSE
```

For end-user contractual terms, see:

```
EULA.md
```

FlatCoder Ltd
United Kingdom

Open-source compliance enquiries:
[gary@flatcoder.co.uk](mailto:gary@flatcoder.co.uk)

Copyright © 2026 FlatCoder Ltd.
This notice does not claim copyright ownership of the third-party software to which it relates.

Third-Party Notices

APOCOS THIRD-PARTY SOFTWARE, DATA AND CONTENT NOTICES

1. APOCOS PROPRIETARY SOFTWARE

2. DEBIAN GNU/LINUX

3. LINUX KERNEL

4. GNU AND OTHER SYSTEM SOFTWARE

5. PYTHON AND PYTHON PACKAGES

6. RUST AND RUST DEPENDENCIES

7. OLLAMA

8. LANGUAGE AND EMBEDDING MODELS

9. OPENSTREETMAP

10. ELEVATION AND TERRAIN DATA

11. SOILGRIDS

12. CHELSA

13. WIKIPEDIA, WIKIMEDIA AND ZIM CONTENT

14. DEVDOCS AND OFFLINE DOCUMENTATION

15. DESKTOP SOFTWARE

16. FIRMWARE

16A. NVIDIA GPU DRIVER

17. SECURITY EDITION

18. SECURITY DATA PACKS

19. ROCKYOU AND OTHER WORDLISTS

20. BOOTLOADERS AND UEFI SOFTWARE

21. THIRD-PARTY TRADEMARKS

22. SOURCE CODE AVAILABILITY

23. TECHNICAL PROTECTION AND THIRD-PARTY RIGHTS

24. RELEASE-SPECIFIC LICENCE MANIFEST

25. NO RESTRICTION OF THIRD-PARTY RIGHTS

26. FURTHER INFORMATION

Written offer for GPL / LGPL source