Use cases
Find the way Ponics’ Pantry fits your kitchen.
Different cooks need different things from a living cookbook. Start with the job you need it to do.
Whether you are preserving family recipes, tracking BBQ experiments, cooking around restrictions, organizing a tailgate crew, or building a creator cookbook, the core idea is the same: keep the recipe, the change, and the story connected.
Start with the job, not the label
A "type of cook" is only useful if it points to a real problem.
Ponics’ Pantry is built around Jobs To Be Done: the recurring cooking problems people need help solving.
That means the best question is not "what kind of cook are you?" It is "what are you trying to make easier, safer, more repeatable, or more memorable?"
Everyday home cooks
Job
I need one clean place to keep recipes, cook from them, and remember what my family actually liked.
Best starting tier
Home Cook
Core features
- recipe import and manual entry
- Kitchen Mode
- shopping lists
- pantry preferences
- grocery usuals
- structured recipes
- basic versioning
- 5 public share links, lifetime total
- Shared Spaces participation
Upgrade path
Move toward Serious Cook when Ponics’ Pantry becomes your regular kitchen system and you want more room, unlimited public sharing, compare, richer Shared Spaces contribution, or more advanced tools.
Why it sticks
The product becomes the place you return to when dinner has to happen.
Families and recipe keepers
Job
I need our family recipes and the stories around them to stay alive across generations.
Best starting tier
Home Cook for participants, Serious Cook for organizers
Core features
- recipe families
- versions and lineage
- Shared Spaces participation
- Table Talk
- shelf forks that do not use personal recipe or version slots
- memories
- Events for holidays and recurring gatherings
- Basil continuity
Upgrade path
Move toward Serious Cook when you want to create Shared Spaces, add your own recipes to a shared shelf, use unlimited public share links, organize a richer family cookbook, and preserve more history.
Why it sticks
The cookbook gets more valuable every time someone adds a branch, memory, photo, or event.
Dietary and health-focused cooks
Job
I need to adapt recipes for real constraints without losing the original.
Best starting tier
Serious Cook
Core features
- branch new versions
- compare versions
- nutrition estimates
- substitutions
- AI-assisted variations
- scaled servings
- cook notes
- structured version history
- unlimited public share links
Upgrade path
Move toward Kitchen Lab when you want deeper experimentation, structured outcomes, nutrition optimization, Pro Capture, or repeatable testing.
Why it sticks
The original recipe stays intact while the version you actually need keeps improving.
BBQ, smoker, pizza, bread, and fermentation cooks
Job
I need to track experiments so the best version is repeatable.
Best starting tier
Serious Cook, with Kitchen Lab for Pro Capture and analytics
Core features
- recipe versions
- compare
- cook sessions
- cook telemetry templates
- outcomes and notes
- ingredient and method changes
- Shared Spaces for cooking crews
- Events for cookoffs, tailgates, and recurring gatherings
Upgrade path
Move toward Kitchen Lab when Pro mode in Kitchen Mode, structured cook capture, cross-recipe workflows, analytics, and repeatable experiment tracking become central to how you cook.
Why it sticks
You stop guessing which tweak worked and start building a record of better cooks.
Tailgate crews, lake houses, and recurring groups
Job
I need our group food traditions, planning, and stories to be easy to repeat.
Best starting tier
Home Cook for participants, Serious Cook for organizers
Core features
- Shared Spaces participation
- Shared Spaces creation at Serious Cook and above
- Shared Spaces Events
- attendee and RSVP tracking
- exact menu versions
- group shopping lists
- task ownership
- event chat
- photos and recaps
- clone prior events
- version-event history
Upgrade path
Organizers move toward Serious Cook when recurring gatherings need Shared Space creation, recipe shelf contribution, event history, reminders, event archives, richer memory, unlimited public sharing, and less text-message chaos.
Why it sticks
The group does not just plan the next gathering. It keeps the lore from the last one.
Creator cooks and community builders
Job
I need my audience to actually use, fork, and keep evolving my recipes.
Best starting tier
Recipe Creator
Core features
- larger recipe and version capacity
- unlimited public share links
- recipe families
- subtree publishing
- cookbook publishing
- creator collections
- public listing pages
- audience access paths
- share and fork workflows
- Recipe Insights
- component import and export
Upgrade path
Move toward Recipe Creator when publishing, audience access, collection management, public cookbook pages, and distribution become part of the work.
Why it sticks
A recipe does not disappear after a post. It becomes something people can keep cooking and building from.
Restaurants and kitchen teams
Job
I need the team to preserve working recipes while still improving them.
Best starting tier
Kitchen Lab
Core features
- unlimited recipes
- unlimited versions
- structured recipes
- version history
- service-safe recipes
- experiment branches
- cook telemetry templates
- Pro mode in Kitchen Mode
- cross-recipe workflows
- analytics
- Shared Spaces for team access
- menu and event continuity
Upgrade path
Move toward Kitchen Lab when repeatability, training, controlled changes, large libraries, Pro Capture, and operational memory matter.
Why it sticks
The working version stays clear while improvements can happen without losing control.
How to choose your starting point
Start with the smallest job Ponics’ Pantry can do for you this week.
If you only need a home for recipes
Start with Home Cook. Import a few recipes, cook from one, and see whether it becomes easier to find what you need.
If you already tweak recipes often
Start with versions. Create one branch and compare it to the original. Serious Cook is the natural next step when comparison and unlimited sharing matter.
If you cook with a group
Start by joining a Shared Space or creating one as a Serious Cook. Add recipes, invite the people who cook with you, and try one Event.
If you are serious about outcomes
Start with cook notes and telemetry. Kitchen Lab is where structured capture, Pro mode, and analytics become the center of the workflow.
Compare helps show what changed, not just what was edited.
Start with the job you need done
Bring in one recipe, create one version, or start one Shared Space. Ponics’ Pantry grows from there.