Menura
Photograph a menu, read it on your own AI key, check it, then export it for your till.
For restaurants moving a menu into a till or online. Often replaces Veryfi.
Single license $89 · Extended license $199 · paid once, yours for good
What it does
Download the menu as Square, Toast, Lightspeed or Vendra expect it. Or paste any till's template.
Your own OpenAI, Anthropic or Ollama key reads the photo or PDF. It takes sections, items, prices, modifiers, allergens and dietary tags.
Edit any item or price. The import preview names what would break your till: nameless rows, duplicate SKUs, missing prices.
Raise or lower prices by a percentage or an amount on every menu at once. Preview it, apply it or schedule it.
Publish a reviewed menu as a phone page and print the table code. Mark a sold-out dish in one click.
Diners hide dishes that list an allergen, or show only vegetarian or vegan dishes. Guests are asked to tell staff about allergies.
Every dish against every allergen and dietary tag on one page. Dishes with none recorded are marked, not shown as clear.
Translate names and descriptions on your own AI key and check them. Allergens and prices are never machine-translated.
Download a clean PDF with your logo and accent, prices typeset from the data you reviewed.
A sheet of numbered table cards with your QR code, ready for A4.
Keep breakfast, lunch, dinner and seasonal versions, and re-extract whenever prices change.
The POS CSV columns are stated in the README and pinned by tests. Ask your till vendor before you buy.
Also: a menu copied for another location, connect your own agent (MCP + API), 2FA and backups.
What Menura deliberately doesn’t do.
- No POS API integration — Menura writes files (POS CSV / nested CSV / JSON, columns documented in the README and pinned by tests) and you import them. No till vendor's API is spoken, no credentials held.
- PDF extraction works best with text-layer PDFs; a scanned or photographed menu is the model's job, and models vary.
- One restaurant per installation (single-tenant); your staff share it with viewer, member and admin roles.
- The QR menu shows the menu; it does not take orders or payments.
- No OCR built in; the vision model you configure does the reading.
- Extraction accuracy is not guaranteed for any given menu layout or language — which is why the review screen and the POS import preview exist.
Release history
For Menura, 4.1 makes two changes that every app gets. What’s new in 4.1 →
For Menura, 4.0 means updates from inside the app: the Updates page checks for a new release with your license key, verifies Ownware's signature, takes a backup and… What’s new in 4.0 →
3.3 is for the day prices move. What’s new in 3.3 →
3.2 turns the reviewed menu into everything around the table.
The 3.1 wave gave the catalog a way to reach the other side of the transaction: counterparty email through your own SMTP server, calendar feeds your own calendar…
The re-rendered menu is the reason to buy twice: digitize the laminate, then download a clean branded PDF — your logo, your accent, prices typeset from data you reviewed.
Menura 2.0 adds the 2.0 owner layer.
What’s in the zip
The tree as the zip ships it — the working leftovers the packager deletes are not listed
- .htaccess
- API.md
- Dockerfile
- LICENSE.txt
- QUICKSTART.txt
- README.md
- assets/
- bin/
- config.sample.php
- controllers/
- deploy/
- index.php
- install/
- manifest.json
- offline.html
- router.php
- src/
- sw.js
- tests/
- views/
src/Llm.php: a real module, the first 24 of 421 lines
Chosen as the largest module in src/ that is not one of the shared cores — this product's own logic, not a file every product carries.
<?php
/**
* Llm.php — BYO-key vision client for Menura.
*
* Sends a menu / price-list image (or PDF) to the buyer's own LLM API and returns
* the raw JSON the model produced. That JSON is then passed to Extraction::normalizeMenu()
* for clean canonicalization — Llm.php does no price/structure parsing itself.
*
* (Transport, timeouts, and every key-safety rule below are carried over verbatim from the
* audited Ownware BYO-key client; only the extraction PROMPT is menu-specific.)
*
* Key-safety rules (never relax these):
* - The API key is read from the $settings array passed by the caller.
* - It is NEVER logged, echoed, stored in a file, or added to any error message.
* - It is transmitted only in the Authorization/x-api-key header of the outbound
* request to the provider the buyer configured.
*
* Supported providers:
* openai — POST {base_url|https://api.openai.com}/v1/chat/completions
* default model gpt-4o-mini; image as data-URL; response_format json_object
* anthropic — POST {base_url|https://api.anthropic.com}/v1/messages
* default model claude-haiku-4-5-20251001; image block base64; PDFs via document block
* ollama — POST {base_url|http://localhost:11434}/api/chat
* default model llama3.2-vision; images array; no auth requiredRuns on: Two-minute web installer; PHP 8.1+ with MySQL or SQLite, standard shared-hosting compatible. Tested on PHP 8.3. Or run it in Docker: the Dockerfile is in the zip.
Technical owners can install it with one line and their license key: curl -fsSL https://ownware.io/install.sh | sh -s -- menura <your license key>
Nothing is obfuscated or encoded; what you read is what runs. Manual · API · the test run
Which license do I need?
It comes down to how many installations you need. Running your own business on one site is the Single license. A second domain of your own, or sites you build or run for other people, is the Extended license.
- Install it on one domain or subdomain you own or operate
- Change the source however you like for that installation
- Run your own business on it commercially, client work included
- Re-download the current build any time from your buyer portal
- A second site, or an installation you hand to a client as theirs, needs the Extended license
- No reselling, redistributing or sublicensing the source
- Not for offering it to other people as a hosted service
- Everything the Single license grants
- Install it on as many domains as you own or operate — no cap on the number
- Up to ten client installations, one per client project, handed over or hosted for each client; for more, buy another Extended license
- White-label: remove or replace the product name and logo in the screens of client installations
- Still no reselling or redistributing the source itself
- Running it as a multi-tenant service others sign up for needs a SaaS agreement
Every download carries the full terms as LICENSE.txt. The complete wording is on the terms page.
After you buy
The app’s Updates page installs a new release with your license key, with the release’s signature checked and a backup taken first. Your download link always serves the current build. Download again any time from your order page or the buyer portal; there is no renewal fee.
Email support for installation and for defects in the code as delivered: a person reads and answers every message. It does not cover custom development or server administration. What support covers
Refunds are handled by Lemon Squeezy as merchant of record, case by case. EU consumers keep the statutory 14-day right until delivery starts. Refund terms
It keeps running: your server, the full PHP source, no license check that can fail. If no stable release is published for 365 days, the domain limit lifts; after three such years your copy becomes MIT-licensed. The terms have the exact wording: continuity.
PeerPush 
Trustpilot 
Smithery 
SourceForge Questions
Do I need my own API key?
Will it run on shared hosting?
Does it push directly into my POS?
Is extraction fully automated?
What about handwritten menus or PDFs?
What does it cost to run after the license?
If a menu does not list an allergen, will it work one out?
What does it do with a dish priced at market price?
Can an AI agent run extractions and spend my model credits?
Covered in these guides
More about Menura
Photograph a menu, extract every item and price with your own AI key, review, then export POS-ready data.
The problem it solves
Every restaurant onboarding, POS migration, delivery-platform signup, and print-menu update starts the same way: someone retypes the entire menu. Item by item, price by price, section by section. A 120-item menu with modifiers is an afternoon of data entry — and it happens again at every price change.
Metered document-AI APIs can read menus, but they charge per page forever, and your menu data flows through a third party's pipeline.
Every feature
- POS import preview. Before you export, the review screen runs your rows through the same exporter and names what would break the import — nameless rows the export drops, duplicate SKUs, items with no price or section. Fix it here, not in the till.
- Documented, test-pinned export columns. The POS CSV and nested CSV column sets are stated verbatim in the README and pinned by the test suite — ask your till vendor "does this import?" before you buy. Prices export as bare decimals; the formula guard covers every layout.
- Structured menu extraction. Extract sections, item names, descriptions, prices, modifiers, allergens, and dietary tags from a photo, scan, or PDF.
- Bring your own LLM key. Choose OpenAI, Anthropic, or local Ollama and switch providers any time in Settings.
- Review before export. Edit any item, fix any price, and re-order or re-section everything before export.
- Three export formats. Export nested CSV, flat POS-import CSV with auto-generated SKUs, or JSON.
- Multi-menu library. Keep breakfast, lunch, dinner, and seasonal versions, and re-extract whenever prices change.
- Self-hosted, one-time purchase. Runs on PHP 8.1+ with MySQL or SQLite on standard shared hosting, with no subscription or per-page metering beyond your own LLM cost.
- Installable mobile app (PWA). Add it to a phone or tablet home screen straight from the browser — a full-screen app served from your own server, with no app store involved. Business data is not stored offline on the device; what you see is read live.
- QR menu on your own server. Publish a reviewed menu as a mobile page, print the table code, and 86 a sold-out dish in one click; it stays in your exports and PDF.
- Guests filter by allergen. Diners can hide dishes that list an allergen, or show only vegetarian or vegan dishes, straight from the table code. The page reads what each dish lists and asks guests to tell staff about any allergy.
- Table cards to print. A sheet of numbered table cards with your QR code, ready for A4.
- The file your till imports. Download the menu as Square, Toast, Lightspeed or Vendra expect it, or for any till whose template you paste. It remembers your settings, so a price change is one download.
- An allergen chart to print. Every dish against every allergen and dietary tag on your menu, on one page, with the dishes that have none recorded marked so nobody mistakes them for clear.
- Your menu in your guests' languages. Translate names and descriptions on your own AI key, check them, and your QR menu offers the language. Allergens and prices are never machine-translated: they show exactly as you recorded them.
- One price change, every menu. Raise or lower prices by a percentage or an amount on every menu at once: preview it, apply it in one go, or schedule it for a date. The QR menus show the new prices straight away.
- Updates from inside the app. The Updates page installs a new release with your license key: Ownware's signature is checked, a backup is taken first, and the app puts the previous version back by itself if the update is interrupted or the database step or start-up check of the new version fails. It never checks by itself.
- Backups by themselves. Automatic backups, an optional copy to S3-compatible storage you own, and a weekly check that the latest backup reads back. The Health page names anything that needs attention.
- Own It 4.0.1 — fixes and an up-to-date manual. For Menura, 4.0.1 fixes an installer that had lost its styling, a rollback that a page opened during an update could stop and a command-line update that ended in an error after putting the previous version back. Its manual, FAQ and QUICKSTART now cover everything 4.0 added, including two Nginx rules that keep the data folder private. Your license covers it: press Check for updates on the Updates page, or download it from your order page.
- Own It 4.0.2 — the installer opens on every host. For Menura, 4.0.2 fixes a fresh install on an Apache host: the one-page setup at /install/ looped back to itself and never opened, and now it opens. Your license covers it: press Check for updates on the Updates page, or download it from your order page.
Release notes in full
- Own It 4.1: client installations and your other tools. For Menura, 4.1 makes two changes that every app gets. An Extended license bought from October 4, 2026 covers up to ten client installations, one per client project: hand each one over to the client or host it for them, with the client's logo and colors from the app's branding settings. The API reference now shows how to connect Menura to Zapier, Make or n8n, using its own webhooks and API key. Your license covers the update: press Check for updates on the Updates page, or download it from your order page.
- Own It 4.0: it updates and backs itself up. For Menura, 4.0 means updates from inside the app: the Updates page checks for a new release with your license key, verifies Ownware's signature, takes a backup and puts the previous version back by itself if the update is interrupted or the database step or start-up check of the new version fails. A new install can start with a sample business and remove it in one click; backups run by themselves, with an optional offsite copy and a weekly check that the latest one reads back; and the Health page says whether the install is looking after itself.
- Own It 3.3: one price change, every menu. 3.3 is for the day prices move. Raise or lower prices by a percentage or an amount on every menu at once: preview it, apply it in one go or schedule it for a date, and the QR menus show the new prices straight away.
- Own It 3.2: the menu, safe to read and ready for the till. 3.2 turns the reviewed menu into everything around the table. Guests filter the QR menu by allergen, an allergen chart and a sheet of numbered table cards print ready, and the menu downloads as the file your till imports. It can be translated on your own AI key, with allergens and prices shown exactly as you recorded them.
- Own It 3.1: it writes to the people you serve. The 3.1 wave gave the catalog a way to reach the other side of the transaction: counterparty email through your own SMTP server, calendar feeds your own calendar subscribes to, attachments filed where the paperwork belongs, and export presets other people's software imports. Each outbound feature ships switched off and runs on your own credentials; a failed send is recorded, and the action that triggered it stands. What this app gained is listed at the top of this section.
- Own It 3.0: works for your AI, not just for you. The re-rendered menu is the reason to buy twice: digitize the laminate, then download a clean branded PDF — your logo, your accent, prices typeset from data you reviewed. Price-update mode applies a percentage or fixed change with optional charm rounding and a before-and-after preview of every line.
- Own It 2.0: API, 2FA, backups, dark mode. Menura 2.0 adds the 2.0 owner layer. Upgrade by replacing the files — the database migrates itself, and it is still the same one-time purchase.
Browse self-hosted: AI document tools · Restaurant & café software · Hotel & hospitality software