Last Updated On: 19 December, 2025

​

House Of FOSS is an infrastructure platform for hosting open-source software. This policy explains how we host and operate software licensed under copyleft and network copyleft licenses such as GPL and AGPL. It defines our role as a neutral hosting provider, outlines our compliance approach, and clarifies how source code availability, containerization, and isolation are handled. Our goal is to respect open-source licenses, protect authors’ rights, and provide transparent, compliant hosting without modifying application code.

​

1. Scope of This Policy

This policy applies to all software hosted on House of FOSS that is licensed under copyleft or network copyleft licenses, including but not limited to:

• GNU General Public License (GPL v2/v3)

• GNU Affero General Public License (AGPL v3)

• LGPL (where applicable)

Permissive licenses (MIT, Apache, BSD) are not restricted by this policy.

 

2. Our Role

House of FOSS acts solely as:

• An infrastructure provider

• A software host

• A compute resource operator

We do not:

• Claim ownership over hosted software

• Modify application source code

• Embed proprietary logic into hosted applications

• Add application-level observability, tracing, or instrumentation

We charge only for infrastructure usage (hardware minutes) and not for the software itself.

​

3. General Copyleft Principles

For all copyleft-licensed software hosted on House of FOSS:

• The original license terms remain fully in force

• All rights granted to end users by the license are preserved

• No additional restrictions are imposed by House of FOSS

Responsibility for license compliance is shared as follows:

• House of FOSS: compliance related to hosting and operation

• Software authors: licensing of the software

• End users: downstream usage and redistribution

​

4. GPL-Licensed Software (GPL v2 / v3)

4.1 What We Do

• Host and run GPL software as a network-accessible service

• Build and run container images without modifying application source code

• Provide server-level metrics (CPU, memory, disk, network)

4.2 What We Do Not Do

• Distribute binaries or source code for download

• Create proprietary derivative works

• Link GPL code with proprietary House of FOSS components

4.3 Compliance Position

Under the GPL:

• Running software as a service does not trigger source code disclosure

• No GPL obligations extend to the House of FOSS platform itself

House of FOSS remains compliant provided no modified binaries are distributed.

​

5. AGPL-Licensed Software (AGPL v3)

5.1 Network Use Acknowledgement

AGPL software hosted on House of FOSS is accessed over a network.
This constitutes “remote network interaction” under AGPL v3.

5.2 Source Code Availability

For AGPL-licensed software, House of FOSS ensures that users are provided with:

• A clear and accessible link to the Corresponding Source Code

• Either:

  • The upstream project repository (if unmodified), or

  • A repository containing any modifications made by House of FOSS (if applicable)

If no modifications are made, upstream source disclosure satisfies AGPL requirements.

5.3 Modifications

House of FOSS does not modify AGPL application source code.

If modifications are ever made, House of FOSS will:

• Publish those modifications under AGPL v3

• Provide access to the modified Corresponding Source Code

• Clearly disclose the existence of such modifications

5.4 Containerization and Dockerfiles

House of FOSS may create Dockerfiles to enable hosting.

Dockerfiles are limited to:

• Fetching upstream source or images

• Installing dependencies

• Configuring runtime parameters

• Exposing ports and entrypoints

Dockerfiles does not:

• Patch or alter application source code

• Introduce proprietary linked components

• Change licensing terms

Dockerfiles are treated as infrastructure configuration, not application modifications.

​

6. Configuration and Runtime Parameters

The following are not considered modifications under this policy:

• Environment variables

• Runtime flags

• Resource limits

• Standard configuration files not altering application logic

These do not trigger additional copyleft obligations.

​

7. Observability and Metrics

House of FOSS provides:

• Host-level and container-level metrics only

House of FOSS does not:

• Instrument application code

• Inject tracing libraries

• Modify request/response handling

Server-level observability does not constitute a derivative work.

​

8. Isolation and Platform Boundaries

Copyleft software is hosted in isolated environments.

House of FOSS platform components:

• Do not link against hosted application code

• Do not embed application logic

• Remain independent and non-derivative

This separation is intentional and enforced.

​

9. Vendor and User Responsibility

• Software vendors remain responsible for correct licensing of their software

• Users are responsible for compliance in downstream use, redistribution, or modification

• House of FOSS does not grant additional rights beyond those provided by the original license

​

10. Policy Enforcement

House of FOSS reserves the right to:

• Restrict hosting of software that violates license terms

• Require proof of source availability for AGPL software

• Suspend workloads that create license compliance risk for the platform

​

11. Policy Intent

This policy exists to:

• Respect copyleft licenses

• Protect open-source authors

• Enable sustainable infrastructure hosting

• Avoid license contamination of unrelated systems

House of FOSS supports open-source without weakening its licenses or abusing loopholes.