Save it with its story.
Capture a recipe from a website, review the ingredients, and keep its source. Manual entry belongs here, too.
Website capture: local prototypeIn development · A first look
The recipes you love, the meals you plan, the groceries you need. We’re building Chef-It to bring them all to the same table.
Try a sample weekA development preview. No account needed for this sample.
01 / Keep what you love
That weeknight favorite deserves more than another open tab. Chef-It is taking shape around the everyday work of saving, finding, and cooking your recipes.
Capture a recipe from a website, review the ingredients, and keep its source. Manual entry belongs here, too.
Website capture: local prototypeLook up a recipe by name or the ingredients you have in mind. Categories, favorites, and richer organization are part of the full library we’re building.
Search: local prototypeChange the servings and carry those quantities into the grocery list. Your saved recipe stays intact. Cooking aids and offline access are still in progress.
Serving calculations: tested locally02 / See the pieces connect
Explore three sample recipes. Change the portions, look at the plan, then see what lands on the grocery list.
Interactive illustration · Sample data only · Runs in this page
3 sample recipes
Your sample menu
Open nights stay open.
It’s a plan, with a little space.
This sample uses a fixed plan. Reusable menus and automatic planning are part of the product roadmap.
For the three meals
Shared ingredients come together. Check off sample items as you go.
This illustration explains the intended journey. It is separate from the Chef-It app and does not save your changes.
03 / Make the next step easier
The plan is the connection between your recipe collection and the rest of your week.
Private meal-calendar feeds work in the local backend. Calendar setup and checks in Apple Calendar, Google Calendar, and Outlook are still ahead. The first version publishes meals; it won’t read your personal events.
Start with the recipes and groceries. When it helps, account for ingredients you’ve confirmed you already have. Pantry tracking is optional, and stock should never be guessed.
We’re building a way for authorized agents to work from reviewed ingredient needs. An agent’s access and shopping capability must be verified separately. A shopping request is only a request.
An honest look at where we are
Chef-It is a development preview.
Release acceptance is still in progress.
Recipe capture, search, serving calculations, dated meals, grocery calculations, optional pantry entries, private meal feeds, and scoped agent tools in the backend.
A native iPhone and iPad app, fuller recipe organization, cooking controls, reusable planning flows, and the work toward close Paprika parity.
Recipe migration, offline workflows, public account security, verified calendar and agent connections, and real household trials. Launch timing and pricing are undecided.
Development preview · October 2026 · Deployment does not establish release readiness or live integration support.
A few things to know
You can explore the sample on this page or open the development app. The account page depends on configured identity services; account creation and recovery may be unavailable during setup. Chef-It is still in development, with release acceptance and native iPhone and iPad distribution unfinished.
That is part of the release plan. Importing a Paprika recipe collection, preserving its contents, and showing any unsupported fields still need implementation and compatibility validation. Chef-It does not yet offer a complete Paprika replacement.
Chef-It is intended to prepare ingredient needs and a reviewable shopping request. An external agent may do the shopping through its own authorized connections. Live agent and retailer compatibility is unverified; the sample here never places an order.
No. The product is designed to work without inventory setup. Pantry deductions are optional and should reflect stock you’ve confirmed. Shopping reports alone won’t be treated as proof of purchase or used to silently update stock.
The demo uses invented recipes and keeps changes only in the current page. It has no signup form, analytics, cookies, external fonts, or external trackers. Searches and choices aren’t submitted to a server. Downloading the sample creates a text file on your device. See the privacy policy for the Chef-It service and app.
The local backend scopes recipe and planning data to households and supports revocable agent access. Production account linking, identity verification, recovery, and full data export and deletion remain release work. Calendar publishing is designed around revocable private links.
A little less deciding. A little more cooking.
No signup. Just a first look at what we’re making.