Forkly: ordering and QR menus for neighbourhood restaurants
Forkly is restaurant software we built: QR menus, table ordering, pickup and delivery, bookings and a live orders board. It is a public preview with demo venues, not yet used by real restaurants.
Forkly is ordering and booking software for neighbourhood restaurants and cafés. It is a product we designed, built and host ourselves. It is a public preview with demo venues at forkly.gr: the product works end to end, but no real restaurant is trading on it yet.
Who is Forkly for, and what problem does it solve?
Small venues often run bookings in a notebook, orders through a phone and a paper menu that is out of date. Forkly gives a neighbourhood venue its own menu, ordering and bookings in one system, with subscriptions and invoicing built in.
How does it work for guests?
A guest scans a QR code on the table or opens the venue page. They browse the menu by category, add items to a basket, and order to the table, for pickup or for delivery. Delivery follows zones the venue draws. The same venue page takes bookings. The interface is in Greek.
How does it work for staff?
Orders board. New orders appear live, and the system routes drinks to the bar and food to the kitchen.
Bookings. Staff see reservations on a floor plan and keep customer records.
Menu. Staff edit categories, items, prices and availability themselves.
QR codes. The system generates printable QR codes as PDFs for tables.
Billing. Subscriptions and invoicing are built in.
Customers receive email notifications. SMS and Viber are built and ready to switch on, but they are not live.
What is the notable engineering?
Data isolation in the database. Forkly is multi-tenant: many venues share one system. PostgreSQL row-level security makes the database refuse to show a venue anything that belongs to another. See how we approach multi-tenant SaaS.
Background workers. Notifications and reminders go through an outbox and a queue worker, so a failed message does not hold up an order.
Documents. QR and PDF generation, and uploads in S3-compatible object storage.
Stack. Next.js on the front, a Fastify API behind it, PostgreSQL with Drizzle.
What is its status?
Public preview. The demo venues and dishes are labelled as such. We will say when real venues go live.
What does Forkly show about how we build for clients?
It shows that we build SaaS where separation between customers is enforced at the lowest level, where background work is reliable, and where a business can print, bill and operate from day one. For similar work, read about our software and SaaS services or see the other products.
Not yet. Forkly is a public preview. The venues you see at forkly.gr are demo venues that show how the product works.
Does Forkly send SMS and Viber messages?
Email notifications work. SMS and Viber are built and ready to switch on, but they are not live.
How is each restaurant's data kept separate?
The database itself enforces it with PostgreSQL row-level security, so one venue's queries cannot return another venue's rows, even if the application code has a bug.
Can you build ordering software for our business?
Yes, if it fits our software work. What we build depends on your venues, payments and integrations, so we give a fixed quote after a short call.
Tell us what you want to build.
A product, a website, a search problem or a system that should work better. We reply with a plain answer and the first step.
May we count your visit with Cloudflare Web Analytics? It sets no cookies and is used only for overall figures: visits, popular pages and loading speed. Cookie policy