Documented public contract
A stable, versioned public API is shared by the products and your own integrations. Internal services are not part of the public reference.
Ottili Core
The shared backend foundation behind every Ottili product.
Ottili Core is the platform base every Ottili ONE product is built on. It gives Ottili HQ, Ottili AI, Ottili Coder, Ottili LD3 and Ottili Cloud one identity, one company context, one permission model, one billing and credits wallet, one public API surface and one tenant-isolated data store — so they feel like one connected system instead of five disconnected apps.
The platform base
One foundation, not five separate backends.
Each Ottili product is a real product with its own surface. Underneath them sits Ottili Core — the shared backend foundation — together with Ottili Console, the operational surface teams use to run and observe it. You use the products; Ottili Core is what keeps them connected, isolated and consistent.
Backend foundation
Nine shared systems, one foundation.
These are the backend systems every Ottili ONE product is built on. They are shared, company-scoped and consistent across the whole ecosystem.
- Beta
Unified identity
One Ottili Auth identity reaches every product. A single sign-on, one account and one API-key layer across products, modules and integrations — no per-product accounts to manage.
- Beta
Company context
Every action runs in one company context. Customers, orders, content and tasks live in one company space that every product shares, so AI and workflows always see the right context.
- Beta
Permissions & roles
A single role and permission model governs access across products and modules. Define a role once and it is respected across the whole ecosystem, including approval gates.
- Private Beta
Billing & invoices
One company billing relationship backs every product. Invoices, subscriptions and payment state are managed in one place and attributed to the company, not scattered per product.
- Beta
Credits & usage
A single company credits wallet backs AI, execution and API usage across every product. Spend is reserved before work begins, settled on success and released on abort — so retries never double-charge.
- Beta
One public API surface
A documented public API contract is shared by the products, integrations and your own apps. Company context is resolved before any request, and no private detail is returned in the response.
- Beta
Capability & feature registry
A shared registry describes the capabilities, modules and features available to a company — with their status and visibility. It drives what each product and workspace actually shows, from one source of truth.
- Beta
Tenant-isolated data
Every business object belongs to a company. Data is stored in a tenant-isolated store bounded by company id, so one company can never read another company's data through the public surface.
- Beta
Shared infrastructure
Shared infrastructure services — files, events, jobs, caching and reliability — are reused by every product. The products do not each stand up their own stack; they build on the same foundation.
How it fits together
Ottili → Ottili ONE → Core → products.
The brand, the software ecosystem, the shared backend foundation and the products you use form one clear hierarchy. Ottili Core and Ottili Console are the layer every product is built on.
Ottili
Top-level brand
Ottili ONE
Software ecosystem
Platform base — shared foundation
- Ottili Core
- Ottili Console
- Unified identity. One Ottili Auth identity across every product.
- Company context. One company space every product shares.
- Permissions & roles. One role model across the ecosystem.
- Billing & credits. One wallet and one billing relationship.
- Public API surface. One documented public contract.
- Capability registry. What is available, with status.
- Tenant-isolated data. Company-bounded, isolated storage.
- Shared infrastructure. Files, events, jobs, caching, reliability.
Product layer — what you use
- Ottili HQ
- Ottili AI
- Ottili Coder
- Ottili LD3
- Ottili Cloud
Ottili Core is the backend foundation. Ottili Console is the operational surface for running and observing it. Both sit beneath the product layer and are not sold as standalone products.
For developers
One public API, clearly separated from internal services
The public API is the contract your own apps and integrations speak. It is documented separately from the internal services that run the platform, so the public reference never exposes internal endpoints, admin routes or infrastructure detail.
Company context resolved for you
The public API resolves your company and permissions before any request, so your app always acts within the right company boundary.
Scoped API keys
Issue company-scoped API keys from the console. Keys are scoped to your company and never expose internal service credentials.
Predictable responses
Responses carry the data and status your app needs, with no private infrastructure detail. Failures return a clear, normalized error envelope.
Availability
Available through Early Access.
Ottili Core is available through the Ottili Early Access program. Core systems are operational while selected customer-facing products are prepared for public beta. The internal services are not exposed publicly; only the documented public API and product surfaces are. Nothing is charged without explicit confirmation.
Build on one shared foundation.
Start with one workspace and let Ottili HQ, AI, Coder, LD3 and Cloud share the same backend — identity, company, permissions, billing, credits, APIs and data.