Technology
The stack
behind Findown
We publish the tools we actually use. Presentation on Next.js. Records in Odoo. Payments through Razorpay and Stripe. No mystery layer in the middle.
Why the
split exists
Guests and staff need fast, clear screens. Finance, stock, plans, and restaurant records need a system of record. We keep those jobs separate so a marketing page never becomes the place you store an order.
- Python
- Odoo 19
- Next.js 15
- React 19
- PostgreSQL
- Tailwind CSS
- Razorpay
- Stripe
- QR ordering
Odoo and Python
Operations, ERP, plans, and restaurant records live in Odoo. It is the system of record for every Findown product.
Next.js and React
Guest shop, operator app, and this parent site run on Next.js. Fast pages, clear routing, and a stack we can keep current.
PostgreSQL
Transactional data stays in a proper database, not a spreadsheet export pretending to be a backend.
Razorpay and Stripe
Card and UPI checkout where the restaurant product needs it. Keys and settlement stay with the operator account.
QR and mobile web
Guests open a menu on their phone. No mandatory app install for ordering at the table.
Roles and access
Kitchen, cashier, manager, and owner see different screens. Public pages never talk to admin tools.
What we will not claim
We do not put certification badges on this site that we have not earned in public. Security work is role-based access, least privilege on public APIs, and keeping secrets out of the browser. If you need a written security note for a tender, ask and we will send what we can stand behind.
Ask for a technical noteTell us what you run today
Restaurant, ERP, a website, or hotel booking. We will map a first live set that your staff can actually use.