User-isolated containers
Real process isolation per user — not just tenant separation.
Agentic OS
Orchestrator, agent roles (Office · Developer · Researcher · SysAdmin · Security Advisor · …), goal engine with dependencies, runners for website and app builds, skill system, multi-LLM router, user-isolated containers — all in one managed runtime.
How the OS works
Whether a WhatsApp message, voice memo, photo or coding session: everything starts with an input and flows through the same layers of the Agentic OS. Scroll through the stack.
01 · Input
WhatsApp message, voice memo, site photo, web form, mobile push, API webhook. Whether app, agentic loop or coding session — the input field is always the beginning. One channel, one event, one task.
02 · Orchestrator + agent team
The orchestrator receives the task and spins up the matching agent team: Office, Developer, SysAdmin, Researcher, Security Advisor. Roles hand off to each other, debate interim results, escalate questions. Not a single chatbot doing everything alone.
03 · Skills + runners
Skills give agents access to email, calendar, WhatsApp, ERP, PDF, custom APIs — tenant-scoped and auditable. Runners are real execution environments: website builds, app deploys, CI/CD pipelines. Not toy tools — productive compute.
04 · Multi-LLM router
Triage with Haiku, reasoning with Sonnet, vision with GPT-4o, routine with Mistral, code with open source. Each task class gets the right model. If a provider fails or rate-limits, the router fails over automatically.
05 · Security Gate
Payments, outgoing mail, ERP writes, price changes: anything MEDIUM or HIGH risk lands at the Security Gate. A human approves, the audit trail is written. LOW risk (show draft, ask for info) passes through.
06 · User container
The whole stack above doesn't run in a shared process — it runs in a container that belongs exclusively to the user. Credentials, interim state, tool state — all physically isolated. Managed runtime: we handle provisioning, scaling, health.
8 pillars
The deep-dives above show how it looks. Here's the compact recap, so you have the core at a glance.
Real process isolation per user — not just tenant separation.
Approval workflows for risky actions. Full auditability.
AES-256-GCM, per user, per integration. OAuth refresh built in.
Multi-step workflows with dependencies — not single-shot agents.
Best model per task: Claude, GPT, Mistral, open source. No lock-in.
Data processing exclusively in Europe. EU-AI-Act-ready.
One agent, all systems — email, calendar, ERP, industry software.
Every AI team action traceable and documented.
Multi-LLM router
One model per class of task. The AI team picks the right model per task — by quality, cost, latency or hosting requirement. A provider outage automatically reroutes to the next.
| Task | Model family | Why |
|---|---|---|
| Triage & categorisation | Haiku, small models | Cost — 95% of inbox events don't need a large model |
| Decisions & text generation | Sonnet, GPT-4o | Quality on reasoning and customer-facing copy |
| Vision: measurements, damage photos, sketches | Vision-capable LLMs | Multi-modal — text + image in one pass |
| Routine generation, templates | Open-source (Mistral, Llama) | EU hosting, cost, reproducibility for regulated industries |
| Code, tool use, structured outputs | GPT code models | Tool-use performance, JSON-mode stability |
| Long-context recall | Claude 1M context | Large surveyor files, ERP dumps without chunking |
Every row has a defined fallback. If a provider fails or rate-limits, the task keeps running — just maybe with 0.4s more latency or 20% more token cost. Not a single task fails on a single vendor.
Compliance & trust
Privacy isn't a checkbox. Here's what we commit to and what you can verify.
Compute and storage exclusively in EU data centres. No US cloud in the hot path. Sub-processors documented on the trust page.
Data processing agreements (DPA) available. Data subject rights (access, deletion, portability) are product features, not compliance theatre.
View DPA →Each app is classified by EU-AI-Act risk class. Transparency logs and human oversight are built into the platform — not retrofitted.
Every AI team action is logged structurally and searchable. Retention configurable per tenant. Export for external audits.
Security policy →Who we are up against
The full comparison against legacy enterprise, AI-lab runtimes, consumer EU AI and vertical tools lives on the home page. Here is the short version of why platform buyers come to us.
OpenClaw vs. Linkworld
OpenClaw shows what agentic AI delivers for individuals — 300,000 GitHub stars in months. For companies the governance layer is missing: tenant isolation, approval workflows, GDPR, packaged vertical apps. Linkworld provides exactly that layer.
Three example apps show what the platform is built for. Custom apps are next.