Coastal Café

Decide what to start next. Toast browns while eggs poach — but the plate-up waits for both, and nothing improves while it sits.

Loading Coastal Café…

About Coastal Café

Coastal Café is a cooking game about one decision made over and over: what to start next. Sixteen dishes run across eight stations — a prep bench, a grill, a fryer, a stove, an oven, a coffee machine, a cold bench and the pass — and twenty-four services get steadily busier. The whole thing runs in your browser with no sign-up, and your progress stays on your device.

Every recipe is a dependency graph rather than a list of steps, and that is the whole game. Toast can brown while eggs poach; the eggs cannot go on the toast before either is ready. Writing recipes as an ordered sequence would make every dish a queue and a timer, and it would quietly hide the only decision that matters — what to put on while something else cooks.

Each station has a fixed number of slots, and unattended cooking still fills one: the grill is busy while the bacon is on it, whether or not anybody is looking at it. That is what turns a rush into a decision rather than a race.

Components also have a holding time. A finished element is perfect for a while and then falls away, and a dish is as good as its worst element at the moment it goes on the plate. So starting everything as early as possible is right when the kitchen is quiet and wrong when it is not.

And no service is offered that has not been cleared. Each one has been worked through this same kitchen by a planner — a deliberately simple one, because an optimal solver would certify services no human could work — and a shift it could not clear with everybody served is absent from the list. A kitchen asked for more than it has is not a hard shift, it is an impossible one, and from the inside the two feel identical.

It is a game, not catering training. The dishes are invented, the money is fictional, and nothing here is a statement about food safety or about running a real kitchen.

How to play

  1. Choose a service. It tells you how many tickets, how long you have, what is on the menu and which stations are open.
  2. Tickets arrive over the service. Each one is a dish, and each dish is a set of steps that depend on each other.
  3. Press a step to start it. It occupies a slot at its station until it finishes, and then it is available to whatever needed it.
  4. The plate-up is the last step of every dish, at the pass. When it finishes, the dish goes out.
  5. Watch the holding times: a component that sits too long drags the whole plate down, because a dish is graded on its worst element.
  6. Customers leave if their ticket takes too long. Longer dishes get more patience, but not indefinitely.

Controls

  • Everything is a button: this is a game about choosing, not about aiming. Each option shows the dish, the step, the station and how long it takes.
  • Steps that cannot be started yet are listed separately with the reason — waiting on another step, no free slot, or that station is shut.
  • C changes the camera between the kitchen, the pass and an overhead view. Escape or P pauses.

The rules

  • A step can start when every step it needs has finished, its station is open, and that station has a free slot.
  • A step occupies its slot for its whole time. Nothing can be hurried and nothing can be taken off early.
  • A finished component is at its best for its holding time, then falls away to nothing over the same again.
  • A dish's quality is the freshness of its worst component at the moment the plate-up started — not the average, because a perfect plate with one stone-cold element is a plate with a stone-cold element on it.
  • A stale dish still takes half its price. Zeroing it would make one bad plate cost as much as a walk-out and teach you to bin food rather than serve it.
  • A customer walks out when their patience runs out, and anybody still waiting when the doors shut has walked.

Scoring, saving and limits

Your grade is how many tickets went out at all and how good they were when they did, weighed equally and rounded. Takings are a consequence of both and are not graded again on top — a till total rewards an expensive menu rather than a good cook. Your best grade for each service is kept, and the till figure on the title screen is the sum of those bests, derived from the record rather than counted up.

Your best grade and takings for each service are kept in this browser only, along with your settings. Nothing is uploaded, there is no account and there is no leaderboard. Clearing your browser's site data for this site clears it.

Sixteen dishes and twenty-four services on one kitchen layout. There is no staff to manage, no ordering, no stock and no money to spend between services: this is about the hour of the service itself. Boarding a customer is a count rather than a queue, and nothing burns — a dish that sits goes stale, it does not catch fire.

Accessibility

Every control is a real button at least 48 CSS pixels tall, and nothing needs a drag, a hold or two fingers at once. Steps that cannot be started say why rather than simply failing. The service pauses if the tab goes to the background, so a kitchen cannot lose every ticket while nobody is looking. If your system asks for reduced motion the camera cuts instead of easing.

Questions

Why can I not start something?
There are only three reasons and the game tells you which: a step it needs has not finished, the station it uses has no free slot, or that station is shut for this service. The list of things that are not ready shows the reason beside each one.
Should I start everything as early as I can?
When it is quiet, yes. Once it is busy, no: a component that finishes long before the plate-up goes stale waiting, and the dish is graded on its worst element. Holding time is what makes the order you work in matter.
Why is a station shut on some services?
Because a kitchen with something out of action is a different puzzle, and the menu for those services is chosen so every dish on it can still be made. A service whose menu needed a shut station would be unclearable, and the suite refuses one.
How do you know a service can be cleared?
Because one has been. Every service here was worked through this same kitchen by a planner, and a shift where anybody walked out is absent from the list. The planner is deliberately greedy rather than optimal — an optimal solver would certify services no human could work.
Does the daily service change?
It is chosen from the certified services by the date in UTC, so everybody gets the same one on the same day, and it is marked with a star on the list. There is no leaderboard attached to it.