The studio
kris + zaka (坂)
Krizaka presents
Our story
One studio. One engine. Every product on the same blocks.
Krizaka is a studio built on one refusal. Your data shouldn't have to leave home to be useful, a creator shouldn't hand a fortune to a platform to get paid, and nobody should have to take software on faith. So we forge the building blocks in the open, build an AI engine on them — Orazaka — and ship our products on both. We use what we make, every day.
Team battle · 4 productsOne studio · one engine · the same blocks
Choose a product
The blade folded in the open
A kris is a blade forged in layers: iron folded onto iron, again and again, until a pattern rises in the steel. Zaka is the slope you climb, one step at a time. Krizaka is the forge halfway up that hill.
Why a forge? Because the software we were asked to trust had turned into a black box — data shipped to someone else's cloud, income routed through someone else's rules, code nobody outside could read. We set out to build the opposite, and to prove it rather than promise it.
Nothing leaves the forge unfolded, untested or undocumented, and everything that leaves it is open source under Apache-2.0. You don't have to believe us: read the pattern in the steel.
Special move
Prove it, don't promise it.
In the cornerThe duck · The builder
The platform: the blocks every product stands on
Open source, published, versioned — and used by our own products first. If a block isn't good enough for Orochia, it isn't good enough for you.
- public repositories
- 33
- components in Krizaka UI
- 106
- published packages
- 43
- Krizaka UIWeb and native components, one design language
@krizaka/ui 3.3.0 - Tokens, icons, intlColours, glyphs, money and dates
@krizaka/tokens 3.3.0@krizaka/icons 0.4.0@krizaka/intl 0.1.0 - Realtime & pushLive updates and mobile notifications
@krizaka/realtime 0.1.1@krizaka/push 0.1.0 - Java platform kitUsers, billing and notifications on Spring
krizaka-platform-kit 0.2.0
The engine
ōrāre (to speak) + zaka
The oracle that never leaves home
Ōrāre: to speak, to ask — the Latin root of oracle. In the old stories you climbed to the oracle with your question, and you trusted it with something private.
Today, asking an AI usually means carrying your contracts, your files and your ideas down to someone else's valley. For a lot of teams that's a deal-breaker, so they do without. We think that's the wrong trade.
Orazaka brings the oracle to your hill: answers drawn from your own documents, visuals generated on your machines, Studios that take the repeat work — on your infrastructure, under your rules. Your questions and your answers stay in the house, and every line that touches them is public, so your security team can check instead of trust.
It is also the engine the products call: Yazakia's conversations run on it, and so will every product that needs intelligence without sending anything away.
Runs onKrizaka UITokens, icons, intlJava platform kit
Special move
Your data never leaves home.
In the cornerThe owl · The reader
Product
Yamata no Orochi
Eight heads, one deal: the creator keeps 90%
Yamata no Orochi is the eight-headed serpent of Japan's oldest chronicles. Players of a certain age met it somewhere else too: waiting at the end of a 1990s arcade tournament, sealed by three clans and their sacred treasures.
The creator economy has a serpent of its own: heavy cuts, payouts nobody can audit, links that leak, accounts closed overnight. Creators do the work and carry the risk — and too often they're the last to be paid.
Orochia is our answer: a video platform where the creator keeps 90% of every sale, every movement is written once in a double-entry ledger, and the whole thing runs on servers you choose. In the myth, Susanoo doesn't win by force — he sets out eight vats, one for each head. Orochia sets out one answer for each.
Runs onKrizaka UITokens, icons, intlRealtime & push
Special move
90% to the creator. On every sale.
In the cornerThe flamingo · The creator
Coming soon
The dating app where you talk first
Talk first. Meet both ways.
Dating apps turned people into a catalogue: swipe, score, repeat. You end up judging photos at midnight and being judged the same way.
Yazakia starts with a conversation instead of a form. An agent powered by Orazaka gets to know you in your own words, then opens a small batch of three to five people who match you in both directions — with the reasons in words, never a score.
The next batch waits for your debrief. No swipe, no catalogue, no endless feed: fewer people, better chosen, and nobody you didn't both want to meet.
Runs onKrizaka UITokens, icons, intlOrazaka
Special move
Both ways, or not at all.
In the cornerThe lovebird · The introducer
Under construction
A listening space with a face and a voice
A presence that stops.
Some evenings you need to put words on what you carry, hear one question you hadn't asked yourself, and leave with one clear line.
Yororis is a listening space with a face and a voice: an AI presence that says it is one, listens, reflects back, asks one question — and stops. A moment has an end, and so does the day: the limits are the product.
It is powered by Orazaka's wellbeing pack, so its guards live in the engine and what you say stays on our machines. We're building Yororis in the open and studying its framework — legal, ethical, clinical — before making it available. Nothing is live, nothing is offered, and there is no date.
Runs onKrizaka UITokens, icons, intlOrazaka
Special move
A presence that stops.
In the cornerThe crane · The listener
How Orochia stays live
A tip lands, a bid moves the price, a message arrives: the screen that cares hears of it in well under a second — no polling, no message broker, no extra service to pay for.
Every action is written to PostgreSQL first. Then one NOTIFY crosses to every instance of the app; each hands the event down the Server-Sent Events streams it holds. Plain HTTP, the same session as the rest of the API, and any instance serves any stream.
A cut connection comes back by itself and says where it stopped (Last-Event-ID): what it missed is replayed from the database, each message once. Presence is a heartbeat, never a database write per beat.
The app closed? The same notification leaves as a push — Expo, then Firebase on Android (Apple's APNs on iOS once our developer account is active) — and a tap opens the very screen it is about.
- Written first. Send, bid, pledge, tip: an ordinary HTTP request, committed to PostgreSQL — the database is the truth.
- One NOTIFY. NOTIFY orochia_events: every instance hears it on its LISTEN connection. Past three instances, the same code switches to Valkey by configuration.
- Down the open streams. Each instance pushes it to the Server-Sent Events streams that care — a heartbeat every 15 s, a resume after any cut.
- Or to the phone. In the background, a push: Expo Push → Firebase Cloud Messaging or APNs → the phone; the tap opens its screen.
- Median delivery, 500 open streams
- 27 ms
- 95th percentile, 2,000 streams
- 65 ms
- Memory per open stream
- ≈ 90 KB
- Median, from a message sent to the push shown on Android
- 0.5 s
Measured, not estimated: scripts/realtime-load.mjs on a production build, one instance on a MacBook (2026-10-11), and a real push timed on the Android emulator (2026-10-13).
Special move
What happens reaches you once, in order, wherever you are.
In the cornerThe carrier pigeon · The messenger
We use our own products.
Every product runs on the same blocks and, when it needs intelligence, on Orazaka. The table is the proof — read from the products' own manifests.
| Product | Krizaka UI | Tokens, icons, intl | Realtime & push | Java platform kit | Orazaka |
|---|---|---|---|---|---|
| Orazaka | Yes | Yes | No | Yes | Is the engine |
| Orochia | Yes | Yes | Yes | No | No |
| Yazakia | Yes | Yes | No | No | Yes |
| Yororis | Yes | Yes | No | No | Yes |
- Vat 01Sealed
Leaked linksPlayback signed for five minutes
- Vat 02Sealed
Forged paymentsOnly the gateway can confirm
- Vat 03Sealed
Double creditsSettled exactly once
- Vat 04Sealed
Unpaid creatorsBalances read from the ledger
- Vat 05Sealed
Unverified content2257 records before any upload
- Vat 06Sealed
Abuse left unansweredReports kept, takedowns explained
- Vat 07Sealed
DeplatformingYour servers, several gateways
- Vat 08Sealed
Lock-inApache-2.0, every line
The flock
The ones keeping watch.
Our mascots aren't decoration. Each one carries a promise we don't compromise on.
Martin, the falcon
The sentinel
Watches the borders: Law 25, GDPR, 2257. Nothing crosses that shouldn't.
The owl
The reader
Reads your documents and keeps every question in the house.
The duck
The builder
Calm on the surface, paddling hard underneath: the code, the tests, the docs.
The flamingo
The creator
Balances on one leg and still makes it look easy. We make sure she gets paid.
The carrier pigeon
The messenger
Carries signed messages, and delivers each one once.
The lovebird
The introducer
Opens a door only when both sides want it open.
The crane
The listener
Stands still, hears you out, then lets you get back to your life.
The phoenix
The two flames
Purple and gold — two rival flames from the arcade legend, flying together. Code reborn with every commit.
The folded blade: everything is open.
A kris is only as strong as the layers you can't see. Ours are all in plain sight: the AI engine, the video platform, the design system, the icons, the Java building blocks — public repositories and published packages, Apache-2.0.
That's our proof. No benchmark to take on faith, no borrowed logo wall: clone it, run it, read it, fork it. If something on this page isn't in the code, the code wins.
See everything we've openedKrizaka · arcade cabinet
Continue?
Round one is over. Continue?
We don't have a trophy case to show you yet. We have something better to start from: an engine and products you can run today, more on the way, every line in the open, and promises written down where you can hold us to them. The next rounds are played with the people who use them — try them, read them, or write to us.
Insert Coin1 credit = 1 storyCredit 01