TONIGHT · YOUR KITCHEN

What’s for dinneris not a question about food.

It’s a question about a tired brain at seven o’clock, a fridge whose contents you already know, and forty minutes you were not planning to spend choosing. Cibora starts from what you have and hands back something you can actually cook tonight.

Start with what I haveSee how it decides

No account required to cook. Nothing to install. 1,074 recipes · 54 countries.

3 ready, 49 one item away, 98 two items away, of 1,074 recipes.
  • ready
  • one away
  • two away
  • not tonight

Buy one thing → plantain opens 5 more dinners · cucumber 3 · salmon 3

Tick what you actually have

Ten things you already own.

Assumed, because the app assumes them too: baking powder, baking soda, bay leaf, black pepper, chili flake, cinnamon, dried oregano, dried thyme, garlic powder, ground cinnamon, ground cumin, ice cube, ice water, olive oil, onion powder, paprika, red pepper flakes, salt, sugar, sunflower oil, sweet paprika, vegetable oil, water, white vinegar.

02 — At the stove

The moment you start cooking, the design gets out of the way.

Everything you just did — the counting, the lighting-up — is banned from the cook screen. Somebody standing over hot oil on step four needs a calm screen; spectacle there is a defect, not a feature. The player takes the whole screen over the app’s own navigation and shows you one step. Every primary control is at least 56 pixels tall because your hands are wet. The screen will not sleep while you cook. Timers stack and keep running when you move between steps.

And when you fall behind, nothing restarts.

Press “I’m behind” and every timer still running stretches by half again — six minutes becomes nine — and the step swaps in a catch-up tip. Nothing you have already done is thrown away. The pan does not care that the app said fifteen minutes.

  • 56px minimum height on every primary control
  • the screen is kept awake for the whole cook, and released the moment you leave
  • voice: next · back · repeat · ingredients · timer — the browser’s own speech engine, no API key, nothing stored by Cibora
  • a mise-en-place step with a tick-off checklist, inserted before step one
  • 3,118 timers already written into the catalogue — you are not setting them

The optional photo check reads the step you are standing on and comments on what it can see. It will never tell you food is cooked: a photograph has no core temperature. It runs on a model provider the operator has to configure, and without a key it is simply off — the timers, steps and voice are not.

Step 1 · Mise en place

Lay everything out before the heat goes on.

Skip the neat piles. Get the first thing in the pan and prep as you go.

06:0009:00
I’m behind · every running timer × 1.5

03 — One shop

Decide once, not seven times.

The same idea at a week’s scale. Hand Cibora a shop and it builds seven dinners around it, then lists only what is genuinely still missing. Your allergies, exclusions, diet, time ceiling and equipment are hard filters: they run before anything is scored, and nothing can outscore them. What survives is ranked by a model you are allowed to read — nutrition 25, how much of your shopping it uses 20, vegetable variety 15, protein variety 10, waste 10, cost 10, time 5, cuisine spread 5 — and the plan stores it, so every night can tell you why it is there.

Time is never quietly relaxed. Ask for 20 minutes and you get 20 minutes — Cibora drops your "kind of dish" preference instead, and says that it did.

Prices on the shopping list come from demo retailers. They are labelled demo everywhere they appear, and they are not real prices. Live pricing needs a retailer API the operator has configured; there is no connect-your-shop button.

04 — The ledger

Cibora is new, and it says so on its own screens.

Real

  • 1,074 original recipes, written for this app, across 54 countries.
  • 7,027 steps. 3,118 carry a timer. 1,589 carry a technique tip.
  • 416 unit tests across 37 files, plus a quality gate that runs over the whole catalogue before any of it reaches the database — zero high findings, zero medium.
  • The cooking works signed out: pantry, week, timers, cook log. No account is required to cook.
  • Your allergen list never leaves your device, and it is applied as a removal — never a ranking, never relaxed.
  • Finishing a cook writes three things at once: it logs the cook, decrements only the pantry items you confirm, and ticks tonight off your week.

Generated, for now

  • Generated

    The live floor. The cooks, cities and seat counts are generated while Cibora is new. The recipes, steps and timers under them are real, and so is the kitchen you land in — but nobody is waiting for you, and we will not pretend otherwise. There is no video, no voice channel and no live connection between kitchens. “Find a partner” seats you alone in a real recipe with a generated room around it.

  • Demo data

    Grocery prices. They come from demo retailers and are labelled demo everywhere they appear. Live pricing needs a retailer API key the operator configures.

  • Estimate

    Nutrition, until every measurable line resolves to a USDA record. A wrong calorie count presented as measured is worse than an honest estimate.

  • Licensed

    Dish photographs are licensed stock, matched to the dish and credited to the photographer. They are not photographs of your dinner, and none of them is AI-generated. Without a photo key the app draws its own plate art rather than inventing an image. The pan at the top of this page is generated atmosphere, not anyone’s kitchen.

  • Needs a key

    The conversational chef, the fridge photo scan and the pan check. They run on a model provider the operator has to configure, and they are metered. Without a key they are off, and the chef falls back to an engine that answers only from the recipe database. Everything deterministic works regardless.

  • Not sold

    There is no payment page, no checkout, and no payment processor in the app. Cooking bills nobody. You may still meet the words “Cibora Pro” if you exhaust the free AI allowance — that is a tier we have not built a way to sell.

Anything on the right that becomes real moves left. Nothing moves the other way quietly.

  • free to cook
  • no account required
  • nothing installed
  • no payment page

Open Cibora, tick what you actually have, and cook one of them tonight.

Open CiboraBrowse the catalogue

Your kitchen isn’t in the cloud. Your pantry, your week, your cook log, your allergens and your running timers live in this browser on this device. That is the trade in both directions: nothing to leak, nothing to sync — and if you clear your site data, your kitchen goes with it. The catalogue, the photographs and anything you post to the community do live on a server; accounts exist for that, and only for that.

124 dishes in the catalogue are done in 20 minutes or less, 349 in half an hour — prep plus cook, not active time.

Type
Instrument Serif · Figtree · IBM Plex Mono
Colour
ink #0b0b0a · ivory #f2efe6
Build
Next.js 16.3 · React 19.2 · no new dependencies · the 1,074-cell field is one canvas and zero kilobytes of library code
Counted
figures generated from the shipped catalogue on 2026-09-04