Clinical nutrition platform

Every plate,
in protocol.

Protocol-driven feeding studies with milligram-level precision, from recipe library to kitchen production to compliance.

Nourishing the research behind tomorrow's cures.
PRIME · Day 2 compliance
Protein1.34 g/kg · in band
Energy1,809 / 1,850 kcal · in band
Carbs50.3% · watch
12 participantsDay 2 of 14
What Oyster does

Feeding studies are hard.
The software shouldn't be.

Most tools plan menus. Oyster runs protocols, with the precision a study demands and the workflows a kitchen actually uses.

01

Milligram-level targets, not guesswork.

Every recipe is built on a USDA-backed ingredient library, so each plate carries exact macro and micronutrient values. Participant-level protein ranges and dietary restrictions travel with the person, not a spreadsheet.

180 ingredients · 43 recipes
kcal, protein, carbs, fat, fiber, per 100 g
02

Studies, cohorts, and compliance in one structure.

Each study is its own protocol, with its own cycle length, its own participants, and its own targets. Compliance is measured against those targets daily, so out-of-band days surface before they become protocol deviations.

MIND · 5-day cycle
PRIME · 14-day cycle
in-band or out-of-band, per participant
03

Built for the kitchen, not just the clipboard.

Shopping lists, batch production, and printed meal labels with allergen flags. This is the unglamorous work that decides whether a protocol survives contact with a real kitchen.

PRIME · Lunch · Day 2
Lentil and walnut loaf
Contains: Tree nuts, Wheat
How it works

From protocol to plate to proof.

Five steps, one system. Everything a coordinator sets up, the kitchen can cook and the study can defend.

01
Define the study
Set the protocol: cycle length, targets, and cohort.
02
Build the menu
Compose recipes from a USDA-backed ingredient library.
03
Enroll participants
Attach protein ranges and restrictions to each person.
04
Produce it
Shopping lists, batch production, and printed labels.
05
Prove it
Daily compliance against targets, in band or out.
A day in a study
Breakfast
Steel-cut oats, berries, walnuts
420 kcal · 14 g
Lunch
Lentil and walnut loaf
560 kcal · 24 g
Dinner
Baked cod, farro, greens
610 kcal · 38 g
Against target
Protein · in band
kcal · in band
Carb % · watch
Why Oyster exists

It started with a chef who knew there was a better way.

Oyster was built by a research chef working feeding studies at Moffitt Cancer Center in Tampa. Day after day, the same realization: protocols tracked across spreadsheets, printouts, and memory, when all of it could be done so much more easily.

The tools that existed were built for hospital food service at enterprise scale, not for a study with fourteen participants and a nutrient target measured in milligrams. So the work got built into software instead. Every feature exists because someone had to do that job on a real study day.

Built by
A research chef, in a working study kitchen
Who it serves
Research programs, clinics, rehab and outpatient teams
The ribbon
A reminder of who the work is for

Nourishing the research behind tomorrow's cures.

The gap

Serious tools stopped at the hospital door.

Enterprise platforms
Built for hospital systems.

Powerful, expensive, and scoped to food service at institutional scale. A fourteen-person study is not who they are for.

Menu planning tools
No protocol, no proof.

Fine for recipes and shopping lists. No study structure, no participant targets, nothing to show a reviewer.

Oyster
Protocol-grade, at any size.

The precision a study demands, in a tool a small clinic, a rehab kitchen, or a single research program can actually run.

Every plate, in protocol.

Already using Oyster? Your dashboard is one click away. If you run feeding studies another way, I'd like to hear about it.