Ottili ONE Architecture Glossary

Overview

Ottili ONE is a unified SaaS platform for business automation: one login, one company, one dashboard, shared data, shared auth and a shared API. This glossary explains the architecture terms that recur throughout the product documentation — from the control plane down to the individual product surfaces.

All names, routes and availability stages used here are recorded in the Ottili ONE Product Truth Registry (including product_names.yaml, domain_routes.yaml and product_status.yaml). The terms therefore reflect the current architecture and contain no deprecated names.

Platform and control plane

Ottili ONE

The unified platform and control plane for one login, one company and one dashboard. Ottili ONE connects auth, data, API, modules and engines into a single connected workspace. For orientation, see [What is Ottili ONE?](/docs/what-is-ottili-one).

Platform Core (control plane)

The internal platform foundation that every product is built on. Today a concept / internal — it is not yet available as a standalone public product, but it forms the shared basis for auth, the data model and the API. The distinction between the platform layer and the product layer is described in [Platform layer and product layer](/docs/platform-layer-and-product-layer).

company_id and tenant isolation

company_id is the tenant boundary of Ottili ONE. Every business object — customers, orders, files, automations, audit events — belongs to exactly one company and is isolated from other companies. There is no per-module data-silo duplication. The precise model is described in [Shared permissions and entitlements](/docs/shared-permissions-and-entitlements).

Unified API

The central backend contract of Ottili ONE (default port 8100). It is the preferred place to expose platform- and module-spanning endpoints instead of building isolated bypass APIs. The public API boundary runs on api.ottili.one. For authentication, see [Public API authentication](/docs/public-api-authentication).

Ottili Auth

The identity service of Ottili ONE. One account, one company, the same permissions everywhere. Ottili Auth is the verified source of sessions, roles and access; it must not be bypassed for real platform functionality.

Core surfaces

Ottili HQ

The AI-powered ERP/CRM core of Ottili ONE: customers, leads, deals, quotes, orders, invoices, payments, tasks and files in a single data model. It is designed as an AI-powered ERP/CRM for small companies. The overview is in [Ottili HQ overview](/docs/business-hub-overview).

Ottili AI

The AI control surface and assistant layer: models, missions and the Dynamic Workforce Engine (DWE). Everything that acts outward flows through an approval queue. Details in [Ottili AI](/docs/ottili-ai) and [Dynamic Workforce Engine](/docs/dynamic-workforce-engine).

Ottili Files

The shared file and storage foundation (Core Feature) for users, companies, AI, Ottili HQ, LD3 and Flows. It is meant to be a serious storage foundation, not a small upload widget. See [Ottili Files](/docs/ottili-files) and [Files across products](/docs/files-across-products).

Ottili Console

The customer-facing control surface for account, billing, usage, team, API keys and product management on dashboard.ottili.one. The Console is a control surface, not a standalone product.

Modules and engines

Modules

Additional capabilities are activated as modules and belong, company-scoped, to exactly one company context. Each module has its own permission settings. Which module can be enabled in which workspace is described in [Workspace and modules](/docs/workspace-and-modules).

Module Store

The catalog of activatable product capabilities. The Phase-1 selection includes, among others, Ottili Coder, Ottili LD3, Ottili Shop, WordPress Hosting, Shopping and Marketplace Connect.

Engines

Reusable platform intelligence that serves modules through APIs, policies and entitlements — for example the Growth Engine, Opportunity Engine, Analytics Engine, Automation / Flow runtime and the AI / DWE layer. They deliver intelligence across module boundaries rather than being isolated tools.

Ottili Coder

The chat-first software-automation surface for developer workflows (Beta). See [Ottili Coder](/docs/ottili-coder).

Ottili LD3

The content module: sources, topics, generation and publishing jobs (Beta). See [LD3 Content](/docs/ld3-content).

Ottili Shop

The Saleor-based shop-hosting product (Beta). See [Ottili Shop](/docs/ottili-shop).

Ottili Cloud

A managed cloud foundation for hosting, deployments and infrastructure, reachable through an Early Access program (Early Access). See [Ottili Cloud](/docs/ottili-cloud).

Cross-cutting and governance

Availability stages

Every product and feature is labelled with an availability stage: Live, Available (GA), Beta, Private Beta, Early Access, In Development, Planned, Concept / Internal. The exact meaning of the stages is explained in [Understanding feature status labels](/docs/understand-feature-status-labels) and [Product lifecycle and feature status](/docs/product-lifecycle-and-feature-status).

Approval queue (Approvals)

Ottili ONE is approval-first: AI and automation actions that act outward require approval before they run. Every step is auditable. See [Approvals across products](/docs/approvals-across-products).

Audit (core.audit)

A unified, company-scoped audit model (core.audit) that applies across products, modules and engines. Writes are designed to be append-only. Details in [Audit and accountability](/docs/audit-and-accountability).

Feature flags

Feature flags control whether beta features are enabled and allow gradual rollouts. They are part of the platform settings.

Public routes (*.ottili.one)

The public surfaces of Ottili ONE use canonical *.ottili.one routes:

• ottili.one — website and entry point
• dashboard.ottili.one — the Console / workspace
• docs.ottili.one — this documentation
• status.ottili.one — the public status page
• api.ottili.one — the public API boundary (Unified API)
• login.ottili.one and auth.ottili.one — auth surfaces
• ai.ottili.one, coder.ottili.one, ld3.ottili.one, cloud.ottili.one — product surfaces

The routes are recorded in the domain_routes.yaml registry; public surfaces do not invent their own hosts.

Related articles

• [What is Ottili ONE?](/docs/what-is-ottili-one)
• [Platform layer and product layer](/docs/platform-layer-and-product-layer)
• [Workspace and modules](/docs/workspace-and-modules)
• [Shared permissions and entitlements](/docs/shared-permissions-and-entitlements)
• [Approvals across products](/docs/approvals-across-products)
• [Roles and permissions](/docs/roles-and-permissions)
• [Ottili AI](/docs/ottili-ai)
• [Ottili Files](/docs/ottili-files)
• [Ottili Flows](/docs/ottili-flows)
• [Ottili Coder](/docs/ottili-coder)
• [Ottili Shop](/docs/ottili-shop)
• [LD3 Content](/docs/ld3-content)
• [Ottili HQ overview](/docs/business-hub-overview)
• [Integrations across products](/docs/integrations-across-products)
• [Product lifecycle and feature status](/docs/product-lifecycle-and-feature-status)