CompKitchen is built on peer-reviewed food science. Pro at academic prices for individual educators and classroom cohorts — both within standard university P-card thresholds.
Fastest path
Instant verification with your university email
Sign in with your academic Google account (.edu, .ac.uk, .edu.au, .ac.jp, and most national academic TLDs).
We’ll mark you as a verified educator on the spot — no application, no 2-day wait.
Multi-cohort program, research lab, or whole-department access?
Contact us
— we set up custom plans for incubators, extension programs, and food science departments.
For program directors
Infrastructure for a food business incubator grounded in food safety
A compound-level data layer that connects the program you’re already building — HACCP, GRAS thresholds, allergen management — to what your participants need next: differentiated products, defensible pricing, and pitches that hold up to a buyer.
Module 1
Food Safety Foundations
HACCP, FSMA, GRAS limits, allergen control — the work your program is already grounded in.
CompKitchen fits here
Module 2
Product Development
Compound-level formulation grounded in the same data that informs safety.
Module 3
Business Viability
Buyer meetings, shelf-life economics, defensible differentiation against incumbents.
The strongest food business incubators don’t treat product development and food safety as separate disciplines. They share a common foundation: knowing what’s in your product, at what concentrations, with what implications. CompKitchen is the working tool that makes this connection visible to participants.
The same compound data that supports a participant’s GRAS-threshold check — verifying their formulation stays under FEMA limits — also tells them which volatile compounds drive their flavor signature, which compounds they share with category leaders, and which novel pairings would let them defend a price point against private label.
For a department building a program from the food safety side outward, this matters: your participants don’t leave food safety thinking when they walk into product development. They carry it forward, with data.
→Formulate with intent.Move from instinct to a compound-level reason a flavor combination works.
→Defend the product.Walk into a buyer meeting with chemistry-backed differentiation, not just taste claims.
→Scale with confidence.Understand which volatiles drive aroma loss before reformulating for shelf life.
Three exercises mirroring the three-module program design above — adapt for your course length, group size, and lab equipment. Full slide deck and additional exercises on request.
Exercise 1Module 1 ↔ Module 2 bridge · ~75 min · individual or pairs
Compound Audit Lab
Setup: Each participant brings a familiar dish or product prototype — a salsa, a spice rub, a fermented hot sauce, an energy bar. Anything with 4+ ingredients they cook regularly.
Task:
Use /tools#pair to look up each ingredient and pull the top 10 compounds by Odor Activity Value (OAV)
Note the odor threshold and key-aroma flag for each
Cross-reference any compound flagged as key-aroma with FEMA GRAS limits — would the use rate in their dish stay under the regulatory ceiling?
Identify the 3 compounds that most drive the dish’s flavor signature
Deliverable: One-page compound report listing the top-10 by OAV, the 3 signature drivers, and any compound that came within an order of magnitude of a GRAS use-level concern. Cite each compound page (e.g., /compound/eugenol).
Why it matters
Connects “what’s in your product” — the language they already speak from Module 1 — to “what drives your flavor signature.” Participants leave seeing compound data as the same data layer that informs both safety and formulation.
Exercise 2Module 2 core · 75–150 min · individual
Substitute Defense
Setup: Instructor assigns each participant an “unavailable ingredient” constraint:
Regulatory — an aroma chemical that’s been delisted in their jurisdiction
Supply — a seasonal ingredient out of season
Allergen — a common allergen that needs to be removed for a target customer
Cost — an ingredient whose price tripled overnight
Task:
Use /tools#sub to find substitutes ranked by Jaccard compound similarity
Pick the top 2 candidates and pull their full compound profiles
For each, write a defense: shared compound count, top 3 shared volatiles by OAV, what’s lost vs the original, what’s gained
Recommend one — and explain why over the other
Deliverable: 5-minute critique presentation. Whiteboard the original vs the substitute vs what changes in the volatile profile. One slide: the compound-level reason this swap holds up.
Why it matters
Reformulation is constant in real product work — supply, regulation, allergen reformulation, cost-of-goods pressure. This exercise builds the muscle of justifying a swap with chemistry, not “tastes similar.”
Setup: Each group identifies a high-compound, low-recipe novel pairing using /tools#pair novel mode. Target: compound score ≥ 0.40, recipe score ≤ 0.10 — the territory where genuine differentiation lives.
Phases:
Week 1 — Discover. Generate 3 candidate pairings. Pull compound overlap data for each. Pick one to prototype.
Week 2 — Prototype. Make the dish or product in the kitchen lab. Iterate twice based on tasting feedback.
Week 3 — Defend. Compare the prototype’s compound profile against the closest category leader. Where does it overlap? Where does it differentiate? What’s the defensibility against a private-label knockoff?
Week 4 — Pitch. 5-minute CPG-style pitch: positioning, price point, why a buyer should care, what the chemistry backs up.
Deliverable: Prototype tasting for the class + one-page positioning brief + 5-minute pitch.
Why it matters
This is the full incubator arc — compound chemistry → prototype → defensible product → buyer pitch. The compound data isn’t decoration; it’s what lets them walk into a buyer meeting with chemistry-backed differentiation instead of taste claims.
Adaptable to course length, lab equipment, and cohort size. Typically 48-hour reply.
Apply
Tell us about your role and use case — we'll set up access and send a payment link. We typically reply within 2 business days.
A small ask
If CompKitchen contributes to a published paper, course material, or thesis, we'd appreciate a citation. It helps us justify the time we spend curating the data and improves visibility for the research it supports. This is a request, not a license condition.
Canonical reference: Unsupervised Recovery of Food Taxonomy from Volatile Compound Profiles: A UMAP Analysis of 450 Ingredients.
DOI: 10.5281/zenodo.19719459