Build a working commerce product.

Run Box locally, call the API your deployment exposes, and move the same package set into infrastructure your institution operates.

Terminal
$ box create acme-commerce
 engine
 merchant console
 website

$ box start acme-commerce 4000 3010
API      http://localhost:4000
Console  http://localhost:3010
Ready in 1.8s

One deployment. Three interfaces.

The CLI changes the deployment, the API changes commerce state, and events connect the systems around it.

box

Command line

Create, authenticate, install, run, deploy, inspect, and upgrade.

openapi.json

Generated API

Use the contract published by the packages installed in your deployment.

order.paid

Events and adapters

React to signed events and connect providers at explicit ports.

The same deployment moves with you.

Local development is not a separate hosted sandbox. You evaluate the packages, interfaces, and operating boundaries that move into your environment.

  1. 01

    Create and run locally

    Use the CLI to create a deployment, install its packages, and start the engine, console, and website together.

  2. 02

    Integrate what is installed

    Generate clients from the deployment’s OpenAPI contract and connect surrounding systems through signed events and provider adapters.

  3. 03

    Operate in your environment

    Move the same package set into production with your hosts, credentials, network boundaries, and upgrade schedule.

Understand here. Implement in the docs.

This page explains the operating model. The developer documentation owns quickstarts, API schemas, configuration, and version-specific instructions.