Product lifecycle and feature status

Overview

Ottili ONE distinguishes two separate but related maturity vocabularies. They are often confused, yet they have different scopes:

• Product lifecycle* — the availability of a *whole product* (Ottili ONE, Ottili HQ, Ottili AI, Ottili Coder, Ottili LD3, Ottili Cloud …). Defined in the product_status.yaml registry and coupled to the ProductStatus enum in libs/product_truth.
• Feature status* — the maturity of an *individual feature* inside a product. Defined in the feature_status.yaml registry and coupled to the FeatureStatus enum in libs/product_truth.

Both registries are part of the Product Truth registry of Ottili ONE. Every state has a fixed maturity_rank, and the canonical enums in libs/product_truth ensure a label means the same thing everywhere — in the documentation, on the website, in the Console, on the status page and at the public API boundary.

This article explains both models, clearly separates the common stages Live, Beta, Private Beta, In Development, Planned* and Concept*, and shows where you see each status.

Two vocabularies, one principle

A product can carry the status *Available* (or *Live*) while individual features inside it are still *Beta* or *In Development*. Lifecycle and feature status are independent of each other:

• Product lifecycle* answers: *Is the product available at all?* It knows stages from Concept to Retired.
• Feature status* answers: *How far along is this one feature?* It knows stages from Concept to Disabled.

The precise product overview with the current availability of each product is provided by the article [What is Ottili ONE?](/docs/what-is-ottili-one) and the product picker [Choose an Ottili product](/docs/choose-an-ottili-product).

Feature status: the maturity of individual features

The feature status is defined in the canonical feature_status.yaml registry and coupled to the FeatureStatus enum in libs/product_truth. It describes the maturity of *one feature*, not the availability of a whole product. The nine states with ascending maturity_rank (0–8):

The six most commonly cited stages in detail:

Concept

An early idea under consideration. Not yet scheduled or built. Concept is the earliest state and is not shown on public surfaces — it only becomes visible once it is promoted to Planned.

Planned

Accepted and scheduled for development but not yet started. The idea is confirmed and sits on the roadmap; implementation has not started yet. Planned is publicly visible.

In Development

Actively being built, but not yet available to users. The feature is in progress, but you cannot use it yet. Once it becomes reachable it usually moves to Beta or Private Beta.

Private Beta

Available to an invited group for early feedback. Access is limited — you get access after you are invited to an early-access program. The feature breadth is similar to Beta, but availability is deliberately narrow.

Example from practice: Ottili Cloud* — Compute is reachable through an early-access program, while further categories such as Storage and Networking are still planned.

Beta

Publicly available in a pre-release state. Anyone with an Ottili account can use the feature, but it may still change — paths, fields or limits evolve as it matures.

Example: Ottili Coder* is publicly available in a Beta; the chat-first coding-agent surface is live and actively evolving. The difference between public and private Beta is explained in [Understand feature status labels](/docs/understand-feature-status-labels).

Live

Generally available and fully supported. The feature is enabled for everyone it is intended for and belongs to the supported scope of Ottili ONE. You can use it in production.

Product lifecycle: the availability of whole products

The product lifecycle is defined in the canonical product_status.yaml registry and coupled to the ProductStatus enum in libs/product_truth. It describes the availability of a *whole product*, not the maturity of individual features. The nine states:

The product-side counterpart to a *Live* feature is Available* (GA): the product is generally available and fully supported. In public communication products are usually called *Live* or *Available*; technically the canonical state is AVAILABLE. Correspondingly, a *Private Beta* on the feature level is closest to a product-side Early Access*.

Where you see status

Status labels are labelled consistently everywhere:

• Documentation* — articles like this one and [Understand feature status labels](/docs/understand-feature-status-labels).
• Public status page* — [status.ottili.one](https://status.ottili.one) reports the operational state of products and components; see also [Cloud status](/docs/cloud-status).
• Ottili Console* — areas such as account, company and team carry a status label; see [Navigate the Ottili Console](/docs/navigate-ottili-console).
• Website* — product pages show availability and maturity; see [What is Ottili ONE?](/docs/what-is-ottili-one).
• Public API boundary* — the Unified API (standard port 8100) reflects the same canonical statuses; details are in the API documentation.

Status, routes and tenant isolation

All public statuses refer to objects that belong to the company (company_id). A feature status applies within the company context; it is not identical across companies globally. The distinction between the platform layer and the product layer is explained in [Platform layer and product layer](/docs/platform-layer-and-product-layer), and which module can be activated in which workspace is covered in [Workspace and modules](/docs/workspace-and-modules).

Related articles

• [Understand feature status labels](/docs/understand-feature-status-labels)
• [What is Ottili ONE?](/docs/what-is-ottili-one)
• [Platform layer and product layer](/docs/platform-layer-and-product-layer)
• [Navigate the Ottili Console](/docs/navigate-ottili-console)
• [Workspace and modules](/docs/workspace-and-modules)
• [Choose an Ottili product](/docs/choose-an-ottili-product)
• [Getting Started with Ottili ONE](/docs/getting-started-with-ottili-one)
• [Understand plans and credits](/docs/understand-plans-and-credits)