Overview
Ottili ONE is a platform: one login, one company, one dashboard, shared data and shared capabilities across every product. Integration is not an island feature of a single module — it is the core idea of the platform. Ottili ONE connects products at two levels:
1. Product-to-product*: Ottili HQ, Ottili AI, Ottili Coder, Ottili LD3, Ottili Flows, Ottili Cloud and Ottili Files all share the same data layer, the same login and the same permissions.
2. Product-to-tool*: through connectors you bring the tools you already use (marketplaces, payments, communication, developer tools, AI models) into your workspace.
This article explains how these integrations work, which are available today, and how company boundaries (tenant isolation) are respected everywhere.
Why integration across products?
A company does not work in silos. An order in Ottili HQ, an AI suggestion in Ottili AI, a publish-ready article in LD3 and a Flow that ties them together are all part of the same day's work. Ottili ONE keeps these connections on one shared platform, instead of every product maintaining its own integration:
- One data layer* — every product reads and writes through the same company-scoped Unified API.
- One login* — Ottili Auth connects identity and session across every surface.
- Shared permissions* — who can see and do what is consistent across every product.
- Company boundaries* — no data or action crosses your company's boundary.
Product-to-product: the platform connects
Instead of every product maintaining its own integrations, the modules use the same platform mechanics.
One shared data layer (Unified API)
The Unified API is the central backend of Ottili ONE. Ottili HQ, Ottili AI, Ottili Coder, Ottili LD3, Ottili Flows and Ottili Files all talk over the same API and the same company_id-scoped context. An object created in one product (for example an order) can be read and acted on by another product — no export, copy-paste or double entry.
One login, one company (Ottili Auth)
Ottili Auth provides one identity and one session for every Ottili surface (single sign-on). You sign in once and are in the same company in every product — from the dashboard through Ottili AI to the Coder.
Shared permissions and entitlements
Who can see or trigger an integration follows the same permission model as access to the data. Roles decide consistently across products — see [Shared permissions and entitlements](/docs/shared-permissions-and-entitlements).
Company scope (tenant isolation)
Every integration is scoped to your company. The platform derives the company context from the verified token and enforces separation end to end — an integration in company A never sees data from company B.
Which products work together?
Most active Ottili ONE products are connected through the platform. Typical examples:
| Product | Role in the integration |
|---|---|
| Ottili HQ | Business data (orders, invoices, customers) as the shared source for AI, Flows and Coder |
| Ottili AI | Uses HQ, LD3 and Files data; drives actions through tools (MCP) |
| Ottili LD3 | Produces content from HQ and source data; publishes through connectors |
| Ottili Flows | Connects products and external tools through triggers, conditions and actions |
| Ottili Coder | Reaches repos, APIs and workspace data; automates through connectors |
| Ottili Cloud | Hosts workloads and provides infrastructure connectors (e.g. Cloudflare) |
| Ottili Files | Shared storage that every product reads and writes |
External connectors (integrations with third-party tools)
Through connectors you bring the tools you already use into your workspace. Each connector is a one-time, authorized connection; after that, data flows into your company. The connectors and their status come from the canonical connector registry of the public surfaces.
Live connectors
These connectors are available today:
- Marketplaces*: Shopify, eBay, Kleinanzeigen
- Payments*: Stripe, Billing systems (reconciliation), Invoices (Ottili workspace)
- Communication*: Gmail, Slack, Telegram
- Developer tools*: GitHub, Cloudflare, API Keys, Custom APIs
- AI & models*: Ottili AI tools (MCP), Anthropic, OpenAI
Planned
These connectors are planned (not yet generally available):
- Marketplaces*: Amazon
- Communication*: Discord
- Developer tools*: Cursor
- AI & models*: Gemini
- Automation*: n8n, Brave Search, Google Places
Internal services
Some connections are internal Ottili services and are not offered as external connectors: Ottili Files* (shared storage) and Ottili Auth* (login and session). They are clearly marked internal and never leak a secret, route or local path.
Status and availability
Ottili ONE clearly distinguishes maturity levels. The main status labels you see in the platform and in the documentation:
- Live* — generally available and fully supported.
- Beta* — publicly available in a pre-release state; may still change (e.g. Ottili Coder, Ottili LD3).
- Private Beta* — available to an invited group.
- In Development* — actively being built, not yet available.
- Planned* — accepted and scheduled, but not yet started.
- Concept* — an early idea under consideration.
The current status labels are explained in [Understand feature-status labels](/docs/understand-feature-status-labels). Connectors without a docs link are deliberately not documented yet ("Docs in progress") so no invented or dead links appear.
Related articles
- [Connect an integration](/docs/connect-an-integration) — bring a tool into Ottili ONE.
- [Platform layer and product layer](/docs/platform-layer-and-product-layer) — how the stable platform supports the products.
- [Shared permissions and entitlements](/docs/shared-permissions-and-entitlements) — who can do what.
- [Ottili HQ overview](/docs/business-hub-overview) — the business surface.
- [Ottili AI](/docs/ottili-ai), [Ottili Coder](/docs/ottili-coder), [Ottili Flows](/docs/ottili-flows) — the connected products.
- [Files across products](/docs/files-across-products) — the same principle for storage.
Was this article helpful?