Skip to main content
The platform

One software ecosystem, built on a shared platform layer.

Ottili ONE is not a single tool you add to your stack. It is the Ottili software ecosystem — a shared platform layer that every Ottili product is built on, so your company, identity, data and permissions stay connected across them all.

Ottili ONE is an ecosystem

Two layers. One Ottili.

Ottili is the top-level brand. Ottili ONE is its software division and ecosystem. The ecosystem is made of two layers: a platform layer of shared services underneath, and a product layer of the products you actually use.

Platform architecture

One brand, one ecosystem, many products.

Ottili is the top-level brand. Ottili ONE is its software ecosystem — a shared platform foundation (Core and Console) with five products built on top. Ottili Electronics is a separate hardware area and does not own the software platform.

Text equivalent of the Ottili platform architecture:

Ottili (Top-level brand)
  Ottili ONE (Software ecosystem)
    Ottili Core (Platform foundation)
    Ottili Console (Platform foundation)
    Ottili HQ (Product)
    Ottili AI Platform (Product)
    Ottili Coder (Product)
    Ottili LD3 (Product)
    Ottili Cloud (Product)
  Ottili Electronics (Hardware area)
  • OttiliTop-level brand

    The Ottili brand family.

    • Ottili ONESoftware ecosystem

      The Ottili software division and ecosystem.

    • Ottili ElectronicsHardware area

      A separate Ottili hardware area. It is not the owner or definer of the Ottili ONE software platform.

Text equivalent of the Ottili platform architecture:
Platform layer

Shared services every product builds on.

Underneath the products sits the Ottili ONE platform layer. It is a set of shared services that every product reuses — so the products feel like one connected system instead of five disconnected apps.

Unified identity

One login, one identity and one API-key layer across every product, module and integration through Ottili Auth.

Company & shared data context

Every product works in one company context. Business data stays connected so AI and workflows always have the right context.

Permissions & roles

A single role and permission model governs access across products and modules — set it once, applied everywhere.

One public API surface

One public API contract is shared by the products, integrations and your own apps — no separate stacks to wire together.

Shared AI layer

The same Ottili AI models, credits and controls power every product through one Ottili AI Platform.

Shared files

A shared file foundation is used by Ottili AI, HQ, LD3, Coder and Cloud — one place for assets and documents.

The shared backend foundation — identity, company context, permissions, billing, credits, the public API surface, the capability registry, tenant-isolated data and shared infrastructure — is Ottili Core. It sits beneath every product and is not sold as a standalone product. The customer-facing control surface that runs on top of it — accounts, companies, teams, products, billing, credits, usage, API keys, security and settings — is Ottili Console.

Product layer

The five Ottili ONE products.

Every product below is built on the same platform layer, so they share one identity, one company context and one set of permissions.

Ottili ONE

One family of products, working as one

Ottili HQ, Ottili AI, Ottili Coder, Ottili LD3 and Ottili Cloud are distinct products on one shared platform — each with a clear outcome and a real entry point.

Ottili AI

Available

Get an AI assistant that works inside your data: missions, model routing and approvals.

Ottili AI — the AI control surface and assistant layer of Ottili ONE: AI models, model routing, missions and the Dynamic Workforce Engine (DWE).

Works with

  • Ottili HQ
  • Ottili Coder
  • Ottili LD3
  • Ottili Cloud

One AI layer shared across HQ, Coder, LD3 and Cloud so every product stays connected.

Why one identity

Separate products, one identity and company context.

Because the products share the same platform layer, they also share one login, one company, one data context, one permission model and one API. You manage a business, not five silos. Ottili ONE is the software division of the Ottili family; the separate hardware area does not own or define the software platform.

One sign-on

A single Ottili Auth identity reaches every product — no per-product accounts.

One company context

Customers, orders, content and tasks live in one company space shared by every product.

Unified permissions

Roles and access are defined once and respected across the whole ecosystem.

One API & data context

Integrations and your own apps speak one contract against one shared data context.

Ottili is the top-level brand. Ottili ONE is its software division. Ottili Electronics is a separate hardware area and is not the owner or definer of the Ottili ONE software platform.

Availability

Available through Early Access.

Ottili ONE is available through the Ottili Early Access program. Core systems are operational while selected customer-facing products are prepared for public beta. No dates are promised here, and nothing is charged without explicit confirmation.

Build on the Ottili ONE platform.

Start with one workspace and let Ottili HQ, Coder, LD3, AI Platform and Cloud share the same foundation.

Architecture & transparency

How Ottili ONE is built — and what that means for you.

Ottili ONE is a software ecosystem on a shared platform layer. Here is exactly how the foundation, your data, approvals, the API and external providers fit together — so technical buyers can evaluate it without guesswork.

Shared platform foundation

Every product is built on Ottili Core (identity, company data context, permissions, credits, tenant context) and Ottili Console (accounts, teams, billing, API keys). One foundation means the products behave as one connected system.

One product family

Ottili HQ, Ottili Coder, Ottili LD3, Ottili AI Platform and Ottili Cloud are distinct products on the same foundation. They share one login, one company context and one permission model rather than five silos.

Data boundaries

Every business record is scoped to your company workspace. Cross-company access requires explicit, audited operations — records are never commingled between companies. See how we isolate and protect data.

Security overview

Approvals & human control

AI and automation actions are approval-first: Coder plans, builds, reviews and ships behind approvals; LD3 publishes draft/approval-first; admin actions are logged. Every state-changing action writes to an append-only, tamper-evident audit log.

Public API, clearly separated

One public, versioned API contract is documented and stable at our public API reference. The internal service-to-service layer is not publicly documented and is never exposed to the internet. Build against the public contract with confidence.

Public API reference

External providers

Where we rely on vetted third parties (for example email delivery or infrastructure), they are listed as subprocessors with their role. We do not share your company data with providers beyond what each integration requires.

Subprocessors