The restaurant ordering stack.
Build custom ordering experiences on your own terms. Connect menus, carts, customer auth, fulfillment, and checkout without rebuilding restaurant infrastructure from scratch.
Menus, carts, order timing, customer sessions, and checkout in one storefront API.
REST API essentials ->Multi-location brands get one operating model for QR, web, app, kiosk, and room service.
Explore the platform ->From blank repo to live storefront.
The page now leads with the same practical promise developers expect: install, connect credentials, run locally, then customize the storefront.
Scaffold
Start from a production storefront template with the Crave CLI.
Connect
Add a location-scoped API key and location ID from the Crave dashboard.
Run
Preview a live menu, cart, and checkout flow locally.
Every restaurant primitive, wired for real ordering flows.
Crave.js is not generic commerce copy. It exposes restaurant-native primitives: daypart menus, modifier trees, pickup timing, delivery addresses, table and room metadata, discounts, customer sessions, and analytics events.
Real storefronts, ready to study.
CLI Quickstart
Scaffold a storefront template, authorize with the dashboard, and start local development.
Storefront SDK
Typed TypeScript helpers for Crave Storefront endpoints, auth tokens, timeouts, and request config.
API Key Guide
Generate and rotate location-scoped storefront keys from the Crave dashboard.
Developers building restaurant software should not start alone.
Crave.js should feel practical from the first visit: clear docs, live examples, copyable setup commands, and a community path for teams building restaurant software.
For chains, hotels, golf courses, and multi-location operators.
Bring Crave.js into production with API keys, location governance, custom integrations, launch support, and implementation guidance from the Crave Up team.
Talk to our team ->