Imagine the system you actually want in your life.
Start with the problem you want to solve or the thing you want to create. Sushi Kitchen helps turn that intention into an inspectable Recipe made from open-source projects, then fits it to the machine, privacy posture, and network you actually have. The Kitchen stays open source. Tsugiita roughly translates into the concept that we have of a “Sous Chef” and is the optional paid assistant experience, powered by Sushii Intelligence, when you want help comparing possibilities and tradeoffs.
Your imagination comes first. Sushi Kitchen turns the outcome you want into a Recipe you can understand, save, change, and run on your own machines.
Twelve families. Ninety-three rolls.
Family sizes run uneven by a factor of five. Drawn to scale, one square per roll, rather than as twelve equal tiles.
A creator wants her work back under her control.
Start with the human problem: photographs and illustrations are scattered, useful metadata is trapped inside files, private locations should stay private, and AI help should enrich the archive without becoming the source of truth. Sushii turns that goal into a Recipe instead of asking the creator to become a storage, database, metadata, and machine-learning expert.
Sushii Assets combines a data Bento, a creator workbench with Lychee, ExifTool and ImageMagick, and optional local intelligence. ExifTool reads embedded source metadata before AI enrichment; originals stay immutable by default; GPS remains private by default.
Solutions, not a catalogue.
You do not have to know what a roll is to start. Find the problem you actually have, and the composition is already chosen.
- Case study
A kitchen that can hold a privilege
Eight containers on four networks, two of which have no route to the internet at all. The queue sits on one of those. The workers sit on the other, outbound-only, and never accept a connection from anywhere.
7 rolls · Privacy · Legal privilege - For consultants and researchers
Everything you read, searchable by meaning
Eight rolls that turn a folder of documents into something you can ask questions of, without any of it reaching a third party.
8 rolls · Privacy · Business-confidential - For studios and publishers
A publishing pipeline that stays yours
Six rolls for turning raw material into finished work, with the archive and the models both on hardware you control.
6 rolls · Privacy · Business-confidential
Start with a Recipe that is already assembled, then inspect it, change it, and make it fit the machine and network you actually plan to use.
Ready to serve.
Knowledge Worker, to scale.
Eight rolls, 11.8 GB of memory between them. Each block's area is its share of the total — a stack is never eight equal parts.
Or start from nothing. Add the Rolls you want, let the Builder resolve declared needs, and save the result as your own versioned Recipe.
Four courses, one kitchen.
Omakase: you choose how far to go, and the kitchen handles the order of things.
Pick a composition
Combos that solve one problem, platters that stand up a whole scenario — each lists its rolls, its hardware, and its licence.
Resolve requirements
Add a roll and what it needs resolves in one click. The Builder never hides a closed door.
Hosted or self-host
A URL, credentials and a named privacy profile — or a bento box that never leaves your network.
A running kitchen
Models, interfaces, storage, monitoring — the stack comes up as one unit, and stays yours.
✓ 5 rolls up · 8 GB RAM
itadakimasu — your kitchen is running.
The open Kitchen tells you what is true: dependencies, hardware, known licence state, machine fit, and what still needs attention.
Tsugiita is the paid layer above those facts, powered by Sushii Intelligence: it helps decide what to build, compare alternatives, explain tradeoffs, and adapt the Recipe to your real machines.
A kitchen that can hold a privilege.
A law practice in Harrison, New York runs its whole AI stack on its own hardware. Client documents are searchable, calls are transcribed, and the file room answers questions — with the network egress closed. Nothing goes out.
It was built by the attorney who read the ninety-three licences. That is the shortest honest answer to whether any of this actually works: it is already load-bearing for someone whose bar licence depends on it.
The Recipe stays simple. The guidance can get smart.
A Recipe is a durable description of what you chose, how it is configured, and where it should run. Keep the open facts inspectable. Add Tsugiita only when you want a paid architectural deputy to help you reason about the next decision.
Menu, Builder, Recipes, Machines and deterministic checks stay useful without a paid assistant.
Save the intended system once, then adapt variants for the machines and networks you actually use.
Pay for architectural guidance and judgment, not permission to use the open-source platform.
Twenty-six compositions.
Seen end-on, the way a roll is cut — every family sized by the rolls it holds.
Pick your side of the counter.
A URL, credentials and a named privacy profile. Nothing to provision, nothing to patch.
A sealed bento box on your own hardware. No telemetry, no per-seat meter, nothing leaving the network.
84 of 93 rolls are open both ways, so the choice waits until you make it.
Build your own AI operating system in your own private sushi kitchen.
- Private by architecture
- The self-host path sends nothing out: no telemetry, no per-seat meter, no keys leaving your network.
- 93 pinned services
- Every roll pinned to a version, and its licence read at that version rather than recalled from memory.
- Composable, checkable
- Rolls declare what they provide and what they need, so a build verifies before it ships.
- One command
- The bento box is a sealed artifact — versioned, re-downloadable, and happy offline.