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.
Source code
One repository per component.
19 open-source repositories (Apache-2.0) in the krizaka organisation. Take only what your application needs, or clone the whole workspace with krizaka/orazaka.
Foundation
Reusable by any Krizaka application: build, contracts, edge, UI kit.Parent POM (Spring Boot / Spring AI BOMs, plugin management, Orazaka BOM) and the shared governance test kit (ArchUnit rules, Testcontainers base) for every Orazaka JVM repository.
Tier-1 platform contracts shared by every Orazaka service: the job plane (jobs-api) and the application-persistence ports (persistence-app-api). Pure interfaces and records, zero implementation.
← orazaka-build
Transparent HTTP edge in front of every Orazaka service: routing, API-key → JWT exchange, CORS and tracing. Spring MVC + virtual threads.
← orazaka-build
@krizaka/orazaka-shared (TypeScript types, Zod schemas, design tokens) and @krizaka/orazaka-design-system (React components, Tailwind preset, theme, icon registry) for Next.js and React Native apps.
Domain services
Users, notifications, billing — plug them into a new application as they are.Reusable user management for any Krizaka application: registration, e-mail verification, login (password + Google/GitHub OAuth), forgot/reset password, profile & preferences, API keys, RBAC and JWT issuance.
← orazaka-build
Channel-based notification delivery for any Krizaka application: e-mail (SMTP), SMS (Twilio) and webhooks behind one DeliveryClient port, driven by platform events (user registered, password reset) or explicit notification requests over AMQP.
← orazaka-build
Credits, wallets, plans, subscriptions, pricebook and metering (hold → settle → release) as a reusable billing service, with its contract (billing-api) and a typed HTTP client (billing-client).
← orazaka-build
Orazaka AI engine
The cognitive engine and the services that host it.Studio & pack marketplace: pack catalogue, studio blueprints, installations and saga-driven runs, with its contract (studio-api) and HTTP client (studio-client).
← orazaka-build · orazaka-contracts · orazaka-billing
The Orazaka cognitive SDK: AiClient & provider mesh (core), the interceptor pipeline, tools (MCP · RAG · sandbox), use-case orchestration (business), application persistence and asset encryption.
← orazaka-build · orazaka-contracts · orazaka-billing · orazaka-studio
Interactive ingress of the Orazaka engine: chat (SSE streaming), intents, models, pipeline, MCP and job APIs — translates transport into Intentions, never business logic.
← orazaka-build · orazaka-contracts · orazaka-users · orazaka-billing · orazaka-ai-engine
Asynchronous job executor of the Orazaka engine: drains the interactive and batch lanes, owns the capability registry and the worker registry.
← orazaka-build · orazaka-contracts · orazaka-users · orazaka-billing · orazaka-ai-engine
Knowledge & RAG retrieval service (pgvector) with asynchronous indexing.
← orazaka-build
Connector automation (Jira, Slack, WhatsApp, Messenger, CLI agents) with Quartz scheduling and execution telemetry.
← orazaka-build · orazaka-billing
Native workers
Native media inference, outside Docker.Applications
Web, administration, mobile and CLI.Next.js (App Router) client of the Orazaka platform with its mandatory BFF.
← orazaka-ui-kit
Next.js SecOps & administration console of the Orazaka platform.
← orazaka-ui-kit
Expo / React Native client of the Orazaka platform (talks to the edge with Bearer tokens).
← orazaka-ui-kit
The `orazaka` developer CLI: install, start, dev, test, docs and pack tooling for the Orazaka workspace, with an offline SQLite queue.