Technology

ZiyaOS

The operating system our AI applications run on

ZiyaOS is the technological foundation of Ziya ONE, Ziya Navigator and every future Ziya product: one layer for connectivity, permissions, models and operations, built once and reused everywhere.

Free initial consultation See Ziya ONE

The four layers

Connectors
Agent Runtime
Governance
Model Layer

One core, many apps

What appears above as four layers is a set of concrete parts underneath. Every app on ZiyaOS reaches the same ones - and no app gets past anything it was not granted.

Apps

TranscriberSlidesContract reviewQuote agentService chatmore apps

TriggersAgent RunsConductorSandboxesTransactionsSubagentsP2PEventsTriggersAgent RunsConductorSandboxesTransactionsSubagentsP2PEvents

SkillsCapabilitiesModel CardsContext BuilderMemoryViewsActionsSkillsCapabilitiesModel CardsContext BuilderMemoryViewsActions

MiddlewaresRolesExecution RulesSecret StoreCost CenterAudit LogGovernanceMiddlewaresRolesExecution RulesSecret StoreCost CenterAudit LogGovernance

ZiyaOS

The apps that run on it

ZiyaOS is not a program but the layer beneath one. What people open are apps: each with its own interface and its own job, all on the same connections, the same roles and the same governance.

Ziya ONE

Chat and collaboration with AI agents

The app most people open every day. They ask in natural language, the agents answer with sources from your own systems. Assistants are configured per department, and artefacts and folders keep results where the team can find them again.

Agent chat with citations
Assistants per department
Artefacts and folders
Shared prompt library

Ziya Navigator

AI strategy, portfolio and maturity

The app for the level above the daily work, and a product in its own right: goals, challenges and use cases in one place, every case scored on potential and risk, ordered into a roadmap and measured against the benefit realised after delivery. A different audience and a different interface - the same foundation.

Goals with challenges and use cases
Scoring on potential and risk
Roadmap, projects and budget
AI maturity year on year

Ziya NavigatorUse cases

New use case

Use cases

Manage prioritised use cases and track where their scoring stands.

Portfolio: risk against potential

Not rated - placed before the scale

Potential

Low Hanging FruitRecommendedTransformation ProjectMoon ShotUninteresting use casesUC-02UC-07UC-04UC-12UC-11UC-16UC-15UC-23UC-19UC-28UC-31UC-33UC-40

0255075100

Risk

TitleDepartmentPotentialRisk

UC-07Draft quotes from CRM dataSales85 %18 %

UC-12Invoice checking with anomaly detectionFinance62 %31 %

UC-19Optimise shift planning to demandProduction38 %74 %

13 use casesPage 1 of 1

Platform and app

The usual routes force a choice: a tool that helps a little everywhere, or an application that really solves one case. ZiyaOS is both, because the breadth sits in the core and the depth in the app on top of it.

Only ZiyaOS is both at once.

Every alternative has a gap

There are four usual routes to an AI application. Each covers one half: either the depth of a single use case or the breadth across many. None covers both.

Workflow toolsAI assistantsBuy an appBuild an appZiyaOS

In depth

A real app for its users

Connected and adaptable

Use case covered in depth

In breadth

One stack for all of them

A new use case without a new project

Synergies between the apps

MetProblematicGap

Built once, used everywhere

Every AI application needs the same foundations: connectivity, permissions, model access, operations. ZiyaOS bundles them into one operating system that Ziya ONE, Ziya Navigator and every future Ziya product run on.

The apps that run on it

Ziya ONEResearchTrainingWorkflowsZiya Navigator

ZiyaOS

01
Connectors
A shared connectivity layer for ERP, CRM, DMS and file storage. Connected once, a source is available to every application on ZiyaOS.
02
Agent Runtime
The runtime environment in which agents use tools, log intermediate steps and interact safely with systems.
03
Governance
Roles, permissions and traceability in one place: who may see what, which agent may do what, and what happened when.
04
Model Layer
One access point for all language models, whether GPT, Claude, Gemini or open models in your own data center. Interchangeable per use case.

ERPCRMDMSMicrosoft 365File storage

Your systems

Governance from the first minute

Roles, permissions and logging are not a retrofit but the foundation: who may see what, which agent may do what, and what happened when.

01RequestSomeone asks a question or starts a run.
02IdentityWho is asking, and in which role.
03Permission checkWhich folders, documents and systems that role may see.
DeniedWithout the permission the path ends here - and is logged all the same.
04ToolThe agent reads exactly the released sources and no others.
05ModelThe answer is produced in the model layer.
06LogWho, when, which document, which model.

Sovereignty starts with ownership

Where your data sits is one question. Who owns the company that builds and runs the software is the other - and it decides whose law can reach that data if it comes to it.

Ownership: German owners, no foreign parent company
Legal framework: German and European law, no external reach-through
Operations: ISO 27001-certified EU data centres, on-premise or air-gapped
Development: Built and maintained by the team in Dortmund

Frequently asked questions

Where can ZiyaOS run?

In ISO 27001-certified EU data centres, on-premise in your own infrastructure behind your firewall, or fully air-gapped with no internet connection. Cloud operation is GDPR-compliant with a data processing agreement; air-gapped we work with open models in your own data centre on request.

Which systems can be connected?

ERP, CRM, document management, Microsoft 365 and file storage through the platform's connectors, plus custom connectors for business systems and open interfaces for anything else. A source is connected once and is then available to every app on ZiyaOS - under the same roles and permissions.

How quickly is a first application productive?

The first eighty per cent or so of a use case is the part every use case shares - connectivity, permissions, model access, operations - and ZiyaOS already brings it. The remaining twenty per cent is your domain expertise and matures iteratively in operation, rather than putting a large project in front of the first use.

Can we build our own apps on ZiyaOS?

Yes. Prebuilt apps can be loaded as templates and tailored, and your team builds its own with low-code on the SDK. Every app follows your branding from one central UI kit, and each runs in a sandbox: what is not granted is not reachable.

Can I buy ZiyaOS on its own?

ZiyaOS is not a standalone product but the technological foundation of our products and individual AI solutions. You benefit from it automatically: every Ziya product and every customer project runs on this infrastructure.

Why is a dedicated operating system faster than individual projects?

Because connectivity, permissions, model access and operations consume most of the time in individual projects, and with us they already exist. A new use case then consists almost entirely of the actual business logic.

What does ZiyaOS mean for future-proofing?

Applications on ZiyaOS are decoupled from individual models and vendors. When better models appear, we swap the model layer, not your application.