Prices are per month. Businesses you add yourself can be free; sign-ups start with a trial. Public sign-up page: /signup

Sign-up and billing

Businesses pay their monthly subscription by card on Lemon Squeezy's page, and their plan follows the payment automatically. Keys are saved encrypted and are never shown again, only their last four characters. Enter them here, never in a chat.

1. In Lemon Squeezy, create one subscription product per plan (monthly) and copy each variant number into the plan above ("Card variant").
2. Settings → API: create a key and paste it here. Settings → Stores: copy the store number.
3. Settings → Webhooks: add the address below, choose a signing secret, tick all subscription events, and paste the same secret here.

Connect any AI provider with your own API key, then choose which model does what. Costs are worked out from the prices you enter (per 1 million tokens, in USD), so keep them up to date with the provider's price list.

Providers

Models

The model name exactly as the provider writes it (e.g. gpt-5.4-mini, claude-haiku-4-5, gemini-3.5-flash). "Cached" is the price of input the provider has cached (repeated menu text in chats); leave 0 if it has none. "Effort" is for reasoning models only; leave it empty otherwise.

What each feature uses

If the main model fails (error, refusal, unreadable answer), the backup model answers instead. Reading menus from photos needs a model that can see images (and PDFs, if you want those).

No feature has a model yet, so AI is off everywhere (the menu assistant won't show). Pick a model above and tap "Use this model for everything", then Save.

Point each domain's DNS (an A record) at this server; the certificate is made by itself. Keep the records you already have.

Website domain

The product's own website (what it is, plans, stories) shows at the front door of this domain, for example www.yourbrand.com. Leave it empty and the website is still at /home.

QR domain

A short domain (for example q.yourcafe.com) for the codes you print. A scan lands there and is sent on to the menu, so you can move the app or change the main domain one day without reprinting a single code. Codes printed from the dashboard use it from the moment you save. Leave it empty to print the normal address.

Old domains

Everything on an old domain is sent to the same page on the new address (the path and the table number are kept), so printed codes and shared links on it keep working.

Shown on /terms, /privacy and /help. Until a company name and a contact email are saved, those pages show a "draft" notice and sign-up does not ask for consent. Once saved, every new account must accept the terms and the privacy policy (and the acceptance and its version are recorded in the audit log). The texts are a starting template: have a lawyer review them before you rely on them.

Every day a compressed copy of the database is sent to storage that is not on this server, and once a week a full copy with the photos. If the server is ever lost, nothing is. Use any S3-compatible storage; Backblaze B2 is the cheapest (10 GB free), Cloudflare R2 is just as good.

Sends password reset links, weekly reports, booking notices and AI allowance warnings. Optional: until you set it up, owners who forget their password ask you, and staff ask their owner. The key is saved encrypted and never shown again, only its last characters. Enter it here, never in a chat.

A business gets a feature when its plan includes it and it's switched on here. Use Beta to try a feature with a few businesses first (tick "Beta tester" when you edit a business), or Off to pause it everywhere. You (the platform admin) can always use everything, to test it.

Maintenance

Guests leave a name, phone number, address or note with orders, table bookings and gifts. After the number of days below, those details are erased from old records every night. Totals, items, dates and ratings stay, so stats and reports keep working. Regulars and "your usual" are recognised only within this period. Leave it at 0 to keep everything.

Lets owners create an account and log in with their Google account, next to the usual email and password. Optional: until you enter the details below, the Google buttons do not appear. The secret is saved encrypted and never shown again, only its last characters. Enter it here, never in a chat.

1. In Google Cloud Console, create a project, then APIs & Services → OAuth consent screen (External) and fill in the app name and your email.
2. Credentials → Create credentials → OAuth client ID → Web application. Under Authorized redirect URIs add the address shown below.
3. Copy the client ID and client secret here. Then publish the consent screen ("In production") so any Google account can use it.