Raktim94 /nodedr-restaurant-pos
Self-hosted restaurant POS with tables, kitchen display, reservations, QR ordering, loyalty and local-network operation.
★ 300⑂ 192👁 3⑃ 14● 13▤ 15
+1
Daily
300
stars
192
forks
3
watchers
14
prs
13
issues
15
releases
README
Open-source, self-hosted restaurant POS & management system — billing with UPI QR payments, tables, kitchen display (KDS), reservations, inventory, staff attendance & payroll, accounting, reports, CRM/loyalty and multi-branch control. Offline-first, runs on your own server, no subscription. Not a retail POS bolted onto a restaurant; purpose-built for dine-in, takeaway, delivery and kitchen operations. Developed by NodeDR Infotech Private Limited Try OrderRestro · Case study · Maintainer: Raktim Ranjit Quick Start · How to use · Full tutorial · Features · Screenshots · Docs · Contributing · Roadmap --- Integrate with AI Coding Agents Building a restaurant website or app on OrderRestro? Point your coding agent at prompts/AI_INTEGRATION_PROMPT.md (verified endpoints, scopes, server-side Next.js pattern, MCP setup, test checklist). See also AGENTS.md and llms.txt. What this is Nodedr OrderRestro is a purpose-built, offline-first Restaurant Management System for restaurants, cafés, coffee shops, bakeries, fast food, fine dining, bars, food courts, cloud kitchens, and multi-branch chains. The whole stack — Postgres, API, and web app — runs on one local server on the restaurant's own LAN: order-taking, billing, KDS, and printing all keep working with the WAN cable unplugged. No subscription, no forced cloud dependency, self-hosted by design. It's a sister project to nodedr-pos (the retail-shop POS), reusing its proven patterns — auth/session model, receipt rendering, ESC/POS printing, currency-rounding discipline — but built as its own codebase, because restaurant floor/kitchen/reservation operations and retail shop billing are different enough domains that forcing one schema to serve both would have compromised both. See PROJECT.md for the full rationale. Non-negotiable product principles (the short version — full detail in PROJECT.md): 1. Offline-first / self-hosted — a single branch runs entirely on a local LAN server, zero internet dependency once installed. 2. Premium, not "POS-ugly" — every screen is held to the same bar as Stripe Dashboard, Linear, Notion, Vercel, Shopify Admin. 3. RBAC everywhere — every action gated by a granular, individually toggleable permission, never a hardcoded role check. 4. Modular / plugin-ready — 20 product domains that can evolve independently. 5. Server-authoritative money — all pricing, tax, discount, and loyalty math computed server-side, never trusted from the client. Where to run it "Offline-first" describes how the app runs, not where it has to live — nothing about it is tied to a specific machine or network: - A local LAN server (the default, recommended setup). One machine in the restaurant runs docker compose up; every till, tablet, and KDS screen on the same Wi-Fi/Ethernet reaches it at http://:1995. No internet connection is needed once it's running — order-taking, billing, KDS, and printing all keep working with the WAN cable unplugged. - An
Discussions
#19Idea: a checked reference for takeaway-order inquiries0 comments · 2026-10-27#12Welcome to nodedr-restaurant-pos Discussions!0 comments · 2026-08-06
Latest release
OrderRestro 1.22.0 v1.22.0 2026-11-05Packages for Ubuntu and Debian (amd64 and arm64). They install a systemd service that runs the version-pinned Docker images. One command: curl -fsSL https://orderrestro.nodedr.com/install-linux.sh | sudo bash Or: sudo apt install ./nodedr-orderrestro_1.22.0_.deb Guide: https://orderrestro.nodedr.com/docs