Krizaka UI
Krizaka UI
Modèles

Expliquer

Vous venez ici quand un lecteur doit comprendre : comment ça marche, un portail ou un article de documentation, un journal des changements, une FAQ, une politique.

Sur un téléphone, réduisez le cadre ou ouvrez la page de la mise en page : chaque modèle se lit sur une colonne.

Components

Krizaka UI's components: search, platform filters, compact link cards.

Pourquoi cette mise en page. A reader looking for the right piece scans a filterable catalogue instead of reading every page. Construit sur Catalogue page

Krizaka UI

Components

Every component, web and mobile, documented from its code.

Krizaka UI releases

Two releases with their changes by kind.

Pourquoi cette mise en page. A user checks what changed in each release and whether it concerns them. Construit sur Changelog page

Krizaka UI

What changed

Every release, newest first — and why, when it was a decision.

  1. 2.6.0

    Page blocks

    • AddedPage, PageHero, CardGrid, LinkCard, ArgumentCard and seven more blocks.
    • ChangedThe blocks' stylesheet is imported once by the app.
  2. 2.4.0

    Data and media

    • AddedDataTable, Combobox, DatePicker, VideoPlayer.
    • FixedA live line chart no longer hides its line.

Button

The page of the Button, with its preview and its sections.

Pourquoi cette mise en page. A builder decides whether a component fits, sees it live and copies it, all on one page. Construit sur Component page

Actions

Button

The action: six looks, three sizes, the Krizaka cut, and the whole life of an action built in.
  • Web + Mobile
  • Stable
ts
import { Button } from "@krizaka/ui/button";

When to use

For the action a block is about; links that look like actions use `asChild`.

Accessibility

A real button; while loading it says so in a live region.

Orazaka's CLI

An article with its pages, breadcrumb, facts, contents and pager.

Pourquoi cette mise en page. A reader follows one article, always knowing where they are, what it covers and what comes next. Construit sur Docs article page

Pages of the documentation

The CLI

Install, start and develop Orazaka from one command line.

Install

One command installs the engine, the console and the models you choose.

bashTerminal
npx orazaka install

Start

Then start it; the console opens on your machine.

FAQ

Questions as disclosures, each with a short answer, the contents beside them.

Pourquoi cette mise en page. A reader finds the one answer they came for without reading a page. Construit sur Docs article page

Pages of the documentation

Questions, answered

What people ask before they install.

Does anything leave my server?

No. Requests are answered by models on your machine; the only calls out are the ones you configure yourself.

Which models can I run?

Any model your hardware can hold. Orazaka lists the ones that fit before you download them.

How is it priced?

A plan with a monthly credit allowance. Credits are spent per job, and what is left is always shown.

krizaka.com/docs

The five collections, a quick start, the most read pages, what is new.

Pourquoi cette mise en page. A newcomer picks a collection, starts quickly and sees what is new, from one hub. Construit sur Docs hub page

Documentation

Build with Krizaka

Every building block the products are made of, documented from its source.

Collections

  • Krizaka UI

    Tokens, a Tailwind preset, the components — live, generated from their code.

  • Krizaka Java

    Parent, BOM, starters, messaging, Problem Details.

  • Orazaka

    The sovereign AI engine: install, packs, administration.

  • Orochia

    The creator platform: payments, auctions, the admin console.

Start in one line

bashTerminal
npx orazaka install

Every page here is generated from the code it documents — when the code changes, the page does.

The owl's promise

Orazaka's journey

Install, guard, answer — each with its command.

Pourquoi cette mise en page. A reader grasps a process as a few steps, each with the command that does it. Construit sur How-it-works page

Orazaka

How it works

The journey of a request

Six stages, the same for every request — and none of them leaves your server.

  1. Install

    One command pulls the engine, the models you choose and the console.

    bashTerminal
    npx orazaka install
  2. Guard

    Every request crosses the same interceptors: identity, quotas, the rules of your workspace.

    bashTerminal
    orazaka rules add --deny pii-export
  3. Answer

    The best local model answers; the answer is checked before it is shown.

    bashTerminal
    orazaka chat --model llama3.3

A summary and three sections with their contents.

Pourquoi cette mise en page. A person finds a commitment in plain words, with a summary first and the detail by section. Construit sur Legal page

Privacy policy

Last updated: October 2026

In short: we collect what you send us, keep it in Québec, never sell it, and delete it when you ask.

What we collect

Your email and your message, when you write to us.

Where it is kept

On servers in Québec, encrypted at rest.

Your rights

Ask for a copy or for deletion at any time; we answer within 30 days.

A documentation hub

Groups of compact link cards under the hero.

Pourquoi cette mise en page. A newcomer finds the right documentation from one page of grouped entry points. Construit sur Marketing layout

Documentation

Build with Krizaka

The building blocks the products are made of, documented from their source.

Start here