Client-side tool
Example: Before entering its labor numbers, a Silver Spring taqueria checks the DevTools Network tab and sees nothing fire on each keystroke, confirming it's using a client-side tool whose math stays on the laptop rather than POSTing inputs to a server.
Browser-only tool, no-server tool
A tool whose math runs entirely in your browser — no server stores your inputs, no fetch fires when you type. Verifiable in DevTools' Network tab in under a minute. The opposite is the lead-gen tool that POSTs every keystroke.
Why it matters
Free restaurant tools come in two architectures: client-side (the math runs in JavaScript on your laptop, which is the safe one) and server-side (your inputs travel to a server first, which is how 'free' tools turn operators into the product). Knowing the distinction is half the audit.
Every Muntin tool is client-side. The build invariants at /security/ enforce it.
Frequently asked
What is client-side tool?
Client-side tool is a tool whose math runs entirely in your browser — no server stores your inputs, no fetch fires when you type. Verifiable in DevTools' Network tab in under a minute. The opposite is the lead-gen tool that POSTs every keystroke.
Why does client-side tool matter for a restaurant?
Free restaurant tools come in two architectures: client-side (the math runs in JavaScript on your laptop, which is the safe one) and server-side (your inputs travel to a server first, which is how 'free' tools turn operators into the product). Knowing the distinction is half the audit.
Browse all
149 terms.
Plain-English definitions for every term in your audit, organized by category.