Krizaka

Open source. Closed to compromise.

We build what others take years to get right — AI that never leaves your walls, a video platform that pays every cent exactly once, a dating app where you talk first. Compliance and security aren't add-ons: they're compiled in.

Website · Products · Docs · Open source · Roadmap · Contact

Orazaka The AI that never leaves home. A multimodal AI orchestration engine — chat, RAG, agents, image, audio, video — where every request crosses a deterministic interceptor pipeline to the best local model. Your documents, your models, your network: nothing leaves it. Law 25 and GDPR by design. One command, orazaka demo seed, sets up Eric's day on your own machine. Workspace · Docs · How it works · Demos

Orochia Creators get paid. Every cent, exactly once. The creator video platform: direct-to-CDN 4K streaming, an Explorer that is never empty, complete stories (sound, likes, tips, private replies), audiences the creator chooses, auctions and challenges paid in credits held in escrow until delivery. Creators keep 90 %, settled once on a double-entry ledger. Built-in 18+ compliance — on the web and on iOS and Android (orochia-mobile). Try it · Repository · Docs · Video tour

Yazakia coming soon The dating app where you talk first. No swipe, no catalogue, no score. An AI agent gets to know you, then opens a small batch of people who match you in both directions — with reasons, never a score — and the next batch learns from your debrief. iOS and Android, built on the Krizaka blocks, with Orazaka as its AI engine. Coming soon · Repository · Mobile app · Get notified

Yororis under construction A listening space with a face and a voice. Powered by Orazaka's wellbeing pack: an AI presence that listens, reflects back and stops — a set length, a set number of moments, and what it keeps is a three-line summary, not a transcript. We are building it in the open and studying its framework — legal, ethical, clinical — before anything is offered. Nothing is online, and there is no date.

Orazaka — Eric answers a customer from his own documents, then generates the product photo. Everything ran on one Mac. More demos	Orochia — Alex, a fan, supports Elena, a creator; she sees it arrive and keeps 90 %. Recorded on the real app. Elena's and Alex's day

What the repositories actually run — each badge is a dependency you can find in a pom.xml, a package.json, a requirements.txt or a workflow.

Layer	Stack
Backend
Data & messaging
AI, on your machines
Web
Mobile
Delivery
Quality

Claims are cheap; each line below links to the file that proves it.

Every product is built on Krizaka building blocks — open-source components any application can take on its own, published on Maven Central and npm. The products consume them; they do not own them.

Clone the whole Orazaka platform — building blocks included — with krizaka/orazaka.

Import the BOM once, add a starter, and every com.krizaka artifact resolves to one coherent release — 0.2.0 is out, signed (B523D2E9DE35AE17882361BE25DF268F9213EB5D, on keyserver.ubuntu.com).

A service with the starters:

<dependencyManagement>
  <dependencies>
    <dependency>
      <groupId>com.krizaka</groupId>
      <artifactId>krizaka-bom</artifactId>
      <version>0.2.0</version>
      <type>pom</type>
      <scope>import</scope>
    </dependency>
  </dependencies>
</dependencyManagement>

<dependencies>
  <!-- problem details, correlation id, pagination -->
  <dependency>
    <groupId>com.krizaka</groupId>
    <artifactId>krizaka-spring-boot-starter-web</artifactId>
  </dependency>
  <!-- session JWT and SERVICE tokens -->
  <dependency>
    <groupId>com.krizaka</groupId>
    <artifactId>krizaka-spring-boot-starter-security</artifactId>
  </dependency>
  <!-- outbox, deduplication, retry / DLQ -->
  <dependency>
    <groupId>com.krizaka</groupId>
    <artifactId>krizaka-spring-boot-starter-rabbitmq</artifactId>
  </dependency>
  <!-- published at 0.1.0 until November: pin it -->
  <dependency>
    <groupId>com.krizaka</groupId>
    <artifactId>krizaka-users-client</artifactId>
    <version>0.1.0</version>
  </dependency>
</dependencies>

All artifacts → · Java docs · How they fit together

