1. Scope of this page
This notice applies to public Forge Accelerant website content, the Technology Catalog, product and vendor references, technology-learning workflows, generated reports, and other Forge surfaces that identify third-party software, services, projects, standards, or vendors.
This page is a transparency statement, not a license from a third party and not legal advice. Rights to use third-party software, documentation, trademarks, APIs, data, or other materials are controlled by the applicable owner and the terms that accompany those materials.
2. Third-party names and trademarks
Forge may use company names, product names, project names, service names, and other word marks when they are needed to identify technology accurately or describe a technical relationship. These references are intended to be factual and descriptive.
- A technology appearing in Forge does not mean its owner sponsors, endorses, certifies, approves, or is affiliated with Forge Accelerant.
- Forge does not claim ownership of third-party trademarks or the goodwill associated with them.
- Third-party names should not be incorporated into Forge product names, company names, slogans, domains, or branding in a way that could suggest ownership or affiliation.
- Vendor logos, icons, artwork, screenshots, and other brand assets are treated separately from plain-text names and should not be used unless the applicable owner permits that use or Forge has the necessary authorization.
All third-party trademarks, registered trademarks, service marks, and product names remain the property of their respective owners.
3. Technology Catalog references
The Forge Technology Catalog may record vendor, product, version, edition, technology type, aliases, package identifiers, APIs, documentation sources, license metadata, source status, and related technical information. Those entries are catalog metadata; they are not statements of commercial relationship or proof of a customer's license rights.
Catalog listing does not equal certification or a license grant. Unless Forge expressly states otherwise and can support the statement, a listing should not be read as a claim that Forge is an authorized reseller, certified integration, official partner, supported implementation, vendor-approved product, or source of third-party license rights.
Compatibility, discovery support, API connectivity, and other technical relationships may vary by version, edition, deployment model, configuration, permissions, and customer environment. Forge may update catalog metadata as better evidence becomes available.
4. Customer licenses, subscriptions, and entitlements
Forge can help identify technology and organize licensing evidence, but use of Forge does not create, extend, transfer, or replace a customer's rights to use third-party software or services. Customers are responsible for confirming that they hold the licenses, subscriptions, entitlements, permissions, and other rights required for the products and features they use.
- Before using, enabling, accessing, deploying, copying, modifying, redistributing, or integrating third-party technology through a Forge workflow, the customer should confirm that the activity is permitted by the applicable terms.
- Discovery of a product in a customer environment does not establish that the deployment is properly licensed, and absence of a Forge warning does not establish license compliance.
- Commercial products may require separate rights for editions, processors/cores, users, devices, virtualized instances, options, add-ons, cloud use, disaster recovery, test environments, or other functionality.
- Open-source software may not require a commercial purchase, but use, modification, redistribution, hosted delivery, or combination with other software may trigger license conditions that still must be followed.
- Where a customer's contract, enterprise agreement, reseller agreement, cloud marketplace purchase, support agreement, or other negotiated terms differ from public information, the customer's applicable agreement controls.
- Forge may require an authorized customer administrator to confirm that the organization has the rights needed for a licensed-product connector, integration, or workflow before that capability is enabled. Forge may retain the attestation date and supporting evidence reference for audit purposes.
Forge is not a substitute for a customer's software-asset-management, procurement, or legal review. Forge may record evidence and surface possible licensing concerns, but it should not represent a customer as legally compliant solely from automated discovery or catalog metadata.
Illustrative catalog labeling
The following example shows the type of licensing and source information Forge may display. It is a labeling model, not a determination of any customer's legal rights.
| Catalog field | Open-source example | Commercial example |
|---|
| Technology | PostgreSQL community project | Oracle Database — exact edition/version recorded by discovery |
| License model | Open source | Proprietary / commercial |
| License / terms | PostgreSQL License | Customer agreement plus applicable Oracle licensing information and product-specific terms |
| Source status | Official upstream source available | Proprietary source unless the applicable owner provides otherwise |
| Upstream / terms location | Official PostgreSQL project and license pages | Official Oracle licensing documentation and the customer's governing agreement |
| Customer entitlement status | Commercial entitlement not inferred; customer remains responsible for applicable open-source obligations | Customer confirmation required for the discovered edition, options, features, and deployment rights |
| Forge evidence status | Source/license identified; version-specific review may still be required | Review required unless the customer provides entitlement evidence for the discovered use |
Forge may use operational labels such as Customer confirmed, Review required, Open-source obligations identified, or Unknown. Those labels describe the evidence available to Forge; they are not legal opinions or independent license certifications.
For a commercial technology workflow, Customer confirmed should mean that an authorized customer representative has attested that the organization holds the required rights for the identified use. It should not mean that Forge independently audited the customer's contracts or guarantees compliance.
TenantAdmin License / Rights Attestation
Forge can record a tenant-scoped rights attestation from an authenticated customer administrator. The record identifies the vendor or project owner, product, edition or version when known, license model, rights basis, covered use, optional review or expiration date, and a customer-controlled evidence reference. Forge retains the attestation history so a later change, revocation, or replacement does not erase the earlier record.
- Only an authorized TenantAdmin or equivalent Forge administrator can create or revoke an attestation.
- The attestation records the customer administrator's assertion; Forge does not convert that assertion into an independent legal opinion or compliance certification.
- Customers should reference their own contract, procurement, software-asset-management, open-source review, or other evidence record rather than entering license keys, passwords, tokens, or full confidential agreements.
- Expired, revoked, superseded, missing, or uncertain attestations should be treated as requiring review before a rights-gated product workflow is enabled.
- Where Forge later enforces an attestation gate for a connector or product workflow, the gate confirms that an active customer attestation exists; it does not determine whether the underlying agreement is legally sufficient.
5. Open-source and source-available technology
Some technologies recognized by Forge are distributed under open-source licenses. Others use source-available, dual-license, community/commercial, or mixed licensing models. Forge treats those categories separately rather than assuming that visible source code automatically means a product is open source.
| Forge label | What it means |
|---|
| Open source | The identified project, component, edition, or version is distributed under an open-source license. Where known, Forge may show the license name or SPDX identifier and an upstream project or source location. |
| Source available | Source code can be viewed or obtained, but the governing terms may impose restrictions that differ from recognized open-source licenses. Forge does not treat source availability alone as proof that software is open source. |
| Dual / multi-licensed | The same technology may be offered under more than one license depending on edition, use, distribution, or commercial agreement. |
| Mixed model | An open-source core, library, or component may coexist with proprietary extensions, hosted services, commercial editions, support packages, or separately licensed features. |
| Proprietary / commercial | Use is governed by the vendor's commercial, subscription, EULA, service, or other applicable terms. |
Where Forge points users for open-source software
When reliable information is available, Forge may identify the official upstream project site, source repository, release page, license page, and a standardized license identifier such as an SPDX identifier. The exact license text and terms for the specific version or component control.
- Forge does not grant, replace, or modify a third-party open-source license merely by listing the software.
- An open-source label applies only to the specific project, component, edition, or version identified; it does not automatically apply to a vendor's entire portfolio.
- Commercial packaging, cloud hosting, support, trademarks, add-ons, connectors, data, or enterprise features may be governed by separate terms even when underlying software is open source.
- If Forge distributes third-party open-source software, Forge will provide the notices, license texts, attribution, source availability information, or source offers required by the applicable distribution terms.
6. Documentation, APIs, repositories, and public sources
Forge may identify or link to public documentation, project repositories, package registries, standards, APIs, vulnerability feeds, and other technical sources as part of discovery, learning, analysis, or evidence collection. A link or citation does not transfer ownership of the referenced material to Forge and does not create a right to copy or redistribute material beyond what the owner or applicable license permits.
Forge's technology-learning workflows are intended to use authorized or lawfully accessible sources and to preserve source identity, provenance, and licensing context where practical.
7. Forge software and third-party components
Forge Accelerant software, branding, original website content, and proprietary platform components remain Forge property except where a file, component, dependency, or accompanying notice identifies different ownership or licensing terms.
Forge may incorporate or depend on third-party software. Those third-party components remain subject to their own licenses and notices. Nothing on this page is intended to relicense third-party software under Forge terms.
8. Accuracy and licensing responsibility
Technology and licensing models change over time. Forge works to keep catalog information useful and evidence-backed, but license metadata should be verified against the official terms for the exact product, component, edition, and version before making procurement, redistribution, compliance, or legal decisions.
Customers remain responsible for their own software entitlements, subscriptions, license compliance, procurement obligations, export restrictions, and contractual requirements unless a written agreement with Forge expressly assigns a specific responsibility elsewhere.
9. Reference resources
Forge uses original wording on this page. The following owner and standards resources are provided so users can review authoritative policies and license information directly:
These external resources are maintained by their respective organizations and may change independently of Forge.
10. Questions, corrections, and rights concerns
If you own rights in a name, mark, work, project, or other material referenced by Forge and believe the reference is inaccurate or should be reviewed, contact contact@forgeaccelerant.com. Please identify the material, the concern, and the relevant owner or authoritative source so Forge can evaluate the request.
