Cooking for ten.
Planning for none.
MealOrbit started in a Pune kitchen in 2025. A joint family of seven — two grandparents observing strict Jain, three adults on standard, two kids who refuse anything with a tomato.
Every morning began with the same conversation. “What are we cooking for lunch? Did anyone tell the maharaj? Wait, today is Ekadashi — only one meal? Who's getting groceries?”
We tried spreadsheets. We tried WhatsApp groups. We tried a whiteboard. Nothing held — because none of these tools understood that strict Jain means no roots, Paryushan means a different menu, and Aarav has a peanut allergy.
MealOrbit is what we built so that conversation stops happening. So that the cook knows what to make. So that the shopping list writes itself. So that no one cooks something Grandma can't eat.
What we believe.
Built for one specific kitchen.
We started with the Jain household, not a generic meal planner. Compliance, substitutions, observance days are first-class. Generalization comes later.
Truth in history.
Plans are snapshotted. What you cooked last Tuesday is what your records say you cooked. We never rewrite the past.
No vendor lock-in.
CSV / DOCX / PDF exports today. Full data export soon. Your shopping list belongs to you, always.
Real privacy.
No third-party trackers. No analytics that need a cookie banner. Hosted in India, data stays in India.
Where we've been. Where we're going.
- Jan 2025Cap 1
A whiteboard in a Pune kitchen
Founder family of seven. Two strict-Jain grandparents, three adults on standard, two kids who refuse tomatoes. The whiteboard could not keep up.
- Mar 2025Cap 2
First prototype, paper notebooks digitized
Recipes typed into a Notion table. Spreadsheets for the schedule. WhatsApp for the cook. Nothing fit; everything broke on Paryushan.
- Aug 2025Cap 3
The data model that finally worked
Compliance level as a first-class column. Snapshotted plans. Substitutions as table rows. The model held — and we started coding.
- Dec 2025Cap 5
Schedule + kitchen view shipped
Real-time across the maharaj’s phone and the executive assistant’s laptop. Three test households cooking from it daily.
- May 2026Cap M
Public beta · marketing site
Free beta opens. Recipe library, shopping list with three exports, member roles, audit log. You are reading the marketing site we just shipped.
- Q3 2026Cap 8Planned
Full data export + Hindi pilot
One-click export of everything. Hindi locale pilot with three Gujarati-speaking households.
- Q4 2026Cap 10Planned
Trust + hostel kitchen mode
Multi-shift scheduling, donor reports, daily headcount integrations for community kitchens.
- 2027Planned
Exit beta · paid plans launch
When the product is worth paying for, we will say so. 30 days notice. Free tier stays.
We charge when we deserve to.
Beta means rough edges, missing modules, and the occasional bug we ship by mistake. Charging during that would be dishonest. When the product earns its keep, we'll tell you exactly when, exactly how much, and give you 30 days notice — paid or not, your data stays yours.