Current product boundary
Boundport currently includes public product materials, documentation, and an open-source codebase. This page is intended to clarify how those materials should be understood from a licensing and product-terms perspective.
Product Terms
Terms and licensing boundaries for Boundport.
This page explains the current product terms boundary for Boundport: what is available today as open-source software, what license governs that code, and where separate commercial or customer-specific terms would apply.
Last updated: July 28, 2026
Informational versus binding terms
Public-facing materials are informational unless a separate binding agreement says otherwise. Security commitments, support obligations, service levels, data handling commitments, and commercial scope should live in product documentation, license files, or signed agreements as applicable.
Acceptable use
You may not misuse Boundport materials, interfere with distributed software or related services, attempt unauthorized access, introduce harmful code, or use Boundport in violation of applicable law or third-party rights.
Third-party services and dependencies
Boundport may integrate with or reference third-party services, infrastructure, repositories, or tools. Those services operate under their own terms, licenses, and policies, and teams should evaluate them independently as part of their own deployment and procurement process.
Open-source license
The Boundport open-source codebase is made available under the Apache License 2.0. Use, modification, and distribution of the open-source software should follow the terms of that license and the license files published with the repository.
Brand and proprietary materials
Unless otherwise stated, the Boundport name, brand elements, product positioning, design assets, and non-code materials remain separate from the Apache 2.0 license that applies to the open-source codebase.
Open-source versus commercial offering
The product may be described in both open-source and commercial terms. The open-source software is governed by Apache 2.0. Any future hosted, enterprise, support, or customer-specific offering should be governed by separate commercial terms, service descriptions, and security commitments.
No implied commercial commitment
Public docs, roadmap direction, or launch messaging should not be read as creating an obligation to deliver a hosted service, a specific enterprise feature, or a specific support model unless that commitment appears in a separate written agreement.
Company and contact information
These product terms are published by CVBE ApS, CVR 42764760. Questions about licensing, product terms, or commercial discussions can be sent to c@cvbe.dk or raised by phone at +45 60782978.