Home / Architecture
TUEO PRODUCT ARCHITECTURE

Ten products, one system

Not ten tools sold separately, but one complete chain that runs from identity, knowledge, compute, collaboration, orchestration, and coding to execution and private delivery. Below is how they fit together.

TUEO Console Private foundation · Offline · Bundled k3s · One-click install · Deployment & ops
Experience layer — where people and AI employees work together
CO
Collaboration core · Flagship

Cohort

AI-employee collaboration, messaging engine, cognitive loop, and signal routing. People and AI work together in the same workspace.

desktop clientservercognitive loop
ST
Application orchestration platform

Studio

Business users turn processes into AI applications through conversation; once published, they are invoked by people, AI employees, and external agents.

OrchestrationPublishUse
Invoke capabilities via the @tueo SDK
Capability layer — one gateway governing the procurement, authorization, and invocation of every capability
CA
Capability marketplace · Invocation gateway

Capabilities

Registry SSOT · install governance · credential vault · invocation gateway (dispatched by kind). Cohort and Studio consume through the SDK and hold no platform logic of their own.

Registry SSOTInstall / licenseCredential vaultMeteringProcurement governance
kind = backed → sandboxed execution
Execution layer — where work actually gets done, locked inside a sandbox
EX
Sandboxed execution runtime

Executor

K8s sandboxes, real coding, and connector-isolated execution. High-risk actions run with network-isolated unshare and full audit. AI doesn't just answer — it genuinely runs within controlled boundaries.

K8s sandboxMultiple runtimesConnector isolationNetwork-isolated unshare
CB
Coding execution engine

Codex-build

The coding core of an AI development team: it genuinely reads code, edits files, runs tests, and produces MRs. Enterprise identity boundaries apply, credentials never leave the server, and every action is confirmable and auditable.

Real executionManaged runtimeMultimodalSubagent consent
SK
Developer ecosystem · SDK + source

Skillplugins

manifest → registers into Capabilities backend → runs on Executor frontend → renders in Cohort
Three foundation bases, supporting all the products above
ID
Identity foundation · cross-cutting support

Identity

OIDC SSOSCIM auto-provisioningSAML federationMFAOrganization / tenant SSOT
EN
Knowledge & memory foundation · cross-cutting support

Engram

Knowledge baseConversation memoryEntity graphAuto-organizing
IN
Compute & model foundation · cross-cutting support

Inference

Dual-pool computeModel servingTrainingOffline delivery
How one call flows through

From a single sentence to controlled real execution

People / AI employees
initiated in Cohort
→request
Cohort / Studio
experience layer
→SDK
Engram
knowledge & memory · grounds AI decisions
→invoke
Capabilities
validate · authorize · inject credentials
→dispatch
Inference
model serving · compute
→execute
Executor
executes in sandbox
→return
Back in Cohort
renders result
End to end, Identity authenticates, Capabilities governs, and Executor isolates — the stronger the AI, the clearer the boundaries.
Collaboration matrix

Where each product sits and what it depends on

Product Position in the system Dependencies / dependents Relation
Cohort Experience layer · collaboration core flagship Depends on Identity for login, calls Capabilities through the gateway, embeds Studio consumer
Studio Experience layer · application orchestration platform Depends on Identity and Capabilities; embedded by Cohort consumer
Capabilities Capability layer · marketplace and invocation gateway Invoked by Cohort / Studio via SDK; dispatches to Executor gateway
Executor Execution layer · sandbox runtime Receives dispatches from Capabilities; runs Skillplugins backends runtime
Codex-build Execution layer · coding engine Driven by Cohort work orders; runs in the Executor sandbox or local pairing engine
Identity Foundation · cross-cutting support Supports login, directory, and tenant isolation across all products foundation
Skillplugins Ecosystem · SDK + plugin source Registers into Capabilities; consumed in Executor / Cohort supplier
Console Foundation · intelligent-foundation operations layer Deploys everything above on-premises at the customer's site and operates it from one entry point deployer
Engram Foundation · knowledge & memory substrate Consumed by Cohort / Studio via SDK; sits alongside Identity as cross-cutting support foundation
Inference Foundation · compute & model serving (model-serving substrate) Cohort / Studio / RAGFlow call models through a unified endpoint; dual-pool compute managed independently foundation

Want to see this system in action?

Book a demo and walk the complete path from login to real sandboxed execution.

Book a demo →Back to the product system