Platform concepts

Platform layer and product layer

How the stable platform layer (identity, Unified API, shared company context, Core capabilities and engines) underpins the product layer (Ottili HQ, Ottili AI, Flows, LD3, Coder, Cloud and the Module Store).

Overview

Ottili ONE is built as two cooperating layers: a stable platform layer* (the control plane and shared foundation) and a product layer* (the modules and surfaces you actually work in). Everything connects through one login, one company context and one Console. The platform layer makes that possible; the product layer delivers the day-to-day value.

The platform layer

The platform layer is the operating system beneath every module. It owns the cross-cutting capabilities that no single product should duplicate:

Ottili Auth* — identity and one secure login for every surface.
Unified API* — the single backend contract behind the dashboard, modules and external integrations.
Company context (tenant isolation)* — every business object, activation and action is scoped to one company (company_id); the platform layer enforces this company boundary by default.
Shared data* — customers, permissions, files, automations and audit events live once, not once per module.
Ottili Console* — the single control surface where every product surface renders.
Core capabilities* — a shared set of platform primitives that product surfaces resolve instead of rebuilding: auth, company context, permissions, entitlements, settings, notifications, approvals, audit, search, files and flows.
Engines* — platform intelligence used by modules through APIs and policies (for example Growth Engine, Opportunity Engine, Analytics Engine, the Flow Runtime and the AI/DWE layer).
Module Store* — the registry that activates and rolls out optional modules per company.

The platform layer is the stable foundation: it changes slowly and is shared by everyone.

The product layer

The product layer is where teams work. Every product surface is built on the platform layer and renders inside the one Ottili Console; it reuses the Core capabilities instead of owning its own copy. Verified product surfaces include:

Ottili HQ* — the AI-assisted ERP/CRM core: leads, deals, quotes, orders, invoices, payments and the customer file.
Ottili AI* — the AI control surface and assistant layer across modules.
Ottili Files* — the shared storage foundation for users, companies, AI, Ottili HQ, LD3, Flows and more.
Ottili Flows* — the AI-first workflow engine (triggers, conditions, actions, waits, approvals, persistent execution).
LD3* — content automation: sources, topics, generation, review and publishing jobs.
Ottili Coder* — chat-first software automation for building and shipping features.
Ottili Shop* — platform-native shop hosting.
Marketplace Connect* — unifies external marketplaces and shops.
Ottili Cloud* — infrastructure for hosting and running Ottili ONE workloads.

Modules extend the platform; they never replace the core. A module activation adds capability, never a data silo.

How the layers work together

Both layers share one context: when a module is activated, it is bound to the same company, the same users and the same permissions as the core. A customer created in Ottili HQ is visible to Ottili AI and Flows; a file uploaded in Ottili Files is available to LD3 and Coder; an approval queued in the platform layer gates any outward action from any product surface. This is why enabling a module never creates a second, disconnected system.

Understanding status tiers

Platform-layer capabilities are the stable base, while individual product features move through defined maturity stages. Every capability carries one of these status labels:

Live* — available and supported for all entitled companies.
Beta* — publicly available in a pre-release state; may still change.
Private Beta* — available to an invited group for early feedback.
In Development* — actively being built, not yet available.
Planned* — accepted and scheduled, not yet started.
Concept* — an early idea under consideration.

Current per-feature status changes often; the status-labels article (see related articles) and the public status page show live rollout state.