Every interface is built from layers published on the public npm registry — no account or token to install. Releases are published by the team from a reviewed main; provenance attestations come once trusted publishing is configured.

Package	What it is
	The platform's components: the brand marks, web primitives, layouts and motion on the --kz-* tokens, their React Native counterparts, the mascots and section backdrops
	The semantic design tokens and one theme per brand — CSS (dark, light), typed constants, React Native themes
	The Tailwind CSS v4 preset: the tokens as utilities
	The signature icons, one drawing language — React and React Native
	The three typefaces of every interface — display, text, mono — self-hosted, SIL OFL, for the web and Expo
	Typed, declarative charts on Apache ECharts and the --kz-* tokens — a data table, a written summary and keyboard navigation in every chart; React Native for the simple types
	Money, numbers, dates and plurals formatted the same way everywhere — money from integer minor units only
	Typed messages, format(), <Rich>, a React provider and the krizaka-i18n catalogue checker
	Server-Sent Events behind one bus — PostgreSQL LISTEN/NOTIFY by default, Redis when traffic asks for it — and presence without a write per heartbeat
	Mobile push without an SDK: Expo relays to FCM and APNs from one HTTP call — batched, never throws, reports the dead tokens to forget
	ESLint, tsconfig and Prettier for every repository, and krizaka-ratchet, the UI debt counter
	Orochia's identity on the platform: its theme and product composites (live badge, social icons)
	Orazaka's identity on the platform: the Orazaka Orange theme and product composites (chat showcase, icon registry)
	Orazaka's contracts — TypeScript types, Zod schemas and design tokens

Component docs → · All packages · How they fit together

• One contract per product. Every repository carries an AGENTS.md — the rules its code must keep (architecture, security, compliance) — that humans and AI agents follow alike.
• Documentation generated from the code. API contracts, database references, architecture maps and the component docs — live previews and prop tables read from @krizaka/ui itself — are extracted from the sources and published on krizaka.com/docs; they cannot drift.
• Shared code is a package, never a copy. Security, messaging, users, notifications and billing are released on Maven Central; tokens, primitives, marks and each product's identity on npm. Architecture rules fail the build on a local copy; a change lands in the package first.
• UI debt only goes down. Every interface lints with the shared UI rules (--kz-* tokens only — no raw palette colour, no light: variant — and no locale ternary); krizaka-ratchet records each repository's remaining debt and fails CI the moment a count goes up.
• Supported, then deprecated, then removed. Two majors are supported (N and N-1, fixes for six months); an API lives one full minor deprecated, with a codemod, before a major removes it — the support policy.
• Tested on every commit. Unit, architecture (ArchUnit) and end-to-end suites run in CI; a release never starts on an older database schema.

Everything is Apache-2.0, built and tested on every commit, documented from the code.

• main is protected on every repository: a pull request, the required CI green (administrators included), squash merge only.
• Releases from the history. The Java blocks are versioned by release-please from Conventional Commits (checked by commitlint) and published signed on Maven Central; the npm packages by Changesets.
• Security on by default, on every repository (one organisation configuration, new repositories included): secret scanning with push protection, Dependabot alerts and security updates, weekly grouped Dependabot version updates, CodeQL code scanning on every pull request, and private vulnerability reporting — security policy.
• Measured in the open. OpenSSF Scorecard runs weekly on every repository (actions pinned by commit SHA, read-only tokens) and publishes its score — badges below.

Build status and OpenSSF Scorecard of the main repositories — live

Repository	main	Scorecard	Repository	main	Scorecard
orochia			orazaka
orochia-mobile			orazaka-ai-engine
krizaka-platform-kit			krizaka-build
krizaka-ui			krizaka-com

Latest releases:

• Star the repositories you use — orazaka, orochia, yazakia, krizaka-ui, krizaka-platform-kit. It is how others find them.
• Contribute — how to start, the good first issue label, the roadmap.
• Talk about it — a post, a talk, a link from your project's README: tell us and we will share it.
• Fund the work — sponsorship and partnerships: write to us.

_{Made in Montréal · Open by default · Sovereign by design}