From the first peg to the month’s last rupee, your officers’ mess, kept honestly.
New here? Your mess office sends the invitation.

Officers messes in Indian Army units: the PMC and Mess Secretary who close the monthly mess bill, the Mess Havildar who keeps the dining-in roll and issues ration, the Bar NCO who raises bar chits, and the officers who check their own mess account.
It is invitation-only. There is no public sign-up. A unit admin creates each account and assigns the member's home unit before they can sign in.
Yes. Each unit is its own mess, with its own people, stock and bills. Every page, action and API call is limited to the signed-in person's home unit, and nobody in a unit can switch to another unit's data.
There is a versioned REST API at /api/v1 with bearer tokens, rate limits and idempotency keys. There is no separate mobile app; members and staff use the web app, which works on a phone.
Access is capability-scoped. Each appointment receives a capability template — for example Bar NCO, Mess Havildar, or Quartermaster — bound to a single unit. Members only see and act on the modules their duty requires.
Data is stored in a MongoDB database. Changes to people, units, permissions and master lists are written to an append-only audit log, and every charge on a member's account is a posted row that is reversed, never edited.
Prices sit on stock lots, and every bar line keeps the rate it was charged at. Flat messing rates take effect from a set date, the ration scale keeps numbered revisions, and corrections are reversal rows, so a published bill does not change when a price does.