1. Scope
This page is provided for transparency and open-source license compliance. It does not make Paladin itself open source or freely redistributable unless a specific Paladin package, SDK, or file says so under its own license. Dograh AI, Pipecat, and other third-party names are used only for attribution and license notice, not to imply endorsement, sponsorship, or affiliation.
Third-party components remain governed by their own license terms, copyright notices, disclaimers, and attribution requirements. If there is any conflict between this summary and a package's original license file, the original package license controls.
The Terms & Conditions keep a short open-source clause. This page carries the detailed open-source notice so the Terms and Privacy Policy remain focused on contract, usage, and data-protection obligations.
2. Key Repository Notices
| Component | License / notice | Reason it matters |
|---|---|---|
| Dograh AI original application codebase | BSD 2-Clause. Public Dograh license notice identifies copyright: Zansat Technologies Private Limited. | Paladin is based on a modified and rebranded Dograh AI codebase. Dograh's BSD 2-Clause copyright notice, license conditions, and disclaimer must be retained in source, binary, SDK, release, and notice materials where applicable. |
| Paladin application modifications and SDK license files | BSD 2-Clause notices are present in the current application and SDK license files. Additional Paladin-specific branding, hosted SaaS operations, documentation, pricing, billing, and proprietary service layers are reserved unless separately licensed. | Keep original Dograh and current Paladin license notices intact. Do not treat this notice as permission to copy Paladin-specific hosted service, brand, customer data, credentials, infrastructure, or proprietary materials. |
| Pipecat voice framework | BSD 2-Clause. Copyright notice identified in the repository: Daily. | Pipecat is a core voice/multimodal framework component. Its license notice must remain intact where the component is used or distributed. |
| Paladin Python SDK | BSD 2-Clause. | The Python SDK package metadata and license file should continue to ship with the package. |
| Paladin TypeScript SDK | BSD 2-Clause. | The TypeScript SDK package metadata includes the license and packages the LICENSE file. |
3. Component Groups Identified
The current scan found common permissive licenses across most backend, frontend, SDK, and website dependencies, plus a small number of weak-copyleft packages that should stay visible in release reviews.
Backend and API dependencies
Backend packages identified from the pinned requirements include FastAPI, SQLAlchemy, Alembic, Uvicorn, Redis client libraries, Twilio, MinIO, Sentry SDK, PostHog, Langfuse, FastMCP, PyNaCl, ReportLab, tiktoken, and related Python packages. Their scanned metadata is primarily MIT, Apache-2.0, BSD, or Unlicense. Package-level license files and metadata remain authoritative.
Frontend application dependencies
Frontend packages identified from lockfiles include Next.js, React, Radix UI packages, Lucide React, React Hook Form, Recharts, Zustand, Sentry, PostHog JS, Stack Auth packages, and related build tooling. Most scanned frontend packages are MIT, Apache-2.0, BSD, ISC, or similarly permissive.
Packages requiring special release visibility
- sharp / libvips packages: lockfiles identify LGPL-3.0-or-later and Apache-2.0 license expressions around native image tooling.
- lightningcss packages: lockfiles identify MPL-2.0 license metadata.
- axe-core: lockfiles identify MPL-2.0 license metadata.
- PostHog JS: package license file identifies Apache-2.0 terms and related notices.
- Stack Auth packages: package tarballs include MIT-style license notices.
Website assets and fonts
The public website is primarily static HTML, CSS, JavaScript, and Paladin/Northmann assets. It loads Inter and Outfit through Google Fonts. Google Fonts provides open-source fonts and commonly uses the SIL Open Font License; individual font license terms control.
4. License Types and Controls
For convenience, the important license families identified in the scan are listed below. These summaries do not replace the original license texts.
| License family | Practical handling |
|---|---|
| BSD, MIT, ISC, 0BSD, Unlicense | Retain copyright notices, license terms, and disclaimers in source, package, or distributed notice materials where required. |
| Apache-2.0 | Preserve license text and notices, respect patent and NOTICE-file requirements, and preserve modification notices where applicable. |
| MPL-2.0 | Keep MPL-covered files under MPL terms and preserve required notices if those files are modified or distributed. |
| LGPL-3.0-or-later | Preserve notices and license terms. If LGPL components are modified or distributed in a way that triggers source obligations, provide the required corresponding source or relinking rights as applicable. |
| SIL Open Font License | Follow font-specific naming, redistribution, and bundling conditions if fonts are bundled or redistributed. |
5. Release Practice
Northmann should keep the following controls for Paladin releases and deployments:
- Do not remove root, SDK, Pipecat, or package-level LICENSE and NOTICE files.
- Regenerate a dependency license report from lockfiles before material production releases.
- Review any newly added GPL, AGPL, SSPL, BUSL, source-available, or commercial-restriction license before use.
- Keep this public page updated when important framework, SDK, or license-family changes occur.
- Keep package-level notices in released SDKs, downloadable artifacts, containers, and bundled frontend assets where applicable.
6. Contact
Questions about this notice, license attribution, or third-party software in Paladin can be sent through Northmann Groupe contact. Existing Paladin customers should use the in-app support or report issue flow where available.