Agent Ops Suite
HomeTermsPrivacyLicence

Third-Party Licences

Last updated: 3 May 2026.

Agent Ops Suite is commercial software. It uses permissively licensed open-source components and third-party assets. Those components remain governed by their own licences and do not change the proprietary licence for Agent Ops Suite itself.

Current direct dependencies

ComponentLicenceRole
ElectronMITDesktop application runtime.
ChromiumBSD-style and third-party noticesBrowser engine included with Electron.
Node.jsMITJavaScript runtime used by Electron and local tooling.
FastifyMITLocal API service.
@fastify/swaggerMITOpenAPI schema support.
better-sqlite3MITSQLite database binding.
SQLitePublic domainEmbedded database engine.
TypeScriptApache-2.0Development toolchain.
tsxMITDevelopment scripts and tests.
Electron BuilderMITDesktop installer packaging.
BarlowOpen Font LicenseWebsite typography.

Desktop application notices

The desktop application includes Electron, Chromium, Node.js, V8, bundled assets and production transitive dependencies. Production builds should include generated dependency notices from the locked build. Where a notice file is shipped with the installer or application resources, that notice file forms part of these Third-Party Licences.

Website and brand assets

Agent Ops Suite logos, icons, installer graphics, product copy, screenshots and brand assets are proprietary unless expressly stated otherwise. The Barlow font is used under the Open Font License. Website hosting and deployment infrastructure may involve Cloudflare Pages or similar providers, which are governed by their own terms.

Connected services are separate

Agents, AI models, email platforms, CRMs, issue trackers, support desks, repository hosts, search providers, cloud storage, payment processors and other connected services are not licensed as part of Agent Ops Suite. Their own software, APIs, models, outputs, uptime, pricing and notices remain separate.

Licence policy for embedded code

Agent Ops Suite allows MIT, Apache-2.0, BSD, ISC, 0BSD, Unlicense, BlueOak-1.0.0 and Python-2.0 by default for embedded code, subject to normal attribution and notice requirements. CC0-1.0 and WTFPL require contextual review before use because they can raise attribution, warranty or provenance questions in commercial packaging.

GPL, AGPL, SSPL, BUSL, Commons Clause, unclear/no-licence and open-core code are not allowed for embedding without explicit approval. Those projects may still be useful as connector targets, references or optional systems of record if their licences and deployment boundaries are respected.

Attribution process

Before each public release, dependency notices should be regenerated from the locked production dependency set, reviewed for licence changes and published with the installer or website attribution page. Material licence changes should be reviewed before release.

Corrections

If you believe a licence or attribution is missing or incorrect, contact hello@agentopsuite.com with the component name, version, licence and suggested correction.

Copyright 2026 Agent Ops Suite by [ so.design ].