Licensing and operator FAQ

Availability: The package license matrix is effective in the private release candidate, and the owner confirmed matrix and trademark approval complete on 21 September 2026. No public source release exists yet; explicit owner activation still gates publication. See Release status.

Tedix uses a mixed open-source license boundary: deployable product and server code under AGPL-3.0-only, with intentionally embeddable ecosystem packages under Apache-2.0 or MIT. The exact effective workspace mapping is machine-readable in scripts/oss/public-surface.json and checked against every package manifest by scripts/oss/license-readiness.json.

This page explains the current repository model; it is not legal advice. The root license and per-package SPDX metadata are effective while the repository remains in private beta. Approval of these terms does not activate public launch or make the contributor and commercial drafts effective. The license text and package metadata for the version you use control.

Practical answers

Can I self-host Tedix?

There is no public, supported self-hosted release today. Authorized private-beta recipients may evaluate the release candidate in their own Cloudflare account, subject to the license terms attached to their copy. After public launch, the AGPL-covered product release will permit self-hosting subject to its license. Self-hosting does not include a Tedix Cloud support commitment, provider credentials, production data, or the right to present a modified installation as an official or certified Tedix service.

Do I have to publish my data, prompts, credentials, or configuration?

The license applies to covered software, not to your private data just because the software processes it. It does not turn customer records, credentials, prompts, operational logs, or ordinary configuration into source code. Ask counsel about any material that mixes code and private configuration.

What if I modify the server and users interact with it over a network?

AGPL section 13 adds a network-source obligation for a modified covered program: users interacting with it remotely must be offered the corresponding source of that modified version. The complete license text in LICENSES/AGPL-3.0-only.txt controls the scope and method.

Can I offer an unmodified Tedix release as a service?

AGPL is not a non-compete license. The license does not prohibit an unmodified hosted service. Tedix trademarks, certification marks, and claims of official status remain separate; see TRADEMARKS.md.

Can I keep unrelated software private?

The answer depends on whether it is a separate work or part of a covered combined or modified program. Network calls alone do not produce a universal answer. Keep boundaries explicit and obtain legal advice for a planned proprietary integration.

Which packages are permissive?

The checked-in license-readiness report maps every workspace to one SPDX identifier. Permissive ecosystem packages may not have runtime dependency edges into AGPL product workspaces; CI fails if that boundary regresses.

Is there a commercial license?

Tedix intends to offer a separate commercial grant for organizations that need different terms. No commercial grant exists merely because a draft is present in the repository. Terms, pricing, scope, and support require a signed agreement from an authorized Tedix representative.

What happens after a version is released as open source?

No Tedix product source version has been publicly released yet. Once a version is released, it remains available under the license granted with it. A later business-model or license change is prospective; it does not revoke an existing open-source grant.

Verify the boundary

From an authorized source checkout:

bun run oss:surface
bun run oss:license-readiness:check
bun run oss:dependency-licenses:check
bun run oss:dependency-license-policy:check
bun run oss:provenance:strict

The readiness report deliberately distinguishes engineering completion from recorded matrix ratification and separate owner launch activation.