Reading guide
Orazaka, explained simply.
Before you dive into the map, here's the mental model. Orazaka is an AI orchestration engine you host yourself: every request flows through a deterministic pipeline, step by step, and never leaves your network.
Let's follow one real request.
“Summarize this contract and flag the clauses that don't comply with Law 25.”
Here's what happens to it, from your question to the answer:
- Presentation
You ask from the web client, the mobile app, the CLI or the admin console.
WhyFour front doors, a single engine behind them.
- Entry Gate
The gate receives the request and routes it into the engine — streaming (SSE) when the answer arrives token by token.
WhyOne controlled entry point: nothing touches the models directly.
- Security & Logic
Before any compute, Orazaka authenticates you, checks permissions (RBAC), and enforces quotas and business rules.
WhySecurity and governance happen before inference — not after.
- Cognitive Engine
The stateless hexagonal core orchestrates the request and coordinates the data flow.
WhyThe conductor: reproducible on every single call.
- Workers & Pipeline
The request flows through 15 interceptors (system context, memory, RAG, safety), while async workers handle media and MCP integrations.
WhyThis is where “cognition” is assembled, one ordered step after another.
- Persistence
Sessions, vector memory (pgvector) and identities are stored in your own databases.
WhyYour data stays home, from the first byte to the last.
→ The locally-validated answer comes back to you. Zero data left your network.
The heart of Orazaka. Coordinates stateless AI request execution and orchestrates the data flow.