Skip to main content
Crave pairs a documented developer surface with a managed cloud product: the integration contract is explicit, while production franchise operations remain in a managed control plane. The Storefront SDK is publicly downloadable from npm but is marked UNLICENSED. Its canonical source repository is private, and npm availability or public documentation does not grant permission to copy, modify, or redistribute the package. Contact hello@craveup.com for licensing questions. Crave Cloud is where brands coordinate real locations, roles, integrations, payment routing, customer identity, loyalty, and operational readiness.

​
How to think about it

​
Managed cloud is the production default

Production restaurant franchise infrastructure is not just a package install. It needs secure roles, location readiness, integration monitoring, audit trails, payment routing, and support for operational edge cases across many stores. Use Crave Cloud when you need:
  • multiple locations, franchisees, or business entities
  • staff roles and Business Manager access
  • payment routing between corporate, franchisee, or location accounts
  • monitored integrations with ordering, loyalty, payments, or identity providers
  • supportable production operations

​
Public developer surface

Use the Crave.js developer surface when you need:
  • a local storefront you can run and customize
  • typed SDK calls for menus, carts, checkout, payments, and analytics
  • React components that can live inside your application
  • REST examples for non-TypeScript clients
  • clear contracts for webhooks and API behavior

Build with Crave.js

Start with the CLI, SDK, API, and UI components.

Understand Crave Cloud

See how storefronts connect to identity, ordering, loyalty, payments, and operations.

​
What is not self-hosted

The documented Crave.js developer surface does not make the SDK package or every part of Crave Cloud open source or self-hostable. Business Manager, production identity boundaries, managed loyalty, payment routing, integration health, and franchise operations are managed platform capabilities unless your Crave agreement says otherwise. This keeps the developer experience flexible without pushing the operational burden of a franchise platform onto every storefront team.