Everyone eats.
Nobody chases
a spreadsheet.
CloudGate Food collects every meal preference before the kitchen needs it, chases the people who forget, and hands the caterer one clean number. Across as many companies as you run.
A day, end to end
- 1 Everyone picks their meals
- 2 A reminder goes to whoever forgot
- 3 The cut-off closes the count
- 4 The caterer gets one number
Sign in to see your own company's cut-off and menu here.
3
Meals a day
Breakfast, lunch, dinner
1h
Reminder lead
Before the cut-off closes
45d
History kept
Then deleted for good
3
Sheets exported
Summary, detail, locations
Four things happen. Three of them without anyone doing anything.
Step one
Everyone picks their meals
- Three meals a day
- Per-meal delivery point
- Family splits supported
Step two
An hour before the cut-off, we chase
- One hour of lead time
- Exactly one email per person, per day
- Menu included
Step three
The cut-off closes the count
- Per-company cut-off time
- Locked means locked
- Overrides are audited
Step four
The kitchen gets one clean number
- Counts by meal and location
- Excel export
- Lead-scoped reporting
Step one
Everyone picks their meals
Breakfast, lunch and dinner — Veg, Non-Veg or nothing at all, each with its own delivery building and room. People who live with family get a meal count and can split a single meal across two addresses.
Step two
An hour before the cut-off, we chase
Anyone who has not answered gets one high-priority email — never two, however many times the job runs. It carries the menu for that day and a link straight to the form.
Step three
The cut-off closes the count
At the time your company sets, the day locks. Nobody can add, edit or delete an order for it — and an admin who genuinely needs to can override it, on the record.
Step four
The kitchen gets one clean number
Veg and Non-Veg totals per meal, per building, per room, for a day or a date range — on screen and as a three-sheet spreadsheet. Team leads see only their own team.
A platform, the companies on it, and the people who eat.
Each tier signs in differently and sees a different amount. Pick one.
Runs Dinelify itself, on its own sign-in and its own guard. Never belongs to a company, and is never scoped to one.
- Create and configure companies
- Invite an administrator into any company by email
- One person can administer several companies
- Deactivate a company — its people stop signing in, its data is kept
- Platform-wide activity across every tenant
Runs the day for their own company. Administering two companies means a switcher in the header — and never seeing both at once.
- Employees: add, invite, deactivate, assign to team leads
- Order on behalf of someone, including past the cut-off
- Reports and the spreadsheet export
- Locations, rooms and the weekly food menu
- Cut-off time, how far ahead people may order, caterer name
Signs in with an email address and a password they chose themselves, from a link — nobody ever reads a password out to them.
- Order for the days ahead and edit until the cut-off
- A separate order history, ten to a page, newest first
- The dish they actually ordered, kept as it was on the day
- Their own delivery location on their profile
- Installs to a phone home screen as an app
Forty-five days, then it is gone for good.
Order history is kept for 45 days by food date. On the 46th day a nightly job deletes it outright — no archive, no soft delete, nothing to recover. What the system holds is what it needs.
Tomorrow's orders are never touched by it, and every run that removes something says so in the activity trail.
Reports covering a range older than 45 days will legitimately come back empty.
The parts you only notice when they are missing.
Built for many companies
Every row of every table belongs to exactly one company. The scope fails closed: no company resolved means no rows, never everyone's.
Invitations, not passwords
New people get a signed, expiring link and set their own password. An admin never holds a credential they could read out.
A weekly menu per company
Seven days across three meals, Veg and Non-Veg, edited in place and replaced whenever the caterer changes it.
Self-cooking, handled
Mark someone as cooking for themselves and they drop out of the ordering flow and out of the "still to order" count entirely.
Everything is on the record
Sign-ins, orders, employee changes, menu edits, cut-off overrides — filterable, and never carrying anything secret.
Works like an app
Installs to the home screen, opens without browser chrome, and tells you honestly when it is offline instead of showing a stale page.