The architecture behind AIOS.
A shared object model, specialized runtimes and clear connections form the platform’s foundation.
Control plane and interface
The Django backend manages objects, APIs, access and orchestration. The Next.js frontend provides the workspace. WebSockets keep changes and ongoing work visible in the interface.
Trace a concrete task through the architecture before assessing individual components. The interface presents the brief and its state; the backend manages the related context and orchestration. The agent runtime handles agent execution using the available tools and model connections. The resulting artifact then belongs back in the task’s business context.
Dedicated execution runtimes
The native Rust agent runtime executes agent tasks. Model runtimes connect local and external inference. Website projects run through the site runtime. This lets execution environments evolve separately from the central data model.
For operations, distinguish messages, state and artifacts. A message describes a change or initiates work. Relational data holds structured information, while files and larger results live in object storage. Plan recovery and investigation around these different responsibilities. A reachable service alone does not establish that a task completed correctly from the user’s perspective.
AIOSEvents and durable state
NATS connects services through events and messages. PostgreSQL stores relational data; Redis supports transient state and fast access. S3-compatible object storage manages files and artifacts.
Start investigating an issue by narrowing down its visible effect: Is an object missing, is a run still open, or is a resulting artifact inaccessible? Record the task, time and affected area before moving to the responsible component. System Manager provides authorized operators with visibility into services and runtimes; it is not part of ordinary SaaS user access.
One foundation, multiple deployment models
Public cloud, dedicated cloud and your own infrastructure place different demands on networking, updates and operations. The architecture stays modular; resources and responsibilities must be planned for each environment.
Try it yourself
Adapt the placeholders to your task. This example is a template for your work with AIOS.
Observed operation: [Task and expected result]
Time and environment: [When and where did the issue occur?]
Visible effect: [Missing object / run state / artifact / other observation]
Affected components: [Where known]
Current state: [What is visible and what is missing?]
Last known change: [Configuration or update, if known]
Responsible operator: [Person/team]
Next investigation step: [Specific observation that would narrow down the cause]
Keep assumptions separate from confirmed observations. Do not include credentials in the handoff.Read components by responsibility
| Area | Role in the described architecture | Typical review question |
|---|---|---|
| Django and Next.js | Objects, APIs, access, orchestration and workspace interface. | Is the business context present and accessible? |
| Agent, model and site runtimes | Specialized execution of tasks, inference and website projects. | Which execution environment is involved? |
| NATS and Redis | Messages between services, transient state and fast access. | Which messages or transient states matter to this workflow? |
| PostgreSQL and object storage | Relational data, files and artifacts. | Are the required data and results available? |