// the find
ury-erp/ury
URY - FOSS restaurant management system super powered by ERPNext.
URY is a restaurant management system built as a custom app on top of ERPNext/Frappe, bundling POS (React), a kitchen display system called Mosaic (Vue), a self-order kiosk app, and a setup/reporting dashboard in one monorepo. It's aimed at multi-outlet restaurant operators who want P&L, inventory, and KOT workflows without building ERP plumbing from scratch, and at Frappe-ecosystem developers who already run bench deployments.
Riding on ERPNext means stock, accounting, and BOM/recipe mapping come for free instead of being reinvented - the README leans on Frappe's doctype system for things like pre-billing checklists and shift reconciliation. The 'operational red flags' feature (delayed KOTs, unclosed bills, excessive cancellations) reads like it came from someone who actually operated a restaurant, not a generic feature list. packages/core has an actual typed Frappe client with a roles.test.ts, so there's at least one spot where auth/role logic isn't just trusted blindly. The claim of 10+ outlets running for 10 months is a concrete production signal rather than a demo-only project.
No backward-compatibility guarantee while 'in active development,' and the three previous standalone apps (pos, mosaic, pulse at v1) are being deprecated in favor of this monorepo with support cut off December 2025 - existing adopters are mid-migration right now. The stack is split between React (pos, frontend, self-order) and Vue (mosaic) despite a shared packages/ui - that's two component ecosystems to maintain instead of one, undermining the point of having a shared UI package. Outside of roles.test.ts, there's no visible test coverage for billing, payment reconciliation, or stock deduction - the exact code paths where a bug costs someone real money. Adopting this means adopting the full Frappe/bench deployment model; there's no way to run just the POS piece without standing up an entire ERPNext instance.