Licensing
Trigora Cloud, the open-source Trigora packages, and TCC Engine are governed by separate terms:
| Surface | License |
|---|---|
| Trigora Cloud | The Terms of Service at trigora.dev. Enterprise order forms can add SLAs, a DPA, or support. |
Trigora source: the CLI, @trigora/contracts, and the TypeScript, Python, and Rust SDKs and clients | MIT, in trigora, trigora-typescript, trigora-python, and trigora-rust |
| TCC Engine, including reference hosts | Business Source License 1.1 |
Distributed Trigora binaries that link TCC Engine components do not relicense those components under MIT. That split is recorded in LICENSE_NOTICES and the bundled TCC Engine license.
The Cloud Terms do not grant a right to embed TCC Engine in production. Pricing for Cloud and Pulse is on the pricing page. One plan covers both. Pulse is the durability service with customer-operated compute: you run the published host, ghcr.io/trigora-dev/pulse:1.0.0, and Trigora stores the checkpoint. That is not a license to vendor or redistribute TCC Engine.
Embedding TCC Engine in your own host is a separate arrangement. It is governed by the engine license below, not by running the Pulse image and not by the Cloud Terms.
TCC Engine is BUSL-1.1. Non-production use is permitted. Production use may be permitted under the Additional Use Grant based on Annual Gross Revenue and whether the use is a Competitive Execution Offering. See the TCC Engine LICENSE for the controlling terms.
Production use under $2M consolidated annual gross revenue is permitted by that grant, unless the use is a Competitive Execution Offering. Production at or above $2M, and any Competitive Execution Offering, need a commercial license. On the Change Date, the Change License is Apache-2.0. The Change Date is specified in the engine LICENSE.
Review the license file in the engine repository before vendoring or distributing TCC Engine. This page summarizes the licensing structure; the applicable license text controls.