Skip to content

docs(self-hosting): Community and Enterprise editions page (TH-8084) - #895

Open
nik13 wants to merge 1 commit into
mainfrom
docs/TH-8084-community-editions
Open

nik13 wants to merge 1 commit into
mainfrom
docs/TH-8084-community-editions

Conversation

@nik13

@nik13 nik13 commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

What

Adds the self-hosting Editions page and the matching edits for the uncapped Community edition and the self-hosted Enterprise upgrade (Linear TH-8084).

  • New self-hosting/editions.mdx: what Community includes (1 organization, 1 workspace, up to 3 members, no commercial usage caps on included products), what Enterprise adds (Falcon AI, Turing Models, Protect, Error Feed, more members/organizations/workspaces), how to request a licence (sales@futureagi.com), activate it on Docker Compose and Helm (EE_LICENSE_KEY, optional EE_LICENSE_PUBLIC_KEY, restart every backend and worker service), what expiry/removal does (nothing is deleted; only new creation beyond Community is refused), and troubleshooting.
  • Environment/config reference, Helm, user-management, monitoring, telemetry and support pages updated to link to it and to describe COMMERCIAL_QUOTAS_ENABLED=false for self-hosted collector/gateway.

Merge order

This documents behaviour shipped by the product PR on future-agi/future-agi for TH-8084 (branch feat/TH-8084-community-edition, linked on the Linear issue). Merge after the product PR. Production licence-key bundling (TH-8415) blocks the release, not this docs merge.

Verification

  • Docs test suite: 17 passed.
  • Full docs build at f28750b95f919a7dfff9eafe85ec21617dc34a51: exit 0, 717 pages indexed (ASTRO_TELEMETRY_DISABLED=1).
  • New public copy uses only sales@futureagi.com as the contact; no prices, trials or grace periods were added; existing legal/licence wording unchanged.
  • Unsupported instance binding / revocation is not described as a feature.

Not merged; no deploy.

Add the self-hosted editions page: the approved Community / Enterprise
matrix (1 organization, 1 workspace, up to 3 members; Falcon AI, Turing
Models, Protect and Error Feed plus higher counts with a license), what
"no commercial usage caps" covers and what still costs money, license
request and activation on Docker Compose (including the production
overlay) and Helm, expiry, downgrade and troubleshooting.

Activation steps follow the shipped manifests: the key reaches every
backend and worker service from .env, the overlay reads EE_LICENSE_KEY
from deploy/.env.production and the public key from the root .env, the
Helm Secret is created from an env file, and renewal restarts only this
release's backend and worker Deployments. Details that depend on the
in-flight implementation (UI labels, the 402 gate body, the create_user
message, COMMERCIAL_QUOTAS_ENABLED) are flagged in MDX comments.

List the page under Self-Hosting, link it from Helm and Support, and
replace the Users & sign-in guidance that a second sign-up or create_user
adds people: on Community, invite them instead.

configuration/reference.mdx is generated from future-agi
deploy/env-reference.toml and is not edited here.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant