Recipes stored, versioned, shareable
Your recipes, labels, costs, and allergen data live in one cloud library: autosaved as you work, deep-linkable to a teammate, and embeddable on your own website.
Autosave you never think about
Every change you make (an ingredient amount, a nutrient override, an allergen checkbox) is captured automatically. Work is snapshotted continuously as a local safety net, so a browser crash or accidental refresh never costs you the last hour, and saving to your account lands the recipe in your cloud library, available from any device you sign in on.
There is no "did I remember to save?" anxiety and no version soup of files named final-v3-REAL. The recipe you open is the recipe you left, down to which tab you were editing. For teams, that means the label your colleague reviews is guaranteed to be the current one, not an export from last Tuesday.
Start fast with AI Jumpstart
An empty library is the biggest barrier to switching tools. AI Jumpstart removes it: paste any recipe as plain text (from a document, an old spreadsheet, even a photo transcription) and it parses the ingredient lines and matches them to USDA FoodData Central entries for your review.
A morning of pasting can migrate a whole product line into your library.
Sub-recipes: build once, reuse everywhere
Your library is not just a flat list of products; it is a graph. Save a component as a sub-recipe and drop it into any number of parent recipes: one brioche dough across a dozen pastries, one spice blend across a whole sauce line. Nutrition, allergens, ingredient statements, and costs all flow from the component into every product that uses it.
Reformulate the component once and every dependent recipe updates: the nutrition panel recomputes, the ingredient statement re-nests its parentheses, and the cost rollup adjusts. That is the difference between a recipe file and a recipe system.
Deep links and live label embeds
Every saved recipe has a stable URL (/app/<id>): bookmark it, drop it in a chat, and the editor reopens in the exact state you left. But sharing goes further: any label can be published as a live embed, a snippet you paste into your own website that renders the current Nutrition Facts panel for that product.
</iframe>
Reformulate, and your website's label updates itself: no webmaster ticket, no stale PNG.
Duplicate, experiment, export
Reformulation should be cheap. One click duplicates the current recipe so you can push sugar down or protein up without touching the version that is already on shelves; keep both, compare their labels, and promote the winner when you are ready.
Your data is also never locked in: export the complete recipe and label state as a JSON file to back it up outside our servers, move it between accounts, or keep it in version control alongside the rest of your product documentation. Manual overrides, allergen selections, packaging and cost data: the whole state round-trips. See the recipes FAQ for the details of what is included.
One library, ten languages, every module
The interface itself runs in 10 languages, so a bilingual team can work on the same library with each person using the UI language they think in, while the labels they produce follow whatever market format the product needs.
And the library is the hub the rest of the platform hangs off: the same saved recipe drives your compliant label in any of our formats, your Supplement Facts panels, your cost history, and (when you turn it on) the inventory and production module, where recipes become finished goods with lot codes. Start free in the generator; sign in when you want it all saved.