Run it where you want
A self-hosted distribution is planned, bringing the storefront, dashboard, API, and workers together.
Orders, menus, loyalty, and the tools you already use.
One desktop workspace. Hosted by Crave, or on your own server.

Build a branded ordering experience around your menu, your locations, and your guests. Pickup ordering is the first Restaurant OS milestone.
One product direction, from guest experience to the tools behind the counter.
Your branded storefront
Items, modifiers & availability
From incoming to ready
Hours & restaurant settings
Built around PostgreSQL
Docker distribution planned
Existing Crave platform
Existing Crave platform
Restaurant OS features are in development. API and MCP tooling belongs to the existing Crave platform.
Start with Crave’s existing APIs, SDK, and MCP tools.
Connect an MCP-compatible client to Crave. Inspect menus, check storefront readiness, and work with location settings through the existing platform.
Explore MCP toolsCRAVEUP_ENVIRONMENT=sandbox npx -y @craveup/mcpLocal stdio server · Browser sign-in for authorized actions
A path toward running the essentials on infrastructure you control.
A self-hosted distribution is planned, bringing the storefront, dashboard, API, and workers together.
Persistent restaurant, menu, and order data, with backup and recovery validation before production self-hosting.
Build on shared commerce contracts and explicit integrations as the Restaurant OS runtime takes shape.
The first milestone: create a restaurant, publish a menu, place a pickup order, and process it in the dashboard. Then restart and prove the data stays.
Help shape a workspace that fits your restaurant. Join the list for early access to Crave Restaurant OS.