- Modell
- qwen2.5:7b (lokal via Ollama, aihub.iio.space Fallback)
- Erzeugt
- 2026-08-05
- Felder
- 77
- Norm
- Einfache Sprache ~B1 — nicht Leichte Sprache (DIN SPEC 33429)
- Geprüft von
- Operator-Chat-Freigabe (gate.iio-space-einfache-sprache-content-review-v2, Session AGT-1DED3AED) · 2026-08-05
An operating system,
not an application.
IIO is an agentic operating system for organizations. Not 14 individual products — butone engine that adapts to different problems via specialized adapters. 524 building blocks grow organically and are interconnected.
One engine, many adapters.
Every product is not a new build — it's a view onto the same IIO engine, projected through specialized adapters for different use cases.
Every building block is a skill, a flow, a module, or a layer. They are interwoven through a network of dependencies, data interfaces, and evidence trails. When you use one building block, you automatically get the building blocks it relies on. That's composability. It's not overload — it's elegance through structure.
Feature request → coding-agent work lane → prompt-to-deploy
Flow definition → sequential/parallel execution → evidence trail
Content → publishing engine → multi-language, GEO-optimized
Infrastructure operation → policy-driven dispatch → HITL-gated
Configuration card → direct executor → system states
The 3 axes of the system.
Every building block acts on three orthogonal axes:Governance (what may happen),Operation (what runs),Intelligence (what the system learns).No axis dominates the other — they work together.
Governance
Was darf passieren — und wer entscheidet. Was darf passieren — und wer entscheidet?
Kontrolle als Baustein, nicht als Nachgedanke. Freigabe-Stufen, Policy-Entscheidungen, Nachweisführung, Rechts- und Aufsichtspflichten. Jede Aktion im System trägt ihre Begründung mit sich. Kontrolle ist wichtig für jede Aktion im System.
Operation
Was läuft — und was es kostet. Was läuft – und wie teuer.
Der laufende Betrieb einer Organisation, in Bausteinen: Finanzen, Personal, Vertrieb, IT, Service, Beschaffung, Projekte. Jeder Baustein ist ein Fachgebiet mit eigenen Flows, Daten und Kennzahlen. Der laufende Betrieb hat Fachgebiete wie Finanzen und Personal.
Cooperation
Wer schließt sich an — und wie. Wer nimmt teil — und wie.
IIO ist kein geschlossenes Produkt. Fremde Agenten, fremde Systeme, fremde Organisationen und die physische Welt docken über offene Protokolle an. Wissen fließt, ohne die Kontrolle abzugeben. IIO dockt mit fremden Systemen an. Wissen fließt.
What a building block looks like.
A concrete example:HITL Gate Operations from the domainkontrolle-freigabe. Fully declined across all 3 axes, all components, all connections.
IIO HITL Gate Operations — open, check, approve, or reject gates. Central building block for human-led approvals.
Approval levels, policy decisions, evidence trail
Gated operations, approval workflow, SLA tracking
Policy AI, decision learning, gate evolution
- Skill hitl-ops
- Flow gate-decision
- Evidence template gate-*.yaml
- Gate-definitions YAML
- Compliance Layer
- Execution Dispatch
- Queue Operations
- Neural Graph (learning from decisions)
Every production deployment waits for an open HITL gate. Without approval: execution blocked. With approval: evidence generated automatically.
Platform · Solutions · Consulting.
Three different ways to use IIO. Depending on whether you build yourself, want ready-made solutions, or need guidance.
Platform
Technical engines — the building blocks everything else is made of.
Private AI-Infrastruktur — LiteLLM, GPU-Fleet, Cost-Guard.
HITL-Gates, EU AI Act, ISO 42001, MCP — Governance by Design.
Dispatch, Sandbox, prompt_to_deploy, CI/CD — agentisches Coding.
www-publishing, Living Book, Theming — Content als Bewusstsein.
Intent → Source of Truth → on-demand Code. Karten statt Repos.
Solutions
Ready-made solutions — composed from platform components.
HR, Finance, Legal, Contracts, IT-Mgmt, Groupware — der Arbeitsplatz.
Coding + IT-Management + SOL + QA — die Entwickler-Umgebung.
Publishing + SEO/GEO + Campaigns + Analytics — Sichtbarkeit.
Neural Graph + [Kunde] + Org-Transformation — die kognitive Schicht.
EU AI Act + ISO 42001 + DSAR + Training — Compliance-fertig.
Consulting
Human-led — setup, mandates, partners.
Node Bootstrap, SSO, Monitoring, Team-Onboarding.
SOW-basiert, Discovery → Delivery.
Vermittlungsprovision (8% Silver-Tier) oder Flat-Fee (Associate-Tier) je vermitteltem Vertrag — real aktiv ([Kunde], [Kunde]).
White-Label-Reseller mit Revenue-Split 85% Betreiber / 15% IIO-Platform — vertraglich vereinbart ([Kunde] CertOps Tier-1), noch kein aktiver Sub-Scope.
What IIO delivers. What it doesn't.
Honest boundaries. Nothing is good for everything — and that's OK.
✓ IIO delivers:
- ✓ Governance infrastructure — HITL gates, Policy Decision Points, compliance trail
- ✓ Agentic workflows — flows, agents, evidence-based actions
- ✓ Multi-tenant operations — isolation, quotas, revenue sharing
- ✓ EU AI Act & ISO 42001 compliance — by architecture, not as an add-on
- ✓ Growth without breakage — new layers without a restart
- ✓ Open-source ecosystem — OCC, community contributions, OSS licenses
- ✓ Deterministic operations — same input → same output
- ✓ Learning loop — workflows improve from decisions
✗ IIO is not:
- – Low-code / no-code for non-technical users — IIO is for teams with a development background
- – A quick SaaS install — setup takes 4–8 weeks of professional work
- – A magic fix for bad processes — IIO visualizes them, the fix needs decisions
- – A data store alone — IIO orchestrates, it doesn't automatically store all data
- – Plug-and-play for legacy systems — integration needs adapters, mapping, tests
- – Ready for startups on day 1 — grows with you from ~20 employees
- – A license-management tool alone — IIO has a license layer but isn't primarily an LMS
- – Free — self-hosted infrastructure has real costs (GPU, storage, staff)
Where does IIO run?
Flexible — your infrastructure, your rules, your compliance. Reference: layer-infra-placement Skill.
Shared (Shared Cell)
Multiple tenants on one GPU cell. Cost-efficient for smaller organizations. Data isolated via contextualization (CDT layer). Slowest setup, most cost-effective operation.
Dedicated (Dedicated Cell)
Your own GPU + storage. No neighbors. Maximum control over resources and performance. SLA possible. A realistic choice from ~50 employees with daily AI operations.
On-Premise (Your Infra)
IIO runs on your servers, in your data center or cloud account. Full control, full responsibility. For companies with strict data-localization or air-gap requirements. Needs an IT team.
Maturity of the Overall System.
This is not a marketing promise — it's a live operating system with real limits and real growth.
AI governance — 82% of all controls implemented and auditable.
Total workflows, of which live in operation (numbers above).
Governance, operations, and intelligence layers fully functional.
Skills, flows, modules, layers. New building blocks emerge from real customer projects.
Detailed overview of all building blocks and flows:
What are you ready to build?
IIO is not for everyone — but if you need autonomous systems, secure AI governance, and real growth, let's talk.