Explain
You come here when a reader must understand: how it works, a documentation hub or article, a changelog, a FAQ, a policy.
On a phone, resize the frame or open the layout's page: every template reads in one column.
Components
Krizaka UI's components: search, platform filters, compact link cards.
Why this layout. A reader looking for the right piece scans a filterable catalogue instead of reading every page. Built on Catalogue page
Krizaka UI
Components
Every component, web and mobile, documented from its code.
Krizaka UI releases
Two releases with their changes by kind.
Why this layout. A user checks what changed in each release and whether it concerns them. Built on Changelog page
Krizaka UI
What changed
Every release, newest first — and why, when it was a decision.
- 2.6.0
Page blocks
- AddedPage, PageHero, CardGrid, LinkCard, ArgumentCard and seven more blocks.
- ChangedThe blocks' stylesheet is imported once by the app.
- 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.
Why this layout. A builder decides whether a component fits, sees it live and copies it, all on one page. Built on Component page
Actions
Button
- Web + Mobile
- Stable
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.
Why this layout. A reader follows one article, always knowing where they are, what it covers and what comes next. Built on 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.
npx orazaka installStart
Then start it; the console opens on your machine.
FAQ
Questions as disclosures, each with a short answer, the contents beside them.
Why this layout. A reader finds the one answer they came for without reading a page. Built on 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.
Why this layout. A newcomer picks a collection, starts quickly and sees what is new, from one hub. Built on Docs hub page
Documentation
Build with Krizaka
Every building block the products are made of, documented from its source.
Collections
Start in one line
npx orazaka installEvery page here is generated from the code it documents — when the code changes, the page does.
Orazaka's journey
Install, guard, answer — each with its command.
Why this layout. A reader grasps a process as a few steps, each with the command that does it. Built on How-it-works page
How it works
The journey of a request
Six stages, the same for every request — and none of them leaves your server.
Install
One command pulls the engine, the models you choose and the console.
bashTerminal npx orazaka installGuard
Every request crosses the same interceptors: identity, quotas, the rules of your workspace.
bashTerminal orazaka rules add --deny pii-exportAnswer
The best local model answers; the answer is checked before it is shown.
bashTerminal orazaka chat --model llama3.3
Privacy policy
A summary and three sections with their contents.
Why this layout. A person finds a commitment in plain words, with a summary first and the detail by section. Built on Legal page
Privacy policy
Last updated: October 2026
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.
Why this layout. A newcomer finds the right documentation from one page of grouped entry points. Built on Marketing layout
Documentation
Build with Krizaka
The building blocks the products are made of, documented from their source.